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

LWS MBL 4 HT TKR V2(2)

!64c394f1 · firmware 2.8.1.8e6a88d · reports 4 node(s) online locally · updates every minute

84% 4.01 V · 10 min ago

5 max hops — This station sets its traffic to be rebroadcast up to 5 times; above the default of 3. — this is what the station SETS, not how far away it is; the value is carried unchanged through every relay.

History

Heard on 48 days Sep 15 to Nov 15 · 48 active days · 1080 RF frames · 51 gateways

Sep 15 Nov 15

Most recent

👽 LWS ARC Area 51 Gat no pin 10m 👽 BB LAUNCH FACILITY 1 355m LWS ARC Shaun BASE 📵 4090m 👽 LWS ARC Area 51 Gateway 5950m FLMesh Seeed X1(1) 23949m

Who heard it

LWM stations first (3), then direct links. Last 24 hours, plus 16 direct link(s) heard earlier.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
LWS ARC Shaun Mobile 3 HT T096(1) heard by this node 17 RF — 6.8 dB … -18.8 — 16d 18h ago
FL Mesh MBL 1 RAK (1) heard by this node 4 RF — 7.0 dB … -16.0 — 19d 15h ago
FLMesh MBL 2 RAK 1W(1) heard by this node 4 RF — -5.0 dB … -8.5 — 24d 1h ago
👽 LWS ARC Area 51 Gat 33 RF — -16.5 dB … -20.5 — 10 min ago
LWS ARC Shaun BASE 📵 1 RF — -13.2 dB — 2d 20h ago
👽 LWS ARC Area 51 Gateway 99 RF — -14.2 dB … -20.2 — 4d 3h ago
FLMesh Seeed X1(1) heard by this node 542 RF 0 7.8 dB … -17.5 3 16d 15h ago
FLMesh TN M9 (1) heard by this node 112 RF 0 9.5 dB … 5.0 3 16d 15h ago
SunrisePlazaStation heard by this node 22 RF — 5.8 dB … -18.0 — 16d 16h ago
The Spirited Ham Home heard by this node 4 RF — -8.0 dB … -15.2 — 16d 19h ago
Mobile - K4HNH heard by this node 1 RF — -2.5 dB — 17d 14h ago
WATCHER heard by this node 1 RF — -18.8 dB — 17d 15h ago
St cloud Roman Router 4a04 heard by this node 1 RF — -14.0 dB — 19d 23h ago
LWS ARC Shaun BASE 📵 154 RF — 2.8 dB … -12.8 — 20d 0h ago
LWS ARC Shaun Gateway 📵 1 RF — -19.0 dB — 20d 19h ago
KQ4HDH N1 heard by this node 4 RF — -16.5 dB … -19.8 — 24d 5h ago
!9e7601a0 heard by this node 1 RF — -8.5 dB — 25d 19h ago
👽 BB LAUNCH FACILITY 1 1 RF — relayed — not attributable — 5h 55m 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.