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

Meshtastic 7c54 Wind

!69857c54 · firmware 2.7.15.567b8ea · reports 7 node(s) online locally · updates every minute

History

Silent for 1d 12h Sep 21 to Nov 13 · 10 active days · 39 RF frames · 10 gateways

Sep 21 Nov 15

Most recent

Meshtastic 9a20 no pin 50m Meshtastic 3358 Base 57m Pocket Pool 99m Atlavox Cape Coral 526m ☀️ Sacred Water 819m

Who heard it

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

This node is a gateway. It has received 5 node(s) itself (33 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 3358 Base both ways 2090 RF — 8.2 dB … 5.0 — 57 min ago
Meshtastic 5f0f heard by this node 101 RF — -7.0 dB … -19.8 — 2d 23h ago
Meshtastic 9a20 heard by this node 15 RF — relayed — not attributable — 50 min ago
Pocket Pool heard by this node 10 RF — relayed — not attributable — 1h 39m ago
Atlavox Cape Coral heard by this node 1 RF — relayed — not attributable — 8h 46m ago
☀️ Sacred Water heard by this node 1 RF — relayed — not attributable — 13h 39m 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.