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

ObservationNodev2.0

!4f622c12 · updates every minute

7 max hops — This station sets its traffic to be rebroadcast up to 7 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 maximum Meshtastic allows. — 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 7 days Oct 12 to Nov 15 · 7 active days · 306 RF frames · 9 gateways

Oct 12 Nov 15

Most recent

Beanfield 🐊 flme.sh 4m david79-uconsole 26m Parrish Gateway 26m ViVSoft.live MQTT Gateway 110m Meshtastic 7824 603m

Who heard it

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

Peer Frames Hops SNR (direct only) Hop budget left Last heard
Beanfield 🐊 flme.sh 68 RF 0 -10.0 dB … -20.2 2 4 min ago
Meshtastic 7824 3 RF 0 10.8 dB … 9.8 2 10h 3m ago
Beanfield G3 Filtered 82 RF — -10.5 dB … -20.0 — 3d 10h ago
david79-uconsole 6 RF — relayed — not attributable — 26 min ago
Parrish Gateway 27 RF 1 relayed — not attributable 1 26 min ago
ViVSoft.live MQTT Gateway 2 RF — relayed — not attributable — 1h 50m 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.