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

Meshtastic 6ac8

!433a6ac8 · 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 9d 10h Oct 30 to Nov 6 · 2 active days · 7 RF frames · 3 gateways

Oct 30 Nov 15

Most recent

Mandarin a37e💥 13571m BenClient 22456m

Who heard it

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

Peer Frames Hops SNR (direct only) Hop budget left Last heard
Mandarin a37e💥 1 RF — -1.2 dB — 9d 10h ago
BenClient 2 RF — -7.2 dB … -13.2 — 15d 14h 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.