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

aes1

!1ba67494 · updates every minute

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 once, on Nov 7 first heard Nov 7 · 1 active day · 3 RF frames · 1 gateway

Nov 7 Nov 15

Most recent

kpt3 no pin 11087m aes0 11915m

Who heard it

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

Peer Frames Hops SNR (direct only) Hop budget left Last heard
aes0 heard by this node 7 RF 0 7.0 dB … 5.8 3 8d 6h ago
kpt3 3 RF 0 6.5 dB … 3.8 3 7d 16h 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.