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

W0LZ-M7

!7574ae24 · 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

SunrisePlazaStation 853m KO4RTY Portable/Mobile 2138m W0LZ-T1000E 4384m Gum Lake Fixed Node(Not Monitored) 4745m Meshtastic b1d1 4747m

Who heard it

w0l stations first (1), then direct links. Last 24 hours, plus 8 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
W0LZ-T1000E heard by this node 79 RF — 12.5 dB … 7.2 — 3d 1h ago
SunrisePlazaStation heard by this node 2 RF — -19.0 dB — 14h 13m ago
KO4RTY Portable/Mobile heard by this node 91 RF — 5.0 dB … -20.0 — 1d 11h ago
Gum Lake Fixed Node(Not Monitored) heard by this node 1 RF — -18.5 dB — 3d 7h ago
Meshtastic b1d1 heard by this node 2 RF — -14.0 dB … -15.5 — 3d 7h ago
Meshtastic 75f5 heard by this node 1 RF — -13.2 dB — 3d 7h ago
Swank heard by this node 1 RF — -18.2 dB — 8d 16h ago
!5d4810ac heard by this node 1 RF 0 -19.2 dB 3 15d 10h ago
IronLion heard by this node 1 RF 0 -19.8 dB 3 18d 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.