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

Home One

!188d8083 · updates every minute

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.

History

Silent for 16d 23h Oct 6 to Oct 29 · 17 active days · 1641 RF frames · 6 gateways

Oct 6 Nov 15

Most recent

Home Two no pin 24469m JDR_99 no pin 24529m Meshtastic f540 no pin 26966m !617b46f7 no pin 31150m

Who heard it

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

Peer Frames Hops SNR (direct only) Hop budget left Last heard
Home Two 547 RF 0–1 8.2 dB … 5.2 4 16d 23h ago
JDR_99 25 RF 0 11.2 dB … 9.0 5 17d 0h ago
Meshtastic f540 357 RF 0 8.2 dB … -5.0 5 18d 17h ago
!617b46f7 1 RF 0 9.8 dB 5 21d 15h 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.