Glossary
Moving time and elapsed time
Elapsed time is start to finish on the clock. Moving time subtracts the parts where you stopped. The gap explains most 2-app pace disagreements.
What it is
Two clocks for one run.
Elapsed time runs from the moment you press start to the moment you press stop. Traffic lights, water stops and shoelaces are all in it.
Moving time removes the periods where the software decided you were not moving. Each app picks its own speed threshold for that decision.
| Run | Elapsed | Moving | Pace shown |
|---|---|---|---|
| 10 km, no stops | 55:00 | 55:00 | 5:30/km (8:51/mi) |
| 10 km, 3 min at lights | 58:00 | 55:00 | 5:30 or 5:48/km |
What it is not
It is not your race time. Races are scored on elapsed time from the gun or the mat, so a personal best set on moving time is not comparable.
It is also not consistent between apps. The threshold that counts as stopped differs, which is why the same file can produce two different paces.
What moves it
- Traffic and crossings. Urban runs have the biggest gap.
- The auto-pause setting. On or off changes the recorded numbers.
- Slow uphill walking. Some thresholds count it as stopped.
- Which app you look at. Same data, different rule.
When to ignore it
Ignore moving time when you are comparing yourself to a race result. Use elapsed.
Ignore the gap altogether on a track or a treadmill, where you did not stop.