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

Meshtastic aaac

!49b5aaac · updates every minute

powered 4.33 V · 10 h ago — this node reports itself externally powered rather than running on a battery.

6 max hops — This station sets its traffic to be rebroadcast up to 6 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.

This node advertises a name but no position, so it has no pin on the map. That is an ordinary state rather than a fault — a node broadcasts its identity on one schedule and its location only if its owner enabled that, and most of the mesh never does.

History

Heard on 9 days Sep 21 to Nov 15 · 9 active days · 29 RF frames · 18 gateways

Sep 21 Nov 15

Most recent

Parrish Gateway 610m Just-a-mere Node 📵 610m Peacock Point 610m Citrus Wood (mqtt) 610m KO4HXD- 2 610m

Who heard it

Last 24 hours.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
Parrish Gateway 1 RF — relayed — not attributable — 10h 10m ago
Just-a-mere Node 📵 1 RF — relayed — not attributable — 10h 10m ago
Peacock Point 1 RF — relayed — not attributable — 10h 10m ago
Citrus Wood (mqtt) 1 RF — relayed — not attributable — 10h 10m ago
KO4HXD- 2 1 RF — relayed — not attributable — 10h 10m 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.