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

ASG1

!d8e4ac15 · 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.

Most recent

Meshtastic 9a93 903m KO4RTY Portable/Mobile 2337m !d544f1ea 2485m AW-Node-03 2586m Meshtastic 7a78 4174m

Who heard it

Last 24 hours, plus 7 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
Meshtastic 9a93 heard by this node 3 RF — -10.5 dB … -17.5 — 15h 3m ago
KO4RTY Portable/Mobile heard by this node 2 RF — -9.8 dB — 1d 14h ago
!d544f1ea heard by this node 1 RF — -3.5 dB — 1d 17h ago
AW-Node-03 heard by this node 1 RF — -10.0 dB — 1d 19h ago
Meshtastic 7a78 heard by this node 1 RF — -16.8 dB — 2d 21h ago
W3PTT heard by this node 1 RF — -16.2 dB — 4d 18h ago
Apopka Home Base heard by this node 1 RF — 3.2 dB — 4d 18h ago
Meshtastic 78d0 heard by this node 1 RF — -14.5 dB — 7d 22h 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.