← All blog posts

How to get an accurate result from the Running Pace Calculator

WhiteUI · A plain-English guide to the Running Pace Calculator

A pace is only as good as the two numbers typed in. Get the distance and the time exact and the answer is exact. Guess them, round them, or measure the route wrong, and the answer drifts — sometimes by several seconds a kilometre. Here is how to get it right with the Running Pace Calculator.

Three things to get right

  • Exact distance. Measure the route properly — a running app, a measured course, or a track. A route you guessed at is the biggest source of error in a pace.
  • Exact time. Start the watch when you start running and stop it when you stop. A watch left running through a two-minute stop at a crossing adds time that was not running.
  • The same conditions. Compare paces on the same route in similar weather. A hilly route in the heat is not comparable with a flat route in the cool, even if the distance and time are the same.

Worked example

10 km in 55 minutes. Pace is 55 ÷ 10 = 5:30 min/km, the pace per mile is 8:51 min/mile, and the speed is 10.9 km/h.

Pace = 55 min ÷ 10 km = 5:30 min/km
Pace per mile = 5.5 × 1.60934 = 8:51 min/mile
Speed = 10 ÷ (55 ÷ 60) = 10.9 km/h

How a wrong distance changes the answer

Keep the same 55 minutes and change only the distance. If the route was really 9.8 km instead of 10 km, the pace is 55 ÷ 9.8 = 5.61 minutes — 5:37 min/km, seven seconds a kilometre slower than you thought. A 200-metre error over 10 km is only 2% of the distance, but it moves the pace by 7 seconds a kilometre — enough to make a run look like a personal best when it was not.

At a glance

Same 55 minutes, two distances10.0 km — 5:30 min/km9.8 km — 5:37 min/kmA 200 m error moves the pace by 7 seconds a kilometre.

Two hundred metres is a small error in distance, but pace is sensitive to it: the same 55 minutes is 5:30 over 10 km and 5:37 over 9.8 km.

The mistake to avoid

Rounding the time before you divide. A run of 55 minutes 40 seconds typed in as 55 minutes loses 40 seconds — over 10 km that is 4 seconds a kilometre. Type the full time, seconds included, and let the calculator do the rounding. And recheck the distance every time you run a new route: a route measured once on a map is worth more than a route guessed at every week.

This calculator gives general information only — it is not medical advice. If you have a health condition, talk to a doctor before starting a running plan.

GPS watch, phone app or measured course — which to trust

Not every distance reading is equally good. A measured course — a marked race route, a 400 m track, or a parkrun 5 km — is the most trustworthy, because the distance was fixed before you started. A GPS watch on open roads is next: most are accurate to about 1–2%, which is good enough for training. A phone app is much the same, but it is worse under trees and between tall buildings, where the signal bounces. A treadmill is the least trustworthy of the lot: it measures belt speed, not your movement, and it is rarely calibrated exactly.

The size of the error matters more than the gadget. Run 10 km in 57 minutes 30 seconds and your pace is 5:45 min/km. If the course was really 9.8 km, not 10 km, the pace is 57.5 ÷ 9.8 = 5.87 minutes — 5:52 min/km, seven seconds a kilometre slower than you thought. Two hundred metres is a small error in distance, but pace is sensitive to it, so measure the route once properly rather than guessing it every week.

The one check to run before you believe the number

Cross-check pace against speed. Run 3 km in 20 minutes and the pace is 20 ÷ 3 = 6.67 minutes — 6:40 min/km — and the speed is 60 ÷ 6.67 = 9.0 km/h. If your app says 6:40 min/km but 9.9 km/h, one of the two is wrong, because 9.9 km/h needs a pace of about 6:04, not 6:40. The two numbers come from the same run, so they have to agree.

Then run the same route twice. A pace that jumps by 30 seconds a kilometre between two identical runs is a measurement error, not a fitness change — fitness does not move that fast. When the two runs agree within a few seconds a kilometre, the number is worth trusting, and the comparison with next week means something.

Frequently asked questions

Should I use exact values or round them?

The exact values. Rounding 55 minutes 40 seconds down to 55 minutes loses 4 seconds a kilometre over 10 km — type the full time and let the calculator round.

How accurate is my watch’s distance?

Most GPS watches are accurate to about 1–2% on open roads, less under trees or between tall buildings. A 2% error on 10 km moves the pace by about 7 seconds a kilometre.

Why does my treadmill pace differ from my road pace?

Treadmills measure belt speed, not your movement, and they are rarely calibrated exactly. A treadmill that reads 10.9 km/h may really be running at 10.5 — trust the road time on a measured route.

Does stopping at a crossing change my pace?

Only if the watch keeps running. Stop the watch for the stop, or the standing time counts towards your pace and makes it look slower than your running really was.

More guides on the Running Pace Calculator

Try it yourself

A free calculator that works out your pace, finish time or distance from the other two numbers, in min/km and min/mile.

Open the Running Pace Calculator