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

BURGER

!8fa1e2fc · updates every minute

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

Nov 13 Nov 15

Most recent

kpt0 447m JT HeltecV4 (MQTT) 728m EL Attic 789m It'sa me, MeshWio 1133m K4FSG TallBoi discord.gg/floridamesh 2238m

Who heard it

Last 24 hours, plus 2 direct link(s) heard earlier.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
EL Attic 3 RF — -12.8 dB … -18.0 — 13h 9m ago
K4FSG TallBoi discord.gg/floridamesh 1 RF — -17.2 dB — 1d 13h ago
Eagle3 1 RF — 3.5 dB — 1d 14h ago
kpt0 1 RF — relayed — not attributable — 7h 27m ago
JT HeltecV4 (MQTT) 2 RF — relayed — not attributable — 12h 8m ago
It'sa me, MeshWio 1 RF — relayed — not attributable — 18h 53m 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.