On the details of an activity, you see two durations: elapsed time and moving time. The first is the raw stopwatch, the second removes your stops. Moving time is the one used for average pace and speed.
Elapsed time
This is the time between the first and the last timestamped point of your trace, stops included. Without usable timestamps, Konquo falls back on the duration recorded by the app or by your watch or GPS bike computer.
Moving time
Konquo looks at every interval between two consecutive GPS points and only keeps those covered fast enough.
On an imported activity (watch or GPS bike computer, GPX or FIT file), a gap of more than 10 s between two points when running, or more than 30 s when cycling, is treated as an automatic pause of the device, even if the GPS drifted a little meanwhile. At the very start, points that exactly repeat the starting position (the device is waiting for its GPS signal while you have already set off) count as moving.
What about the Konquo app?
The app has no automatic pause. The pause button stops its stopwatch: if you stay where you are, that time counts in elapsed time but not in moving time. A GPS dropout in the middle of a run is counted if you were moving during it. If you stay still for a long time (10 min when running, 15 min when cycling), the app sends you a notification offering to finish.
The Moving time block (Konquo+)
The advanced analysis counts your stops with its own rule: a stop is at least 10 seconds in a row below 1.8 km/h. It shows the number of stops, the longest one and the share of time spent moving. Since the rule is different, this figure can differ a little from the moving time in the summary.
Moving time is the basis of all your averages.
Pace and speedWas this article helpful?
Log in to rate this article.
Log inStill got a question?
Our team replies on Discord or by email, in French and English.


