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

HighPoint_57da

!ccaf02fa · 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 24d 17h Sep 28 to Oct 21 · 3 active days · 3 RF frames · 1 gateway

Sep 28 Nov 15

Most recent

MT_HTV4_MOBILE1 35491m Meshtastic 3df8 35579m Meshtastic 538f 35584m shadshack-solar-node 36965m

Who heard it

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

Peer Frames Hops SNR (direct only) Hop budget left Last heard
MT_HTV4_MOBILE1 heard by this node 6 RF — -7.5 dB … -18.0 — 24d 15h ago
Meshtastic 3df8 heard by this node 2 RF — -5.8 dB … -10.8 — 24d 16h ago
Meshtastic 538f heard by this node 10 RF — 1.0 dB … -13.5 — 24d 17h ago
shadshack-solar-node heard by this node 1 RF — -17.8 dB — 25d 16h 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.