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

K3DO T-Beam 3

!7a6d7634 · updates every minute

3 max hops — This station sets its traffic to be rebroadcast up to 3 times; 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 13 days Sep 27 to Nov 16 · 13 active days · 22 RF frames · 7 gateways

Sep 27 Nov 16

Most recent

!bdc67fa7 no pin 549m Shades Base dd3e 37630m

Who heard it

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

Peer Frames Hops SNR (direct only) Hop budget left Last heard
Shades Base dd3e 1 RF — -16.5 dB — 26d 3h ago
!bdc67fa7 1 RF — relayed — not attributable — 9h 9m 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.