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

KE4JQ MOB1W

!77af3b4d · updates every minute

82% 4.01 V · 1 h ago

6 max hops — This station sets its traffic to be rebroadcast up to 6 times; some frames went out with a smaller budget, as low as 5 — Meshtastic spends fewer hops on a reply than on a broadcast, so this is the reply economy rather than a second setting; 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 60 days Sep 15 to Nov 15 · 60 active days · 2678 RF frames · 33 gateways

Sep 15 Nov 15

Most recent

Meshtastic eeff no pin 8m FoxTastic-Home 331m ERM Gateway 433m Rene WRKS539 467m KQ4OOB - Base 467m

Who heard it

Last 24 hours.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
Meshtastic eeff 11 RF — relayed — not attributable — 8 min ago
FoxTastic-Home 2 RF — hop distance not reported — 5h 31m ago
ERM Gateway 7 RF — hop distance not reported — 7h 13m ago
Rene WRKS539 1 RF — hop distance not reported — 7h 47m ago
KQ4OOB - Base 5 RF — hop distance not reported — 7h 47m ago
ERM Base M2 Temp 5 RF — relayed — not attributable — 8h 23m ago
CWP3Node 2 RF — relayed — not attributable — 8h 23m 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.