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

kpt3

!522ea50d · 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 14 days Nov 2 to Nov 15 · 14 active days · 404 RF frames · 5 gateways

Nov 2 Nov 15

Most recent

kpt0 50m Apopka Home Base 1069m aes1 no pin 11090m kpt1 12727m ASG1 15130m

Who heard it

kpt stations first (2), then direct links. Last 24 hours, plus 4 direct link(s) heard earlier.

This node is a gateway. It has received 1 node(s) itself (1 RF frame(s)) and uplinks its own traffic straight to MQTT — so it is not heard by anything the way an ordinary node is. MQTT is the way out, not a receiver: traffic reaches it through a gateway, and this node is its own.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
kpt0 397 RF 0–2 9.0 dB … -13.8 1 50 min ago
kpt1 heard by this node 1 RF 0 6.0 dB 3 8d 20h ago
aes1 heard by this node 3 RF 0 6.5 dB … 3.8 3 7d 16h ago
ASG1 heard by this node 1 RF — 7.5 dB — 10d 12h ago
EL Attic 2 RF — -18.5 dB — 11d 14h ago
Apopka Home Base heard by this node 1 RF — relayed — not attributable — 17h 49m 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.