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

JUP G2

!16ced214 · updates every minute

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

6 max hops — This station sets its traffic to be rebroadcast up to 6 times; some frames went out with a smaller budget, as low as 5 — 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 62 days Sep 15 to Nov 15 · 62 active days · 2582 RF frames · 33 gateways

Sep 15 Nov 15

Most recent

Meshtastic eeff no pin 14m IRE Base MQTT 133m ERM Base M2 Temp 496m KO4MFT 5ed4 497m KQ4OOB - Base 497m

Who heard it

Last 24 hours.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
Meshtastic eeff 19 RF — 11.0 dB … 10.2 — 14 min ago
IRE Base MQTT 1 RF — relayed — not attributable — 2h 13m ago
ERM Base M2 Temp 2 RF — relayed — not attributable — 8h 16m ago
KO4MFT 5ed4 2 RF — relayed — not attributable — 8h 17m ago
KQ4OOB - Base 2 RF — hop distance not reported — 8h 17m ago
FoxTastic-Home 2 RF — hop distance not reported — 14h 13m ago
ERM Gateway 2 RF — relayed — not attributable — 16h 14m 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.