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

Ninja 4bbc

!84554bbc · firmware 2.7.26.54e0d8d · reports 4 node(s) online locally · updates every minute

History

Heard once, on Oct 6 first heard Oct 6 · 1 active day · 3 RF frames · 1 gateway

Oct 6 Nov 15

Most recent

Json18-XiaoGator_Vist Fl-Mesh.org 3596m V2 Bleh no pin 8161m W4DFU Meshtastic - gatorradio.org 14015m Ninja 99cf no pin 28319m !3d383189 38562m

Who heard it

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

Peer Frames Hops SNR (direct only) Hop budget left Last heard
Json18-XiaoGator_Vist Fl-Mesh.org heard by this node 4 RF — -0.2 dB … -18.0 — 2d 11h ago
V2 Bleh heard by this node 1 RF — -8.0 dB — 5d 16h ago
W4DFU Meshtastic - gatorradio.org heard by this node 9 RF — -5.8 dB … -17.5 — 9d 17h ago
Ninja 99cf heard by this node 70 RF 0 12.0 dB … 8.5 2 19d 15h ago
!3d383189 heard by this node 1 RF — -17.5 dB — 26d 18h 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.