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

DD04-mt4

!9715bd33 · updates every minute

66% 3.86 V · 18 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 18d 15h Oct 16 to Oct 28 · 11 active days · 88 RF frames · 4 gateways

Oct 16 Nov 16

Most recent

DD-mt3 26832m DD-mt2 27224m

Who heard it

DD0 stations first (2), then direct links. Last 24 hours, plus 2 direct link(s) heard earlier.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
DD-mt3 74 RF — 7.8 dB … 5.2 — 18d 15h ago
DD-mt2 6 RF — 7.5 dB … 5.5 — 18d 21h 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.