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

Meshtastic f540

!6985f540 · 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 18d 17h Oct 7 to Oct 27 · 18 active days · 31 RF frames · 2 gateways

Oct 7 Nov 15

Most recent

Home One no pin 26964m JDR_99 no pin 26969m !617b46f7 no pin 26970m Home Two no pin 26972m Meshtastic e9dc 27068m

Who heard it

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

Peer Frames Hops SNR (direct only) Hop budget left Last heard
Home One heard by this node 357 RF 0 8.2 dB … -5.0 5 18d 17h ago
JDR_99 heard by this node 73 RF 0 7.5 dB … 5.5 5 18d 17h ago
!617b46f7 heard by this node 371 RF 0 8.0 dB … 5.2 5 18d 17h ago
Home Two both ways 46 RF 0 7.2 dB … 4.0 5 18d 17h ago
Meshtastic e9dc heard by this node 122 RF — 8.0 dB … 5.2 — 18d 19h ago
Meshtastic LC8806 heard by this node 46 RF 0 7.8 dB … 5.2 5 19d 1h ago
!6fb51c44 heard by this node 56 RF 0 8.2 dB … 5.5 5 19d 4h ago
XMXa.v4 heard by this node 9 RF — -15.8 dB … -19.2 — 22d 8h ago
U2S1 heard by this node 1 RF — -18.0 dB — 27d 8h ago
K4FSG TallBoi discord.gg/floridamesh heard by this node 2 RF — -19.2 dB — 29d 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.