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

FLMesh MBL 2 RAK 1W(1)

!a30cd684 · updates every minute

32% 3.56 V · 7 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

Heard once, on Nov 7 first heard Nov 7 · 1 active day · 2 RF frames · 2 gateways

Nov 7 Nov 15

Most recent

FL Mesh MBL 1 RAK (1) 10733m LWS ARC Shaun BASE 📵 10743m LWS ARC Shaun Gateway 📵 10748m

Who heard it

LWM stations first (1), then direct links. Last 24 hours, plus 3 direct link(s) heard earlier.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
FL Mesh MBL 1 RAK (1) heard by this node 1 RF — 6.2 dB — 7d 10h ago
LWS ARC Shaun BASE 📵 1 RF — 6.0 dB — 7d 11h ago
LWS ARC Shaun Gateway 📵 1 RF 0 6.0 dB 5 7d 11h 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.