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

Flotilla 59

!f88503c2 · firmware 2.7.26.54e0d8d · reports 12 node(s) online locally · updates every minute

96% 4.13 V · 57 min ago

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.

History

Heard on 33 days Oct 3 to Nov 15 · 33 active days · 767 RF frames · 21 gateways

Oct 3 Nov 15

Most recent

CWP3Node 56m IRE Base MQTT 56m FoxTastic-Home 143m Meshtastic eeff no pin 236m ERM Gateway 359m

Who heard it

Last 24 hours.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
CWP3Node 4 RF — relayed — not attributable — 56 min ago
IRE Base MQTT 8 RF — relayed — not attributable — 56 min ago
FoxTastic-Home 2 RF — hop distance not reported — 2h 23m ago
Meshtastic eeff 4 RF — relayed — not attributable — 3h 56m ago
ERM Gateway 3 RF — hop distance not reported — 5h 59m ago
KO4MFT 5ed4 1 RF — hop distance not reported — 12h 56m ago
CommGuy Base - MeshAdv 1 RF — relayed — not attributable — 13h 9m ago
ERM Base M2 Temp 2 RF — hop distance not reported — 20h 12m 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.