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

!75bad9d6

!75bad9d6 · updates every minute

91% 4.06 V · 14 days ago — telemetry is far patchier than position (only about a quarter of nodes send it at all), so an old reading here is ordinary rather than a sign of trouble.

This node advertises a name but no position, so it has no pin on the map. That is an ordinary state rather than a fault — a node broadcasts its identity on one schedule and its location only if its owner enabled that, and most of the mesh never does.

Most recent

Atlavox Cape Coral 981m !9ea03ba8 999m PASCO-ACS_EOC 1000m Squid’s Base G2 20775m !a6965010 20776m

Who heard it

Last 24 hours, plus 2 direct link(s) heard earlier.

This node is a gateway. It has received 3 node(s) itself (3 RF frame(s)) and uplinks its own traffic straight to MQTT — so it is not heard by anything the way an ordinary node is. MQTT is the way out, not a receiver: traffic reaches it through a gateway, and this node is its own.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
PASCO-ACS_EOC heard by this node 1 RF — -18.2 dB — 16h 40m ago
Squid’s Base G2 heard by this node 1 RF — -15.8 dB — 14d 10h ago
!a6965010 heard by this node 1 RF — -17.5 dB — 14d 10h ago
Atlavox Cape Coral heard by this node 1 RF — relayed — not attributable — 16h 21m ago
!9ea03ba8 heard by this node 1 RF — relayed — not attributable — 16h 39m ago
Reading the hop budget. Every Meshtastic frame carries a hop limit that each relay decrements. A reception showing 0 left is one that arrived with nothing to spare — one more relay in the path and it would not have arrived at all. That is the closest this data comes to explaining a loss, and it is still not a loss: a frame that was dropped is exactly the one that never reached a gateway to be counted here.