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

Meshtastic f714

!a038f714 · 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 41 days Oct 6 to Nov 15 · 41 active days · 3361 RF frames · 25 gateways

Oct 6 Nov 15

Most recent

Meshtastic eeff no pin 13m FoxTastic-Home 270m KQ4OOB - Base 270m

Who heard it

Last 24 hours.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
Meshtastic eeff 2305 RF 0–1 11.8 dB … 9.0 2 13 min ago
FoxTastic-Home 2 RF — hop distance not reported — 4h 30m ago
KQ4OOB - Base 1 RF — hop distance not reported — 4h 30m 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.