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

KO4HXD-RAK SLR discord.gg/floridamesh

!fe5ad8c8 · updates every minute

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.

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 62 days Sep 15 to Nov 15 · 62 active days · 2329 RF frames · 38 gateways

Sep 15 Nov 15

Most recent

Peacock Point 119m KO4HXD- 2 119m Broadband Operations & Relay Gateway 299m Eagle3 476m ViVSoft.live MQTT Gateway 479m

Who heard it

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

Peer Frames Hops SNR (direct only) Hop budget left Last heard
KO4HXD- 2 245 RF — 8.0 dB … 5.0 — 1h 59m ago
K4FSG TallBoi discord.gg/floridamesh 4 RF — -9.5 dB … -16.0 — 7h 59m ago
Mesh Hunter 6 RF — -14.2 dB … -18.8 — 2d 23h ago
Solaris 22 RF — -3.2 dB … -11.0 — 9d 16h ago
Peacock Point 4 RF — relayed — not attributable — 1h 59m ago
Broadband Operations & Relay Gateway 1 RF — relayed — not attributable — 4h 59m ago
Eagle3 1 RF — relayed — not attributable — 7h 56m ago
ViVSoft.live MQTT Gateway 1 RF — relayed — not attributable — 7h 59m ago
Citrus Wood (mqtt) 1 RF — relayed — not attributable — 7h 59m ago
Moka 1 RF — relayed — not attributable — 13h 59m 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.