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

d3fm0nk3y

!6666da38 · updates every minute

6 max hops — This station sets its traffic to be rebroadcast up to 6 times; 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.

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 5 days Oct 30 to Nov 16 · 5 active days · 38 RF frames · 12 gateways

Oct 30 Nov 16

Most recent

👽 LWS ARC Area 51 Gat no pin 67m 👽 BUZZ BASE LAUNCH FACILITY SOLAR 379m BB LAUNCH FACILITY 3 742m Trefulo 2 no pin 832m Pi3 MeshtasticD no pin 852m

Who heard it

Last 24 hours.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
👽 BUZZ BASE LAUNCH FACILITY SOLAR 2 RF — -9.2 dB … -10.5 — 6h 19m ago
👽 LWS ARC Area 51 Gat 9 RF — relayed — not attributable — 1h 7m ago
BB LAUNCH FACILITY 3 1 RF — relayed — not attributable — 12h 22m ago
Trefulo 2 1 RF — relayed — not attributable — 13h 52m ago
Pi3 MeshtasticD 1 RF — relayed — not attributable — 14h 12m ago
It'sa me, MeshWio 1 RF — relayed — not attributable — 14h 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.