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

!8125cd94

!8125cd94 · updates every minute

70% 3.89 V · 7 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 2 days Nov 14 to Nov 15 · 2 active days · 18 RF frames · 6 gateways

Nov 14 Nov 15

Most recent

IRE Base MQTT 440m ERM Base M2 Temp 473m Meshtastic eeff no pin 473m KQ4OOB - Base 499m CWP3Node 965m

Who heard it

Last 24 hours.

Peer Frames Hops SNR (direct only) Hop budget left Last heard
IRE Base MQTT 8 RF — relayed — not attributable — 7h 20m ago
ERM Base M2 Temp 1 RF — hop distance not reported — 7h 53m ago
Meshtastic eeff 5 RF — relayed — not attributable — 7h 53m ago
KQ4OOB - Base 1 RF — hop distance not reported — 8h 19m ago
CWP3Node 1 RF — relayed — not attributable — 16h 5m ago
ERM Gateway 1 RF — hop distance not reported — 20h 35m 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.