Race Prediction Calculator
Predict your finish time for a new distance from a recent race result
Your recent race
Race to predict
You just ran a 5K in 25 minutes and you are wondering what that means for your first marathon. Could you break four hours? Should you sign up for the half marathon instead? The Race Prediction Calculator answers these questions using your real, recent race result. Enter the distance and time of a race you have already run, choose the distance you want to attempt next, and the calculator predicts your finish time with the Riegel formula, the most widely trusted race-time model in running. It also tells you the exact pace per kilometer and per mile you need to hold to hit that prediction. Whether you are setting a goal, choosing a training plan, or deciding which race distance suits you best, this tool turns one good performance into a realistic target for the next one.
What the Race Prediction Calculator Does
The Race Prediction Calculator estimates how fast you can run a race distance you have not attempted yet, based on a race distance you have already completed. It uses the Riegel formula, developed by researcher Peter Riegel in the 1970s: T₂ = T₁ × (D₂ ÷ D₁)^1.06. In plain words, your predicted time equals your known time multiplied by the ratio of the two distances raised to the power 1.06. The exponent 1.06 captures a well-observed fact about human endurance: as distance doubles, your sustainable pace slows down slightly, so a marathon takes a little more than eight times as long as a 5K, not exactly eight times. The calculator accepts common race distances from a dropdown menu — 5K, 10K, 15K, 10 miles, half marathon, and marathon — and also lets you type any custom distance in kilometers or miles. You enter your recent finish time as hours, minutes, and seconds, pick the target distance, and press Calculate. The result is a predicted finish time plus the required average pace, so you know not just the goal but how to run it.
How to Use the Race Prediction Calculator
Start with the “Your recent race” section. Choose your recent race distance from the dropdown. If you ran a standard distance like a 5K or a half marathon, just select it. If your race was a non-standard distance, choose “Custom distance” and type the distance, then select kilometers or miles. Next, enter your finish time using the hours, minutes, and seconds boxes. A 25-minute 5K would be 0 hours, 25 minutes, 0 seconds. Use your most recent race, and ideally one run in the last six to eight weeks, because your fitness changes over time and an old result predicts less accurately. Then move to the “Race to predict” section and select the target distance the same way, using a custom entry if needed. Press Calculate, and your predicted time appears at the top of the results, with the required pace per kilometer and per mile underneath. For the most honest prediction, use a recent race run at full effort on a similar course: a flat road 10K predicts a flat road half marathon far better than a hilly trail race predicts a track 5K.
The Riegel Formula Explained
The Riegel formula, T₂ = T₁ × (D₂ ÷ D₁)^1.06, looks technical but each part has a simple meaning. T₁ is your known race time in seconds, D₁ is the distance of that race, D₂ is the distance you want to predict, and T₂ is the predicted time. The ratio D₂ ÷ D₁ tells you how many times longer the new race is. If both races were the same distance, the ratio would be 1 and the prediction would equal your known time, which makes sense. The exponent 1.06 is the heart of the formula. If running speed never faded with distance, the exponent would be exactly 1.0 and times would scale in direct proportion. In reality, endurance drops as distance grows, so Riegel fitted the exponent to thousands of real performances and found 1.06 describes runners remarkably well across distances from about 3K up to the marathon. It is not perfect — it assumes similar fitness, similar conditions, and proper training for the longer distance — but for goal-setting it beats guessing by a wide margin. One practical note: the formula works best when the two distances are within a factor of about two to four of each other. Predicting a marathon from a 5K stretches the model further than predicting a half marathon from a 10K, so treat far-apart predictions as rough guides and close-together predictions as quite reliable.
Worked Examples
Example 1: 5K in 25:00, predicting a marathon. Your known time T₁ is 25 minutes, which is 1,500 seconds. D₁ = 5 km and D₂ = 42.195 km. First find the distance ratio: 42.195 ÷ 5 = 8.439. Raise it to the 1.06 power: 8.439^1.06 = 9.5911. Multiply by your known time: 1,500 × 9.5911 = 14,386.65 seconds. Convert to hours, minutes, and seconds: 14,386.65 ÷ 3,600 = 3.996 hours, so 3 full hours (10,800 seconds), leaving 3,586.65 seconds; 3,586.65 ÷ 60 = 59.78 minutes, so 59 full minutes (3,540 seconds), leaving 46.65 seconds, which rounds to 47 seconds. The predicted marathon time is 3 h 59 min 47 s — just under the four-hour barrier. The required pace is 14,386.65 ÷ 42.195 = 340.96 seconds per kilometer, or 5 minutes 41 seconds per km, which equals 9:09 per mile.
Example 2: 10K in 55:00, predicting a half marathon. T₁ = 55 × 60 = 3,300 seconds, D₁ = 10 km, D₂ = 21.0975 km. Distance ratio: 21.0975 ÷ 10 = 2.10975. Raise to 1.06: 2.10975^1.06 = 2.20640. Multiply: 3,300 × 2.20640 = 7,281.13 seconds. Convert: 7,281.13 ÷ 3,600 = 2.0225 hours, so 2 full hours (7,200 seconds), leaving 81.13 seconds, which is 1 minute (60 seconds) and 21.13 seconds, rounding to 21 seconds. Predicted half marathon: 2 h 1 min 21 s. Required pace: 7,281.13 ÷ 21.0975 = 345.13 seconds per km, or 5:45 per km.
Example 3: half marathon in 2:00:00, predicting a marathon. T₁ = 2 × 3,600 = 7,200 seconds, D₁ = 21.0975 km, D₂ = 42.195 km. Distance ratio: 42.195 ÷ 21.0975 = 2 exactly. Raise to 1.06: 2^1.06 = 2.08493. Multiply: 7,200 × 2.08493 = 15,011.51 seconds. Convert: 15,011.51 ÷ 3,600 = 4.1699 hours, so 4 full hours (14,400 seconds), leaving 611.51 seconds; 611.51 ÷ 60 = 10.19 minutes, so 10 full minutes (600 seconds), leaving 11.51 seconds, rounding to 12 seconds. Predicted marathon: 4 h 10 min 12 s. Required pace: 15,011.51 ÷ 42.195 = 355.75 seconds per km, or 5:56 per km. Notice how the pace slows from the half marathon pace of 5:41 per km to 5:56 per km — that slowing is exactly what the 1.06 exponent models.
Understanding Your Results
The headline result is your predicted finish time, shown as hours, minutes, and seconds. Treat it as the center of a range rather than a promise: most runners land within a few percent of a Riegel prediction when conditions are similar. The pace figures are arguably more useful for race day, because they translate the prediction into something you can follow kilometer by kilometer or mile by mile. If the calculator says 5:41 per km, that is the average pace you must hold from start to finish. Many runners combine the prediction with a pacing strategy, running the first half slightly slower than target pace and the second half slightly faster. Also pay attention to what the prediction implies about your training: a marathon prediction from a 5K assumes you will do the long runs and endurance work a marathon demands. Without that training, the prediction will be optimistic. Finally, remember that heat, hills, altitude, and wind all shift real times away from the formula, which assumes flat, cool, calm conditions similar to your original race.
Common Mistakes to Avoid
The biggest mistake is feeding the calculator an old or half-hearted race result. A 10K you jogged socially two years ago says nothing about your current fitness, and the prediction will mislead you. Use a recent, all-out effort. A second mistake is mixing units: entering a distance in miles while the calculator expects kilometers, or vice versa, throws the ratio off completely. Use the unit dropdown carefully for custom distances. Third, many runners predict far outside the formula’s comfort zone, such as a marathon from a single mile time trial. The further apart the distances, the wider the error band. Fourth, do not forget the training assumption: predicting a marathon time does not grant you marathon fitness. If you have never run longer than 10K, your first marathon will likely be slower than the formula suggests because endurance, fueling, and pacing are learned skills. Finally, treat the seconds as approximate. Rounding a prediction of 3:59:47 to “about four hours” is honest; planning your race around the exact second is not.
Frequently Asked Questions
1. How accurate is the Riegel formula?
For trained runners racing similar distances under similar conditions, Riegel predictions typically land within 3 to 5 percent of the actual time. Accuracy is best when the two distances are close together, such as 10K to half marathon, and weaker for extreme jumps like one mile to marathon.
2. What is the Riegel formula?
It is the equation T₂ = T₁ × (D₂ ÷ D₁)^1.06, where T₁ and D₁ are your known race time and distance, and T₂ and D₂ are the predicted time and target distance. The 1.06 exponent models how sustainable pace declines as distance increases.
3. Can I predict a shorter race from a longer one?
Yes. The formula works in both directions. A marathon time can predict a 10K time just as a 10K can predict a marathon. Predictions toward shorter distances tend to be slightly conservative because speed, not just endurance, limits short races.
4. Should I use my personal best or my most recent race?
Use your most recent all-out race. Fitness changes over months, so a personal best from two years ago reflects a different runner than you are today. Recency beats glory for prediction purposes.
5. What distance should I enter for a 5K?
Select 5K from the dropdown, or enter a custom distance of 5 kilometers. If your race was measured in miles, enter the miles value and choose miles as the unit so the conversion is handled for you.
6. Why does the prediction assume I trained for the distance?
The formula models what your body could do at your current fitness level, not what it will do without preparation. A marathon prediction from a 5K assumes you complete marathon-style long runs. Without that training, expect a slower result.
7. How do I convert my predicted time into a pace?
The calculator does it for you: it divides the predicted time by the target distance and shows pace per kilometer and per mile. You can also compute it yourself by dividing total seconds by the distance.
8. Does the formula account for hills or heat?
No. Riegel assumes conditions similar to your original race. Hills, heat, altitude, and strong wind all slow you down relative to the prediction, sometimes by several minutes over a marathon.
9. What is a good first prediction to try?
Predict a distance close to one you have raced, such as a half marathon from a 10K. The prediction will be at its most reliable, and it gives you a concrete, believable goal for your next training block.
10. Can beginners use race predictions?
Yes, with caution. Beginners improve quickly, so a race from two months ago may underpredict what you can do now. Also, beginners often lack the endurance base the formula assumes for long distances, so long predictions may be optimistic.
11. Why is my marathon prediction so much slower than eight times my 5K?
Because of the 1.06 exponent. Eight times a 25-minute 5K would be 3:20:00, but the formula gives about 3:59:47. The extra time reflects the real physiological cost of sustaining effort over 42 kilometers.
12. What if my race distance is not in the dropdown?
Choose “Custom distance” and type the exact distance, selecting kilometers or miles. The calculator converts miles to kilometers automatically so the formula always works in consistent units.
13. Should I enter gun time or chip time?
Use chip time, the time from when you crossed the start line to when you crossed the finish. Gun time includes the seconds or minutes you spent waiting to reach the start, which would inflate the prediction.
14. How often should I recalculate my prediction?
After every race, or whenever your fitness clearly changes. Each new result is fresh data, and updating the prediction keeps your training paces and race goals matched to your current ability.
15. Can I use this for triathlon run legs or trail races?
Only loosely. Triathlon runs follow tiring swim and bike legs, and trail races involve elevation and terrain the formula ignores. The prediction is calibrated for standalone road races, so adjust expectations for anything else.
Final Thoughts
A single race result contains more information than most runners realize. With the Race Prediction Calculator and the Riegel formula, one honest recent performance becomes a realistic goal for any other distance, complete with the pacing plan to achieve it. Enter your best recent race, pick your next target, and let the numbers set the ambition. Then do the training the prediction assumes, respect the conditions on race day, and run the even, disciplined pace the calculator worked out for you. The stopwatch will take care of the rest.