What the running pace calculator measures
A running pace calculator turns three numbers — distance, time, and pace — into everything you need to plan or review a run. Enter any two of them and this tool works out the third, then builds on it: your pace in both min/km and min/mile, your speed in km/h and mph, a full table of splits every kilometre, mile, or 5-unit block, and Riegel-based predictions for your likely 5K, 10K, half marathon and marathon times. You also see how your pace and distance compare with other runners who’ve used the calculator.
It works for anything from a 400 m track interval to an ultramarathon-length custom distance — pick a standard race distance (5K, 10K, half marathon, marathon and others) or enter your own from 0.4 km up to 250 km.
How to use the pace calculator
- Pick a mode. Pace mode: enter your finish time and distance, get your pace and speed. Time mode: enter a target pace and distance, get your projected finish time.
- Choose a distance. Use a preset (800 m, 1500 m, 1 mile, 5K, 10K, 15K, 20K, half marathon, 25K, 30K, marathon, 50K) or switch to Custom and type any distance from 0.4 to 250, in km or miles.
- Enter your time or pace. In Pace mode, type hours/minutes/seconds. In Time mode, type minutes/seconds per unit (under 60 minutes).
- Optional: set the split interval. Choose splits every 1 or 5 units to see a full pacing table for the race.
The calculator always shows both units side by side — km and miles, km/h and mph — so you don’t need to switch back and forth.
Pace, speed and time: how the calculation works
Pace, speed, time and distance all come from one relationship: distance = speed × time. Rearranged, that gives the two formulas this calculator runs on:
pace (min/km) = time (min) ÷ distance (km) speed (km/h) = 60 ÷ pace (min/km)
Converting between km and miles uses a single fixed constant: 1 mile = 1.609344 km exactly, defined by the international yard-and-pound agreement of 1959 (NIST Handbook 44). It’s not rounded to 1.61 anywhere in the calculation — only the final displayed result is rounded, to the nearest second.
Step-by-step example
You run 10 km in 50:00.
- Pace = 50 ÷ 10 = 5:00 min/km.
- Speed = 60 ÷ 5 = 12.00 km/h.
- Pace in miles = 5:00 × 1.609344 ≈ 8:03 min/mile.
- Speed in mph = 12 ÷ 1.609344 ≈ 7.46 mph.
Same pace, different distance: a half marathon (21.0975 km) finished in 1:45:00 works out to 4:59 min/km (12.06 km/h) — slightly faster than the 10K example above, because 1:45:00 over 21.0975 km divides out to a marginally quicker pace than 50:00 over 10 km. A 4:00:00 marathon (42.195 km) comes out to 5:41 min/km (10.55 km/h).
Predicting your race time: the Riegel formula
If you know your time at one distance, you can estimate what you’d run at another using the formula published by researcher Pete Riegel in American Scientist (1981):
T2 = T1 × (D2 ÷ D1)^1.06
T1 and D1 are your known time and distance; D2 is the distance you want to predict; 1.06 is Riegel’s empirically fitted exponent, derived by fitting a power curve to world records across distances from 100 m to 100 miles. That exponent above 1.0 is what makes prediction useful in the first place: if effort scaled perfectly linearly (exponent = 1.0), doubling your distance would exactly double your time. In practice it takes a bit more than double, because of accumulating fatigue — glycogen depletion, neuromuscular tiredness, pacing errors over longer efforts.
Example: run 5 km in 20:00 (4:00/km). Since 10K is exactly double the distance, Riegel predicts a 10K time of about 41:42 — noticeably more than a straight 40:00 double, which is the fatigue factor at work.
Stretch the same 20:00 5K time all the way out to a marathon (a distance ratio of 8.4×) and Riegel predicts roughly 3:11:50 — about 23 minutes slower than simple linear scaling (2:48:47) would suggest. The calculator flags predictions like this one as lower confidence whenever the distance ratio passes 6×, because the formula was fitted across a huge range of distances and gets progressively less reliable the further you extrapolate from what you actually ran. It also doesn’t account for terrain, weather, age, or how specifically trained you are for the target distance — a 5K specialist and a marathon specialist with identical 5K times rarely run identical marathons.
Closer-distance predictions are far more dependable: for a runner doing 10 km in 50:00, Riegel puts a half marathon at about 1:50:20 and a full marathon at about 3:50:00 — both well inside the 6× ratio, so no low-confidence flag.
Splits and negative splits
The splits table assumes even pace — the same pace held from start to finish — split into blocks of 1 or 5 km/miles, however you set it. Because most race distances aren’t exact multiples of a kilometre or mile, the last segment is usually shorter than a full block; the calculator computes it as a partial split rather than rounding it away.
Example: a half marathon (21.0975 km) run at an even 5:00/km pace produces 21 full 1 km splits of exactly 5:00 each (cumulative: 5:00, 10:00, 15:00 … 1:45:00 at km 21), plus one final partial split covering the last 0.0975 km (about 97.5 m) in roughly 29 seconds — for a total finish time of 1:45:29.
A negative split means running the second half of a race faster than the first — the opposite of an even split. Take a marathon finished in 3:50:00: an even-split race looks like 1:55:00 for each half; a negative split might be 1:56:00 for the first half and 1:54:00 for the second — same total time, but the pace picks up rather than fades. Most coaches consider negative or even splits a sounder race strategy than starting fast and slowing down (a “positive split”), because starting conservatively leaves more in reserve for the second half, when fatigue bites hardest. The calculator itself always shows even splits — it can’t know your real pacing strategy, only your target average.
Reading your result: pace categories
The scale on your result places your speed into one of six broad bands. These are informal, commonly used reference points, not a medical or competitive standard:
| Category | Pace (min/km) | Speed (km/h) |
|---|---|---|
| Walk | slower than 10:00 | under 6.00 |
| Beginner | 7:00–10:00 | 6.00–8.57 |
| Recreational | 5:00–7:00 | 8.57–12.00 |
| Advanced | 4:00–5:00 | 12.00–15.00 |
| Competitive | 3:00–4:00 | 15.00–20.00 |
| Elite | faster than 3:00 | over 20.00 |
If your entered pace would beat the current world record for the chosen distance, the calculator flags it — usually a sign that km and miles got swapped somewhere, rather than a real result.
Why your GPS watch shows a different distance
If your watch reads 42.3–42.4 km after “a 42.195 km marathon,” that’s normal, not a bug. World Athletics course-certification rules (Book C, Rule 240) require certified road courses to measure no shorter than the official distance, with a built-in “short course prevention factor”: courses are measured so that every kilometre reads as roughly 1001 m rather than 1000 m — a deliberate buffer against underestimating. On top of that, GPS watches cut tangents on curves less precisely than the certified measurement line, which almost always adds a bit more distance to your recorded track. Both effects push in the same direction, which is why your watch pace is often very slightly slower than your official race pace over the same event.