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

FLMesh MBL 3 HT T096(1)

!dbb1bc5d · updates every minute

5 max hops — This station sets its traffic to be rebroadcast up to 5 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 11 days Nov 5 to Nov 15 · 11 active days · 334 RF frames · 7 gateways

Nov 5 Nov 15

Most recent

LWS ARC Shaun BASE 📵 35m FLMesh HT T190 (1) no pin 81m 👽 LWS ARC Area 51 Gat no pin 851m LWS ARC Shaun Gateway 📵 6806m FLMesh MBL 2 RAK 1W(1) 12459m

Who heard it

LWM stations first (2), then direct links. Last 24 hours, plus 4 direct link(s) heard earlier.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
FLMesh MBL 2 RAK 1W(1) both ways 4 RF 0 7.5 dB … 6.0 5 8d 15h ago
FL Mesh MBL 1 RAK (1) both ways 3 RF 0 6.5 dB … 6.0 5 8d 18h ago
LWS ARC Shaun BASE 📵 86 RF 0 8.8 dB … 5.2 3 35 min ago
FLMesh HT T190 (1) 230 RF 0 8.0 dB … 5.5 3 1h 21m ago
👽 LWS ARC Area 51 Gat 4 RF 0 4.5 dB … -18.0 5 14h 11m ago
LWS ARC Shaun Gateway 📵 2 RF 0 6.8 dB … 5.8 5 4d 17h ago
LWS ARC Shaun BASE 📵 both ways 2 RF — 6.2 dB … 6.0 — 8d 18h 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.