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

Shades Base dd3e

!99bddd3e · firmware 2.7.26.54e0d8d · reports 6 node(s) online locally · updates every minute

History

Silent for 13d 23h Oct 27 to Nov 2 · 4 active days · 9 RF frames · 2 gateways

Oct 27 Nov 16

Most recent

Shades Blue 6af8 no pin 28216m SB0 SW Gainesville 32381m Json18-XiaoGator_Vist Fl-Mesh.org 33814m sm Attic Heltec v3 b850 36185m tvrd bc50 🗼 36215m

Who heard it

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

Peer Frames Hops SNR (direct only) Hop budget left Last heard
Shades Blue 6af8 heard by this node 1 RF — 5.8 dB — 19d 14h ago
SB0 SW Gainesville heard by this node 30 RF — -7.8 dB … -19.8 — 22d 11h ago
Json18-XiaoGator_Vist Fl-Mesh.org heard by this node 1 RF — -18.2 dB — 23d 11h ago
sm Attic Heltec v3 b850 heard by this node 1 RF — -17.8 dB — 25d 3h ago
tvrd bc50 🗼 heard by this node 1 RF — -20.5 dB — 25d 3h ago
Meshtastic 1585 heard by this node 1 RF — -16.8 dB — 26d 0h ago
K3DO T-Beam 3 heard by this node 1 RF — -16.5 dB — 26d 3h 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.