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

Meshtastic 7824

!ce327824 · firmware 2.7.26.54e0d8d · reports 3 node(s) online locally · updates every minute

History

Silent for 3d 13h Oct 2 to Nov 11 · 34 active days · 410 RF frames · 6 gateways

Oct 2 Nov 15

Most recent

ObservationNodev2.0 no pin 641m Beanfield G3 Filtered 5109m Beanfield 🐊 flme.sh 8529m Beanfield G3 12489m

Who heard it

Last 24 hours, plus 3 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
ObservationNodev2.0 heard by this node 3 RF 0 10.8 dB … 9.8 2 10h 41m ago
Beanfield G3 Filtered 6 RF — -16.2 dB … -19.8 — 3d 13h ago
Beanfield 🐊 flme.sh 5 RF — -16.2 dB … -18.8 — 5d 22h ago
Beanfield G3 3 RF — -18.5 dB … -19.0 — 8d 16h 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.