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

KZ4NG - FLMesh

!1de92388 · firmware 2.7.15.567b8ea · reports 6 node(s) online locally · updates every minute

History

Heard once, on Oct 20 first heard Oct 20 · 1 active day · 1 RF frame · 1 gateway

Oct 20 Nov 15

Most recent

KZ4NG - Actual no pin 222m !433c44cc 304m KZ4NG - Treetops no pin 341m LWS ARC Altamonte Gateway 586m W⚓ 980m

Who heard it

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

This node is a gateway. It has received 7 node(s) itself (22 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
KZ4NG - Treetops heard by this node 253 RF — 7.5 dB … 5.2 — 5h 41m ago
KZ4NG - Actual heard by this node 137 RF — 7.8 dB … 5.2 — 3h 42m ago
TCHK - MQTT heard by this node 8 RF — 8.5 dB … 6.8 — 2d 9h ago
!433c44cc heard by this node 3 RF — relayed — not attributable — 5h 4m ago
LWS ARC Altamonte Gateway heard by this node 1 RF — relayed — not attributable — 9h 46m ago
W⚓ heard by this node 1 RF — relayed — not attributable — 16h 20m ago
!d182fb61 heard by this node 1 RF — relayed — not attributable — 16h 52m ago
TrackerKeeper_01 heard by this node 2 RF — relayed — not attributable — 16h 52m 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.