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

Meshtastic 67d4

!e5a467d4 · updates every minute

5 max hops — This station sets its traffic to be rebroadcast up to 5 times; some frames went out with a smaller budget, as low as 3 — 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 26 days Sep 15 to Nov 15 · 26 active days · 518 RF frames · 8 gateways

Sep 15 Nov 15

Most recent

TTB Base ed94 19m JT HeltecV4 (MQTT) 98m BenClient 98m Mandarin a37e💥 99m

Who heard it

Last 24 hours.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
TTB Base ed94 207 RF 0 8.0 dB … 4.8 3 19 min ago
JT HeltecV4 (MQTT) 1 RF — relayed — not attributable — 1h 38m ago
BenClient 2 RF — relayed — not attributable — 1h 38m ago
Mandarin a37e💥 1 RF — relayed — not attributable — 1h 39m 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.