Running pace per km / mile and finish-time predictor for common race distances.
Updated
Distance & time
Pace & speed
Pace per km
5:00 /km
Pace per mile
8:03 /mi
Speed (km/h)
12.00 km/h
Speed (mph)
7.46 mph
Riegel race-time prediction
Predicted finish times if you ran each distance at your current endurance level. Based on T₂ = T₁ · (D₂/D₁)^1.06.
Distance
Predicted finish time
Pace
1 mile(1.61 km / 1.00 mi)
7:13
4:29 /km
5K(5.00 km / 3.11 mi)
23:59
4:48 /km
10K(10.00 km / 6.21 mi)
50:00
5:00 /km
Half marathon(21.10 km / 13.11 mi)
1:50:19
5:14 /km
Marathon(42.20 km / 26.22 mi)
3:50:01
5:27 /km
Quick start
How to calculate pace and predict race times
Enter a distance and a time. The calculator returns pace per km / mile, average speed, and predicted finish times for the standard race distances using Riegel's formula.
Step 1
Pick distance unit
Switch between kilometers and miles for the distance input.
Step 2
Enter distance & time
Type the distance you ran and the time as M:SS or H:MM:SS (e.g. 25:30 or 4:15:00).
Step 3
Read pace + predicted finishes
Pace per km and per mile, speed in km/h and mph, and a Riegel-predicted finish time for 1 mile, 5K, 10K, half-marathon and marathon.
In-depth guide
Pace calculator — pace, speed, and Riegel's race-time prediction
Enter a distance and a time and the calculator returns pace per km and per mile, average speed in km/h and mph, and predicted finish times for the standard race distances using Riegel's 1981 endurance formula. Useful for race planning, workout pacing and comparing efforts across distances.
Pace vs. speed
Two ways to express the same number:
Pace — time per unit of distance (min/km or min/mi). The standard runner's unit. Lower is faster. A 5:00/km pace is faster than a 5:30/km pace.
Speed — distance per unit of time (km/h or mph). The standard cyclist's and runner's treadmill unit. Higher is faster.
Conversion: pace (min/km) = 60 / speed (km/h). A 12 km/h pace is 5:00/km; a 10 mph pace is 6:00/mi.
Riegel's race-time formula
Pete Riegel's 1981 paper proposed an endurance scaling law that has held up across forty years of race data:
T₂ = T₁ · (D₂ / D₁)^1.06
The 1.06 exponent encodes the rule that pace slows about 6% per doubling of distance for trained runners. A 5K time of 22:00 implies ~45:30 for 10K (a 6% slow from the 5K pace), ~1:40:30 for the half-marathon, and ~3:31 for the marathon.
Where the model breaks down
Riegel's formula assumes endurance is the limiting factor, which is true for distances roughly between 1 mile and the marathon for trained runners. Outside that range:
Sub-mile — anaerobic capacity dominates. The 1.06 slope is too gentle; sprinters can run a 400m far faster than the 1-mile-extrapolated curve predicts.
Ultras (50K+) — fueling, heat regulation and pacing strategy dominate over cardiovascular endurance. The 1.06 slope is too gentle; real ultra times are usually 5–15% slower than Riegel projects. We cap predictions at the marathon.
Untrained runners — the slope is steeper than 1.06; marathon predictions are optimistic. Train the distance before believing the prediction.
Useful applications
Three places this calculator earns its keep:
Race goal pacing — type your goal marathon time, see the per-km pace you need to hold.
Cross-distance comparison — was last week's 10K faster than last month's 5K, normalised? Project both onto the half-marathon and compare.
Workout pacing — a 25:00 5K runner hitting marathon pace (~4:53/km Riegel-projected) means a steady aerobic run, not a sprint.
Frequently asked questions
Is my data uploaded anywhere?
No. The pace and finish-time predictions run entirely in your browser as you type. Nothing is sent to a server, stored, or logged.
How is the finish-time predictor calculated?
Riegel's formula (1981): T₂ = T₁ × (D₂/D₁)^1.06. The 1.06 exponent encodes the empirical observation that pace slows by about 6% per doubling of distance for trained runners. It's the most-cited endurance prediction model and works well from 1 mile up to the marathon.
How accurate is the prediction?
Within roughly 2–5% for trained runners predicting from a half-distance event upward. It overestimates marathon performance for runners whose endurance training is light (the 6%/doubling slope is steeper at high distances when fueling, heat and pacing dominate). It underestimates short-distance speed for highly anaerobic athletes.
Why does it stop at the marathon?
Riegel's model breaks down at ultra distances (50K+) because the dominant factors shift from cardiovascular endurance to fueling, heat regulation and pacing. We cap predictions at the marathon to avoid implying a precision the formula doesn't have.
What's a good 5K time?
Highly individual. As rough public-data brackets: under 30 min is a typical recreational target, 22–25 min for regular runners, 18–20 min for serious amateurs, sub-15 for elite. Age and sex matter — your own trend over weeks matters more than any benchmark.
Can I use this for cycling or swimming?
Riegel's exponent (1.06) was fit on running data. Cycling has a much flatter pace-vs-distance curve (drafting, gearing, terrain dominate); swimming sits between. For running this tool is reliable; for other sports treat the predictions as illustrative only.
How do I enter time?
Use M:SS or H:MM:SS format — '25:30' for a 25-and-a-half-minute 5K, or '4:15:00' for a 4-hour-15-minute marathon. Distance is in kilometers; switch the pace output row to read in mi/km depending on which side of the Atlantic you train.
Keep exploring
More tools you'll like
Hand-picked utilities that pair well with the one you're on — all
free, client-side, and zero-signup.