Understanding running pace
What pace is, how it is measured, why it changes with terrain and heat, and what it does not tell you about your running.
- Pace is time per unit of distance — minutes per mile, or minutes per kilometre.
- Your pace varies with terrain, heat, wind and fatigue. That is normal, not a fitness problem.
- Average pace is reliable. Instantaneous GPS pace is not, and should mostly be ignored.
- Pace measures speed. Effort is what your body responds to, and the two come apart on hills.
Pace is how long it takes you to cover one unit of distance — minutes and seconds per mile, or per kilometre. An 8:01 mile pace means every mile takes eight minutes and one second.
It is the most useful single number in running, and also the one most often misread.
Pace, speed and effort are three different things
Speed is distance over time; pace is its inverse, and runners use pace because we think in miles and minutes rather than miles per hour. Both describe how fast you are moving over the ground.
Effort is what your body actually experiences, and it is not the same thing. Running 9:00 pace on the flat and 9:00 pace up a four-percent climb are wildly different efforts. On a hot day, the same pace costs more than it did in March.
This is why holding a fixed pace is the wrong instruction for most training runs, and the right instruction for a flat race.
Why your watch disagrees with itself
Consumer GPS is accurate to a few metres in good conditions and worse under trees or between buildings. Instantaneous pace is calculated over a very short window, so those few metres of error become large swings — the same steady run showing 7:30 one moment and 9:10 the next.
Nothing is wrong with your running. Average pace over a mile is reliable because the errors cancel; a reading over three seconds is mostly noise.
What pace is genuinely good for
- Planning a race. A finish time is a pace held for a distance, which is what a split calculator turns into a plan you can actually run to.
- Setting training intentions. Easy, threshold and interval work each have a pace range, derived from a recent race result.
- Comparing like with like. The same route, the same conditions, three months apart.
What it is not good for is comparing yourself to anyone else, or to the same route in different weather, or judging a hilly run against a flat one.
How we calculate pace
Every pace on SplitPace comes from one library with a published contract. Distances are exact — a marathon is 42,195 metres, not 26.2 miles — and values are computed at full precision and rounded once, at the end, so a split table never drifts across the distance.
Common questions
What is a good running pace?
There isn’t one. A useful pace is one you can hold for the distance you intend to run — which makes it a different number for a 5K and a marathon, and a different number again on a hot day.
Why does my pace change on hills?
Because pace measures speed, not effort. Holding an even pace up a climb means working considerably harder; on a training run you are usually better off holding effort steady and letting the pace drift.
Why is my watch’s current pace so erratic?
Instantaneous pace is derived from a GPS signal accurate to several metres, so short-term readings swing wildly. Average pace and lap pace are far more trustworthy, which is why almost every experienced runner watches those instead.