RUNNING DATA
Moving time versus elapsed time: which pace are you comparing?
Before comparing two pace numbers, check the clocks behind them. Removing a pause changes the calculation even when the route stays the same.
Two clocks, one activity
Elapsed time is the time from the start of an activity to its end. Moving time excludes time the recording system classifies as stopped. The exact way pauses are detected and handled can vary between recording sources.
Neither label alone explains how an app calculated every chart, split or summary. Check the activity source and the field you are using, especially when comparing exports from different services.
A three-minute stop changes the number
Imagine a 10-kilometer run with 50 minutes of moving time and a three-minute stop. The elapsed time is 53 minutes. The example is illustrative and assumes both distance measurements are exactly 10 kilometers.
| Clock | Time | Pace |
|---|---|---|
| Moving time | 50:00 | 5:00 min/km |
| Elapsed time | 53:00 | 5:18 min/km |
The 18-second-per-kilometer difference comes entirely from the time included in the calculation. It does not require a different running route or a change in the pace while moving.
Match the clock to your question
For a target race finish time, use the elapsed time you need to reach the finish. For a training comparison, decide whether you are studying the moving portions or the complete outing, then apply that choice consistently.
In the pace calculator, enter 10 kilometers and 50:00, then change the time to 53:00. The calculator cannot know whether a number represents moving or elapsed time; the choice of input belongs to you.
Why can Garmin and Strava show different pace?
Start by comparing the distance and time fields on the watch and in Strava. Strava documents that its moving-time calculation can use GPS, distance and speed, while manual pauses can change which time it uses. A pace difference does not by itself prove either recording is inaccurate. First reproduce each average from its own distance and duration, then check pauses and any distance correction separately.
Check the complete record
Runome's run-detail charts use moving-time handling that excludes identified stops and pause gaps. When you inspect an imported activity, review its source and available streams alongside the summary. A chart, a provider split and a headline duration may not use an identical time basis.
Before comparing a pair of runs, ask: are the distances comparable, do the durations use the same clock, and were pauses treated consistently? The run-comparison guide shows how to carry that check into a worked example.