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

Moth3rship

!49b3dabc · firmware 2.7.15.567b8ea · reports 53 node(s) online locally · updates every minute

powered 4.35 V · 4 h ago — this node reports itself externally powered rather than running on a battery.

3 max hops — This station sets its traffic to be rebroadcast up to 3 times; the firmware default. — this is what the station SETS, not how far away it is; the value is carried unchanged through every relay.

History

Heard on 19 days Sep 15 to Nov 15 · 19 active days · 344 RF frames · 11 gateways

Sep 15 Nov 15

Most recent

av8or 19m Morpheus 142m Niobi 825m therealsamflynn 22871m Icarus1 no pin 42927m

Who heard it

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

This node is a gateway. It has received 2 node(s) itself (3 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
av8or both ways 426 RF 0 8.0 dB … -3.8 3 19 min ago
therealsamflynn heard by this node 30 RF 0 7.8 dB … 5.8 3 15d 21h ago
Icarus1 heard by this node 2 RF 0 7.0 dB … 6.0 3 29d 19h ago
Morpheus heard by this node 1 RF 3 relayed — not attributable 2 2h 22m ago
Niobi heard by this node 2 RF 3 relayed — not attributable 2 13h 45m 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.