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

Quietflight00

!69852978 · firmware 2.7.26.54e0d8d · reports 7 node(s) online locally · updates every minute

History

Silent for 1d 14h Sep 15 to Nov 13 · 60 active days · 2392 RF frames · 1 gateway

Sep 15 Nov 15

Most recent

Basecamp 462m Greyhound06 467m Giraffe 493m K5LD Station 684m !4dd13869 no pin 925m

Who heard it

Last 24 hours.

This node is a gateway. It has received 6 node(s) itself (60 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
Basecamp both ways 958 RF 0 8.0 dB … 4.0 2 7h 42m ago
Greyhound06 heard by this node 16 RF — relayed — not attributable — 7h 47m ago
Giraffe heard by this node 11 RF — relayed — not attributable — 8h 13m ago
K5LD Station heard by this node 8 RF — relayed — not attributable — 11h 24m ago
!4dd13869 heard by this node 1 RF — relayed — not attributable — 15h 25m ago
wj4dx home heard by this node 1 RF — relayed — not attributable — 16h 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.