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

Scopoletus

!2de021eb · firmware 2.7.26.54e0d8d · reports 15 node(s) online locally · updates every minute

92% 4.08 V · 24 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.

History

Silent for 24d 14h Sep 16 to Oct 21 · 35 active days · 1968 RF frames · 58 gateways

Sep 16 Nov 15

Most recent

BRAVADO 35674m Sleeping Beauty 37376m TestRig1 37498m TWEE 39714m WAZAHB 39980m

Who heard it

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

Peer Frames Hops SNR (direct only) Hop budget left Last heard
BRAVADO heard by this node 13 RF — 10.8 dB … -14.5 — 24d 18h ago
Sleeping Beauty both ways 319 RF — 12.2 dB … -17.2 — 25d 22h ago
TestRig1 heard by this node 1 RF — 8.2 dB — 26d 0h ago
TWEE 47 RF — 7.2 dB … 5.0 — 27d 13h ago
WAZAHB heard by this node 16 RF — 11.5 dB … -5.2 — 27d 18h ago
wj4dx home heard by this node 2 RF — -18.0 dB — 28d 19h 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.