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

joey7b27

!139a7b27 · firmware 2.7.26.54e0d8d · reports 30 node(s) online locally · updates every minute

History

Silent for 22d 2h Sep 19 to Oct 24 · 11 active days · 30 RF frames · 2 gateways

Sep 19 Nov 15

Most recent

VBN Tampa Beacon 53m ☀️ Sacred Water 199m NF6P Shack 200m Trinity 267m d0ug-ClientBase 343m

Who heard it

Last 24 hours, plus 1 direct link(s) heard earlier.

This node is a gateway. It has received 8 node(s) itself (39 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
joey7b27 card heard by this node 138 RF 0 7.8 dB … 5.8 7 22d 11h ago
VBN Tampa Beacon heard by this node 3 RF — relayed — not attributable — 53 min ago
☀️ Sacred Water heard by this node 3 RF — relayed — not attributable — 3h 19m ago
NF6P Shack heard by this node 18 RF — relayed — not attributable — 3h 20m ago
Trinity heard by this node 1 RF — relayed — not attributable — 4h 27m ago
d0ug-ClientBase heard by this node 2 RF — relayed — not attributable — 5h 43m ago
CM Solar Seed heard by this node 1 RF — relayed — not attributable — 8h 37m ago
SpiderWeb heard by this node 4 RF — relayed — not attributable — 9h 2m ago
KO4RTY Portable/Mobile heard by this node 7 RF — relayed — not attributable — 12h 26m 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.