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

Yeraze Sandbox

!d8ee7714 · 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 1d 9h Sep 15 to Nov 14 · 57 active days · 2423 RF frames · 22 gateways

Sep 15 Nov 15

Most recent

Yeraze StationG2 🚉 23874m Yeraze BLE Sandbox no pin 25964m Meshtastic eeff no pin 27402m

Who heard it

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

Peer Frames Hops SNR (direct only) Hop budget left Last heard
Yeraze StationG2 🚉 heard by this node 244 RF — 11.8 dB … 7.5 — 16d 13h ago
Yeraze BLE Sandbox heard by this node 3 RF — 10.8 dB … 10.2 — 18d 0h ago
Meshtastic eeff 5 RF — 10.8 dB … 10.5 — 19d 0h 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.