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

K2ELI V4

!6985f458 · updates every minute

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.

This node advertises a name but no position, so it has no pin on the map. That is an ordinary state rather than a fault — a node broadcasts its identity on one schedule and its location only if its owner enabled that, and most of the mesh never does.

History

Heard on 39 days Sep 17 to Nov 15 · 39 active days · 211 RF frames · 21 gateways

Sep 17 Nov 15

Most recent

CWP3Node 390m Meshtastic eeff no pin 390m MTDL Base - MaxOffRoadin WRUV246 no pin 648m KQ4OOB - Base 729m ERM Gateway 731m

Who heard it

Last 24 hours.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
CWP3Node 2 RF — relayed — not attributable — 6h 30m ago
Meshtastic eeff 7 RF 1–2 relayed — not attributable 4 6h 30m ago
MTDL Base - MaxOffRoadin WRUV246 1 RF — relayed — not attributable — 10h 48m ago
KQ4OOB - Base 5 RF — hop distance not reported — 12h 9m ago
ERM Gateway 2 RF — hop distance not reported — 12h 11m 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.