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

Meshtastic f79e

!5ac8f79e · updates every minute

History

Silent for 1d 19h Oct 27 to Nov 13 · 5 active days · 19 RF frames · 9 gateways

Oct 27 Nov 15

Most recent

K3DO T-Beam 2 no pin 124m Meshymoor (DM /play) 8007m Tank Station 8158m Meshtastic c288 8241m Meshtastic c490 26423m

Who heard it

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

This node is a gateway. It has received 1 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
Meshymoor (DM /play) heard by this node 3 RF — -10.8 dB — 5d 13h ago
Tank Station heard by this node 1 RF — -12.0 dB — 5d 15h ago
Meshtastic c288 heard by this node 3 RF — -12.8 dB … -16.0 — 5d 17h ago
Meshtastic c490 heard by this node 15 RF — 7.0 dB … 5.8 — 18d 8h ago
North PP Solar heard by this node 1 RF — -5.8 dB — 18d 23h ago
KQ4SNEPiHat heard by this node 1 RF — -19.2 dB — 19d 15h ago
W4MSN portable heard by this node 3 RF — 2.8 dB … -13.2 — 22d 15h ago
K3DO T-Beam 2 heard by this node 2 RF — relayed — not attributable — 2h 4m 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.