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

Meshtastic 7bf0

!b2a77bf0 · updates every minute

powered 4.34 V · 73 min ago — this node reports itself externally powered rather than running on a battery.

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.

History

Heard on 62 days Sep 15 to Nov 15 · 62 active days · 2294 RF frames · 39 gateways

Sep 15 Nov 15

Most recent

CWP3Node 148m KQ4OOB - Base 603m ERM Gateway 675m KO4MFT 5ed4 815m Meshtastic eeff no pin 876m

Who heard it

Last 24 hours.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
CWP3Node 5 RF — relayed — not attributable — 2h 28m ago
KQ4OOB - Base 3 RF — hop distance not reported — 10h 3m ago
ERM Gateway 2 RF — relayed — not attributable — 11h 15m ago
KO4MFT 5ed4 1 RF — relayed — not attributable — 13h 35m ago
Meshtastic eeff 2 RF — relayed — not attributable — 14h 36m ago
FoxTastic-Home 1 RF — hop distance not reported — 17h 36m 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.