This race predictor calculator estimates your finish time for one race distance from a time you've run at another. Choose the race you've run, enter your time, and pick the race you want to predict, and the race predictor calculator uses Peter Riegel's formula to give your predicted time and average pace.
How to use the race predictor calculator
- Choose US or metric units for pace and custom distances. US (miles) is the default.
- Choose the race you've run and enter your time, such as 25:00 or 1:52:30.
- Choose the race you want to predict. Pick Other distance to enter any distance.
- Press Calculate.
Riegel's formula
The calculator uses the formula published by Peter Riegel, an American research engineer, in a Runner's World article in 1977. It predicts the time for one distance from the time for another:
T2 = T1 × (D2 ÷ D1)
raised to the power 1.06
Here T1 is your time for distance D1, and T2 is the predicted time for distance D2. The exponent, 1.06, is slightly more than 1, which means your pace gets a little slower as the distance gets longer. If the exponent were exactly 1, you'd be predicted to hold the same pace for any distance.
When the formula works best
In a 1981 article in American Scientist, Riegel extended this idea to records in running, swimming and walking, and limited the endurance range to efforts lasting between about 3.5 and 230 minutes. Some websites have changed the formula because the 1.06 exponent can give predictions for very long distances that seem hard to achieve. If either your time or the predicted time falls outside the 3.5 to 230 minute range, the calculator adds a note.
Worked example
Say you ran a 5K in 25:00. To predict a half marathon (21.0975 km), the distance ratio is 21.0975 ÷ 5 = 4.22. Raising that to the power 1.06 gives 4.60, so the predicted time is 25 minutes × 4.60 = 1:55:00, an average pace of about 8:46 per mile. For the marathon, the same 5K time predicts about 3:59:47, an average pace of about 9:09 per mile.
A runner who finished a 10K in 50:00 would be predicted to run a half marathon in about 1:50:19.
Reading the results
The big number is the predicted finish time. The table shows the distance of the race you're predicting and the average pace you'd need, per mile or per kilometer depending on the units you chose. A note appears if the prediction is outside the range the formula was designed for.
Getting a good prediction
The prediction is only as good as the time you put in. A recent race or time trial run at full effort works best. Predictions over a similar distance, such as 10K to half marathon, are usually more reliable than big jumps, such as a mile to a marathon, because the longer race tests endurance in a way a short one can't. And the formula assumes you've trained for the new distance: a fast 5K runner who hasn't done long runs will likely struggle to match their marathon prediction.
Why longer races are slower
The exponent of 1.06 builds in a gradual slowdown. Doubling the distance multiplies your time by 2 to the power 1.06, or about 2.085, so your pace over the longer race is about 4% slower. Going from a half marathon to a marathon adds the same 4% or so. That's a rule of thumb for well-trained runners; how much you slow down over a longer race depends on your endurance, so your own results may differ.
Using the predicted pace
The pace in the table is the average you'd need to hold for the whole race to hit the predicted time. Many runners use it as a target for an even-paced race, starting at that pace rather than faster. If your training runs at that pace feel too hard, set a more cautious goal. You can also use the prediction to check whether a goal time is realistic: if your recent 10K predicts a half marathon well slower than your goal, the goal may need more training.
Custom distances
Choose Other distance to predict any race, such as a 10-mile race or an 8K. Enter the distance in miles or kilometers, depending on the units you chose.
Entering your time
Type your time as hours, minutes and seconds separated by colons, such as 1:52:30, or as minutes and seconds, such as 25:00. A single number is read as minutes. Use your official finish time from the race results if you have it.
Common mistakes
- Using a training run. Use a race or a hard time trial.
- Predicting from very short efforts. Times under about 3.5 minutes are outside the formula's range.
- Ignoring the course. Hills, heat and wind change finish times.
- Skipping long runs. Marathon predictions assume marathon training.
Tips
- Use your most recent race result.
- Predict from a couple of different races and compare.
- Use the predicted pace to plan your race strategy.
Worked example in metric: 10K to marathon
Choose metric units, pick 10K as the race you’ve run and enter 50:00. Pick Marathon as the race to predict and press Calculate. The distance ratio is 42.195 ÷ 10 = 4.2195, and raising it to the power 1.06 gives about 4.60. So the predicted marathon time is 50 minutes × 4.60 = 3:50:01.
The table shows the distance as 42.2 km and an average pace of about 5:27 per km. In US units the same prediction is a pace of about 8:46 per mile. The finish time is the same in both, because the units only change how pace and custom distances are shown. A 10K runner aiming for a marathon should treat this as a best case, since it assumes full marathon training and an even pace from the start to the finish line.
What next
Use this often? Add Race Predict to your Home screen.
Frequently asked questions
How does a race predictor calculator work?
It uses Peter Riegel's formula: T2 = T1 × (D2 ÷ D1) raised to the power 1.06.
What will my marathon time be if I run a 25-minute 5K?
Riegel's formula predicts about 3:59:47.
How accurate is the Riegel formula?
Riegel limited it to efforts of about 3.5 to 230 minutes, and it assumes you train for the new distance.
Why is the exponent 1.06?
It's slightly more than 1, so pace slows a little as the distance gets longer.
Can I predict a half marathon from a 10K?
Yes. A 50:00 10K predicts a half marathon in about 1:50:19.
Sources
Was this tool helpful?
What went wrong?
We only receive the reason you pick, never what you typed into the tool.
Thanks for your feedback.