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

LWS ARC HT T114 (3)

!dbc7f56f · updates every minute

93% 4.10 V · 15 days ago — telemetry is far patchier than position (only about a quarter of nodes send it at all), so an old reading here is ordinary rather than a sign of trouble.

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

Silent for 15d 10h Oct 17 to Oct 30 · 4 active days · 25 RF frames · 6 gateways

Oct 17 Nov 15

Most recent

FLMesh MBL 2 RAK 1W(1) 22208m LWS ARC Shaun BASE 📵 22210m FL Mesh HT V4R8 Kit(1) no pin 22266m FL Mesh MBL 1 RAK (1) 22298m FLMesh HT T190 (1) no pin 22303m

Who heard it

Last 24 hours, plus 8 direct link(s) heard earlier.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
FLMesh MBL 2 RAK 1W(1) both ways 25 RF 0 7.8 dB … 5.5 3 15d 10h ago
LWS ARC Shaun BASE 📵 7 RF 0 6.5 dB … 5.2 5 15d 10h ago
FL Mesh HT V4R8 Kit(1) heard by this node 3 RF — 7.2 dB … 6.2 — 15d 11h ago
FL Mesh MBL 1 RAK (1) heard by this node 2 RF — 6.5 dB … 6.0 — 15d 11h ago
FLMesh HT T190 (1) 12 RF 0 7.2 dB … 2.2 5 15d 11h ago
SunrisePlazaStation heard by this node 2 RF — -18.5 dB … -19.2 — 15d 13h ago
LWS ARC Shaun Mobile 3 HT T096(1) heard by this node 1 RF — 6.2 dB — 15d 23h ago
LWS ARC Shaun Gateway 📵 1 RF — 6.2 dB — 29d 7h 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.