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

L0g.relay

!1156b3de · updates every minute

3 max hops — This station sets its traffic to be rebroadcast up to 3 times; the firmware default. — 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 17 days Oct 28 to Nov 14 · 17 active days · 146 RF frames · 23 gateways

Oct 28 Nov 15

Most recent

KR4CKW-BASE 724m SN MQTT Gateway no pin 724m K4FSG TallBoi discord.gg/floridamesh 724m Eagle3 1259m K4EX_MQTT 1263m

Who heard it

Last 24 hours.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
K4FSG TallBoi discord.gg/floridamesh 5 RF — -12.2 dB … -13.8 — 12h 4m ago
KR4CKW-BASE 1 RF — relayed — not attributable — 12h 4m ago
SN MQTT Gateway 2 RF — relayed — not attributable — 12h 4m ago
Eagle3 1 RF — relayed — not attributable — 20h 59m ago
K4EX_MQTT 1 RF — relayed — not attributable — 21h 3m 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.