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

CUTLER G2

!16db2cd8 · updates every minute

powered 89 min ago — this node reports itself externally powered rather than running on a battery.

5 max hops — This station sets its traffic to be rebroadcast up to 5 times; some frames went out with a smaller budget, as low as 4 — Meshtastic spends fewer hops on a reply than on a broadcast, so this is the reply economy rather than a second setting; 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 63 days Sep 15 to Nov 16 · 63 active days · 2435 RF frames · 46 gateways

Sep 15 Nov 16

Most recent

Meshtastic eeff no pin 88m FoxTastic-Home 88m KQ4OOB - Base 113m CommGuy Base - MeshAdv 208m CWP3Node 807m

Who heard it

Last 24 hours.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
Meshtastic eeff 3 RF — relayed — not attributable — 1h 28m ago
FoxTastic-Home 17 RF — hop distance not reported — 1h 28m ago
KQ4OOB - Base 3 RF — hop distance not reported — 1h 53m ago
CommGuy Base - MeshAdv 3 RF — relayed — not attributable — 3h 28m ago
CWP3Node 3 RF — relayed — not attributable — 13h 27m 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.