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

GAT562 affc mangomesh

!ed6baffc · updates every minute

7 max hops — This station sets its traffic to be rebroadcast up to 7 times; the maximum Meshtastic allows. — this is what the station SETS, not how far away it is; the value is carried unchanged through every relay.

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

Heard on 34 days Oct 7 to Nov 15 · 34 active days · 306 RF frames · 20 gateways

Oct 7 Nov 15

Most recent

ERM Base M2 Temp 438m KQ4OOB - Base 978m

Who heard it

Last 24 hours.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
ERM Base M2 Temp 1 RF — relayed — not attributable — 7h 18m ago
KQ4OOB - Base 2 RF — hop distance not reported — 16h 18m 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.