PacketTrends Mesh a public map of nodes that asked to be on one map stations

Stations

Every node heard on this feed in the last 24 hours, and how much of it we heard. Being heard is what puts a station on this list — not publishing a position, and not having a name. Most of the mesh appears here under a bare node id, which is an ordinary state rather than a defect.

Board Active New Trend

Counting radio receptions

Day Week Month

How many distinct stations this feed heard, one row per month — growth or decline you can see, instead of having to remember what the board looked like the last time you checked. A station counts here the same way it counts on the board: heard as a sender at least once (node_id, not gateway_id) — a busy gateway that only ever relays other stations' traffic does not inflate this number every period it happens to be listening.

Month Active stations Change New
November 2026 1479 ▼ 694 428
October 2026 2173 ▲ 602 1126
September 2026 1571 — 1571
Reading this. Active stations is a distinct-station count within the period — a station heard on three different days of the same week counts once for that week, not three times, so Week and Month are never a sum of the Day rows underneath them. The LAST row on this table is very likely a partial period — today has not finished yet, and neither has this week or this month — so do not read a low final row as a drop until the period it belongs to has actually ended. This is not the whole mesh: it is the stations THIS feed heard, bounded the same way the map and the board are (a regional MQTT root, radio receptions only), so a change here can mean the mesh changed, or that something about how well THIS feed hears it changed — a dead listener would show up here as a drop in every station at once, not as one station going quiet.