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

LuminousElements

!1ba2818c · firmware 2.7.26.54e0d8d · reports 18 node(s) online locally · updates every minute

powered 4.37 V · 23 days ago — this node reports itself externally powered rather than running on a battery.

History

Silent for 23d 3h Oct 5 to Oct 23 · 7 active days · 45 RF frames · 9 gateways

Oct 5 Nov 15

Most recent

Morpheus 33313m Nebuchadnezzar 33325m Trashburner 33344m Niobi 33382m Meshtastic 7028 no pin 34090m

Who heard it

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

Peer Frames Hops SNR (direct only) Hop budget left Last heard
Morpheus heard by this node 404 RF 0 8.8 dB … 5.0 2 23d 3h ago
Nebuchadnezzar 2 RF — 7.8 dB … 6.2 — 23d 3h ago
Trashburner heard by this node 75 RF — -16.0 dB … -21.0 — 23d 3h ago
Niobi 26 RF — 10.5 dB … 7.0 — 23d 4h ago
Meshtastic 7028 heard by this node 91 RF — -7.2 dB … -20.0 — 23d 16h ago
KQ4SNEPiHat heard by this node 4 RF — -19.5 dB … -21.2 — 24d 19h ago
KQ4SNE mini heard by this node 1 RF — -18.8 dB — 27d 1h ago
SutMesh Base KQ4SNE heard by this node 2 RF — -20.2 dB — 28d 23h 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.