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

KZ4DE V4

!b29fa9c4 · updates every minute

7 max hops — This station sets its traffic to be rebroadcast up to 7 times; the maximum Meshtastic allows. — 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 · 887 RF frames · 32 gateways

Sep 15 Nov 15

Most recent

KQ4OOB - Base 49m CommGuy Base - MeshAdv 106m Meshtastic eeff no pin 106m CWP3Node 207m FoxTastic-Home 272m

Who heard it

Last 24 hours.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
KQ4OOB - Base 33 RF — hop distance not reported — 49 min ago
CommGuy Base - MeshAdv 4 RF — relayed — not attributable — 1h 46m ago
Meshtastic eeff 6 RF — relayed — not attributable — 1h 46m ago
CWP3Node 5 RF — relayed — not attributable — 3h 27m ago
FoxTastic-Home 10 RF — hop distance not reported — 4h 32m ago
ERM Base M2 Temp 8 RF — relayed — not attributable — 11h 7m 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.