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

Meshtastic 3358 Base

!69843358 · firmware 2.7.15.567b8ea · reports 5 node(s) online locally · updates every minute

powered 4.38 V · 2 days ago — this node reports itself externally powered rather than running on a battery.

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

History

Heard on 62 days Sep 15 to Nov 15 · 62 active days · 6085 RF frames · 22 gateways

Sep 15 Nov 15

Most recent

Meshtastic 7c54 Wind 56m Meshtastic 9a20 no pin 229m SYSTRON no pin 580m Meshtastic 5f0f no pin 5753m

Who heard it

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

This node is a gateway. It has received 2 node(s) itself (2 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
Meshtastic 7c54 Wind both ways 2090 RF — 8.2 dB … 5.0 — 56 min ago
Meshtastic 5f0f heard by this node 3 RF — -5.5 dB … -7.5 — 3d 23h ago
Meshtastic 9a20 heard by this node 1 RF — relayed — not attributable — 3h 49m ago
SYSTRON heard by this node 1 RF — relayed — not attributable — 9h 40m 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.