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

Yeraze BLE Sandbox

!384df6f7 · updates every minute

2 max hops — This station sets its traffic to be rebroadcast up to 2 times; below the default of 3. — 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 50 days Sep 16 to Nov 14 · 50 active days · 295 RF frames · 12 gateways

Sep 16 Nov 15

Most recent

KQ4OOB - Base 1213m ERM Gateway 1393m Yeraze StationG2 🚉 23951m Yeraze Sandbox no pin 26055m

Who heard it

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

Peer Frames Hops SNR (direct only) Hop budget left Last heard
Yeraze StationG2 🚉 heard by this node 319 RF — 12.0 dB … 9.8 — 16d 15h ago
Yeraze Sandbox 3 RF — 10.8 dB … 10.2 — 18d 2h ago
KQ4OOB - Base 1 RF — relayed — not attributable — 20h 13m ago
ERM Gateway 1 RF — hop distance not reported — 23h 13m 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.