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

Meshtastic bae1

!bb9fbae1 · updates every minute

93% 4.10 V · 5 days ago — telemetry is far patchier than position (only about a quarter of nodes send it at all), so an old reading here is ordinary rather than a sign of trouble.

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 5d 13h Oct 27 to Nov 10 · 14 active days · 247 RF frames · 23 gateways

Oct 27 Nov 16

Most recent

Moka 8019m

Who heard it

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

Peer Frames Hops SNR (direct only) Hop budget left Last heard
Moka 46 RF 0–6 6.2 dB … -20.2 1 5d 13h 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.