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

MT_HTV4_MOBILE1

!49b5a98c · updates every minute

History

Silent for 8d 11h Sep 28 to Nov 6 · 9 active days · 32 RF frames · 5 gateways

Sep 28 Nov 15

Most recent

MT_TLH_LKSHR 3598m MT_HTV4_2VCJ$D no pin 3598m Meshtastic 538f 13726m K4KHCmESH4 15146m Maclay Mesh 1 21644m

Who heard it

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

Peer Frames Hops SNR (direct only) Hop budget left Last heard
MT_HTV4_2VCJ$D heard by this node 532 RF — 8.0 dB … 4.8 — 2d 11h ago
MT_TLH_LKSHR heard by this node 645 RF — 8.2 dB … -4.5 — 2d 11h ago
Meshtastic 538f heard by this node 23 RF — 2.2 dB … -15.0 — 9d 12h ago
K4KHCmESH4 heard by this node 4 RF — -2.5 dB … -11.0 — 10d 12h ago
Maclay Mesh 1 heard by this node 74 RF — -16.8 dB … -20.8 — 15d 0h ago
Meshtastic 3df8 heard by this node 5 RF — -3.2 dB … -12.8 — 16d 19h ago
HighPoint_57da 6 RF — -7.5 dB … -18.0 — 24d 15h ago
Mandarin a37e💥 2 RF — 3.0 dB … 1.2 — 29d 17h 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.