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

ArgusNavis

!4d98b39c · updates every minute

87% 4.03 V · 8 h ago — telemetry is far patchier than position (only about a quarter of nodes send it at all), so an old reading here is ordinary rather than a sign of trouble.

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

History

Heard on 24 days Sep 16 to Nov 15 · 24 active days · 145 RF frames · 28 gateways

Sep 16 Nov 15

Most recent

K4EX_MQTT 434m Rockridge Base 🏭 434m Magi-Mesh aea4 490m Moka 490m TF-ApolloBeach-G2 (Not Monitored) no pin 1395m

Who heard it

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

This node is a gateway. It has received 1 node(s) itself (1 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 bd34 9 RF — -18.8 dB … -20.8 — 7d 19h ago
K4EX_MQTT 1 RF — relayed — not attributable — 7h 14m ago
Rockridge Base 🏭 1 RF — relayed — not attributable — 7h 14m ago
Magi-Mesh aea4 1 RF — relayed — not attributable — 8h 10m ago
Moka 1 RF — relayed — not attributable — 8h 10m ago
TF-ApolloBeach-G2 (Not Monitored) heard by this node 1 RF — relayed — not attributable — 23h 15m 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.