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

heybilly1

!f1b896f0 · updates every minute

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.

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 61 days Sep 15 to Nov 15 · 61 active days · 2637 RF frames · 5 gateways

Sep 15 Nov 15

Most recent

Moka 25m PersonaNonGrata [MQTT] [BOT] no pin 235m Broadband Operations & Relay Gateway 446m Meshtastic a165 488m

Who heard it

Last 24 hours.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
Moka 1007 RF — 1.0 dB … -18.2 — 25 min ago
PersonaNonGrata [MQTT] [BOT] 5 RF — relayed — not attributable — 3h 55m ago
Broadband Operations & Relay Gateway 1 RF — relayed — not attributable — 7h 26m ago
Meshtastic a165 1 RF — relayed — not attributable — 8h 8m 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.