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

🌎NE4LS-1 V3🌎

!fa68b108 Β· updates every minute

powered 4.30 V Β· 33 days ago β€” this node reports itself externally powered rather than running on a battery.

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 7 days Oct 10 to Nov 14 Β· 7 active days Β· 25 RF frames Β· 11 gateways

Oct 10 Nov 15

Most recent

FoxTastic-Home 857m KO4MFT 5ed4 857m ERM Gateway 857m

Who heard it

Last 24 hours.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
FoxTastic-Home 1 RF β€” hop distance not reported β€” 14h 17m ago
KO4MFT 5ed4 1 RF β€” hop distance not reported β€” 14h 17m ago
ERM Gateway 1 RF β€” hop distance not reported β€” 14h 17m 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.