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

Fire 33

!f661e5a8 · firmware 2.7.26.54e0d8d · reports 95 node(s) online locally · updates every minute

66% 3.86 V · 10 h 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.

7 max hops — This station sets its traffic to be rebroadcast up to 7 times; the maximum Meshtastic allows. — this is what the station SETS, not how far away it is; the value is carried unchanged through every relay.

History

Heard on 39 days Sep 23 to Nov 15 · 39 active days · 245 RF frames · 19 gateways

Sep 23 Nov 15

Most recent

FoxTastic-Home 385m CWP3Node 607m ERM Gateway 607m IRE Base MQTT 1476m CommGuy Base - MeshAdv 1699m

Who heard it

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

Peer Frames Hops SNR (direct only) Hop budget left Last heard
IRE Base MQTT 24 RF — -5.2 dB … -14.5 — 1d 0h ago
CommGuy Base - MeshAdv 11 RF — -4.5 dB … -15.0 — 1d 4h ago
FoxTastic-Home 1 RF — hop distance not reported — 6h 25m ago
CWP3Node 1 RF — relayed — not attributable — 10h 7m ago
ERM Gateway 1 RF — hop distance not reported — 10h 7m 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.