Race Time Predictor
Enter one race result and predict your finish time at any other distance, from a mile to 50K, with a confidence rating on every prediction. The race calculator tabs turn that number into pace, finish time and splits. No signup, no download.
- Mile to 50K from one result
- Confidence on every prediction
- Race pace and finish time
- Mile by mile splits
Enter your race result
Select a race distance and enter your finish time.
The big number on each row is your prediction: the average of the Riegel and Cameron formulas. The two lines under it show where each formula lands on its own.
Predicted times for all distances
Select a race distance and enter your time above to see predictions.
You have a prediction. Now go prove it.
Motera gives every training run a reason. Finish a loop where you started and the streets inside are yours, so getting fitter means holding more.

You claimed a new territory!


Always had issues with discipline, now i dont!How do you predict a race time?
To predict race time, multiply your known time by the distance ratio raised to the power of 1.06. That is the Riegel formula, and it turns a 25:00 5K into a 52:07 10K, a 1:55:00 half and a 3:59:47 marathon.
A marathon is 8.439 times as long as a 5K, but the time grows 9.59 times, because the 1.06 exponent adds time for fatigue. The tool rates this jump Low confidence, so read it as what your speed could support with full marathon training. To go straight to a marathon number, use the marathon race time predictor.
Race time predictor chart, mile to 50K
Predicted race times from nine 5K results, all from the Riegel formula. Find your 5K and read across, or use the calculator for an exact time.

How to read these predicted race times
Each row assumes you train properly for the distance you are reading. The 10K and half columns stay close to what your 5K shows. The marathon and 50K columns only hold if the long runs are in your legs. The half column doubles as a half marathon time predictor.
Projected marathon time from a half
To predict marathon time, use this half marathon to marathon predictor. Riegel multiplies a half by 2.085. Slate's reader data landed on 2.19, which is 9 to 16 minutes slower across these times.
Why the two numbers differ
A study of 2,303 recreational runners found Riegel well calibrated up to the half, but marathon times at least 10 minutes too fast for half of runners (Vickers and Vertosick, 2016). Slate's 2014 predictor reached x2.19 from about 2,500 readers.
Which to plan around
Treat Riegel as the fast end and x2.19 as the slow end of your range. To set a pace inside it, the marathon pace calculator gives splits, and the marathon pace chart lists finish times by pace.
Prediction confidence guide
Every prediction in the tool carries a rating, set by how far the target distance sits from the race you entered. Predictions up to the marathon or 50K never rate High.
Half the input distance up to 4x, below the marathon
The closest the formulas get. A 2016 study of 2,303 recreational runners found Riegel well calibrated up to the half marathon.
Predicting a 10K from a 5K result (2x).
From 4x to 8x, a quarter to half the input distance, or a marathon or 50K within 4x
Training for the target distance starts to decide the result. For the marathon, the same study found Riegel at least 10 minutes too fast for half of runners.
Predicting a marathon from a half marathon (2x), or a half from a 5K (4.2x).
More than 8x, or under a quarter of the input distance
Use these as rough estimates only. Your time will depend heavily on specific training.
Predicting a marathon from a 5K result (8.4x).
Factors that affect prediction accuracy
Training volume
Runners with higher weekly mileage tend to outperform predictions at longer distances. If you run 20 miles per week, your marathon prediction from a 5K will likely be too optimistic. If you run 50+ miles per week, you may beat it.
Course terrain
Predictions assume a flat course with ideal conditions, so no formula here works as a trail race time predictor. A hilly or trail race will be slower than predicted. A downhill course like the Boston Marathon may produce faster results, though not always, because the descents punish the quads.
Weather conditions
Heat and humidity degrade performance significantly at longer distances. A 5K is short enough that heat has minimal impact, but a marathon in 80F weather could add 10+ minutes. Wind, rain and altitude also affect results.
Race experience
First-time racers at a new distance often underperform predictions because they lack pacing experience and mental familiarity with the distance. After completing it once, later attempts are typically much closer to predicted times.

Correct for the conditions after you predict: the heat adjusted pace calculator covers hot days, and the elevation adjusted pace calculator covers hills.
How race prediction formulas work
T2 = T1 x (D2/D1)^1.06
T1 is your known time, D1 is the known distance, D2 is the target distance, and 1.06 is the fatigue exponent, the rate at which performance declines as distance grows. Peter Riegel published it in Runner's World in 1977 and covered running, swimming and walking in a 1981 American Scientist paper.
T2 = T1 x (D2/D1) x f(D1)/f(D2)
f(D) = 13.49681 - 0.000030363 x D + 835.7114 / D^0.7905
Distances are in meters. Cameron scales the time by the distance ratio, then by a distance factor f(D) in place of one fixed exponent. From a 25:00 5K it gives a 7:16 mile against Riegel's 7:31, and a 4:03:59 marathon against Riegel's 3:59:47.
What the exponent does to your pace
Pace per km from a 25:00 5K, Riegel. Bars start at 25 percent so the small gaps show.
How Cameron compares
Cameron's distance factor makes it fade differently from Riegel. From a 5K the two agree within seconds at the 10K and half. At the mile Cameron runs faster, and at the marathon and 50K it runs slower.
Adjusted prediction
The big number in the tool is the average of the two lines: 4:01:53 for the marathon from a 25:00 5K. Neither formula accounts for training specificity, weather, terrain or individual physiology, which is why the confidence ratings matter.
The math, step by step
An illustrative example of how Riegel turns one result into a prediction. Say a runner posts a 22:30 5K, which is 1,350 seconds over 5,000 meters.
- 1
Start with the formula
T2 = T1 x (D2/D1)^1.06. T1 is the known time in seconds, D1 is the known distance in meters, D2 is the target distance in meters. - 2
Plug in the 5K to 10K prediction
T2 = 1,350 x (10,000/5,000)^1.06 = 1,350 x 2^1.06 = 1,350 x 2.085 = 2,815 seconds, which is 46:55. That is the pace-decline-adjusted 10K time, not simply double the 5K. - 3
Plug in the 5K to half marathon prediction
T2 = 1,350 x (21,097.5/5,000)^1.06 = 1,350 x 4.2195^1.06 = 1,350 x 4.600 = 6,210 seconds, which is 1:43:30. The distance ratio is 4.22x but the time ratio is 4.60x, because the 1.06 exponent adds time for the extra fatigue. - 4
Read the confidence rating alongside the number
The 10K prediction (2x the input distance) carries High confidence. The half marathon prediction (4.2x) sits just past the High cutoff and the tool rates it Medium, so treat it as a target range rather than a guarantee.
Where these formulas come from
Both prediction models on this page trace back to published work on endurance performance. Here is the sourcing behind them, plus the research on how well they hold up.
Riegel formula, 1977
Research engineer Peter Riegel proposed T2 = T1 x (D2/D1)^1.06 in Runner's World in 1977, then set it out in a 1981 American Scientist paper, Athletic Records and Human Endurance, covering running, swimming and walking efforts of about 3.5 to 230 minutes.
View the sourceCameron formula
Cameron's equation predicts a new time from a previous result with distances in meters, using a distance factor f(D) = 13.49681 - 0.000030363 x D + 835.7114 / D^0.7905 in place of a single fixed exponent. The linked page gives the full equation.
View the sourceVickers and Vertosick, 2016
A study of 2,303 recreational runners in BMC Sports Science, Medicine and Rehabilitation found Riegel well calibrated up to the half, with marathon times at least 10 minutes too fast for half of runners.
View the sourceSlate, 2014
Christie Aschwanden, Andrew Vickers and Chris Kirk built a marathon predictor from about 2,500 readers, covering 929 marathons, 1,446 halves, 888 10Ks and 1,293 5Ks. It multiplies a half by 2.19 and adjusts for weekly mileage.
View the sourceTanda, 2011
Giovanni Tanda predicted mean marathon pace from an 8-week training window, using weekly distance and mean training pace. It needs a training log rather than a race, so this tool does not use it.
View the source"Of those who attempt to race over the marathon distance of 26 miles and 385 yards (42.195 kilometers), more than two-fifths experience severe and performance-limiting depletion of physiologic carbohydrate reserves (a phenomenon known as ‘hitting the wall’)"
Benjamin Rapoport, PLOS Computational Biology, 2010This is why the further a target distance sits from your input race, the more the prediction assumes an endurance base and fueling strategy the formula cannot see.
When to trust a race prediction, and when not to
Trust the number when
- Your input race was a genuine all-out effort on a fair, standard course within the last 6 to 8 weeks.
- The target distance is within 4x of your input distance and shorter than the marathon, where confidence is highest.
- Your training already includes long-run mileage appropriate for the target distance, not just speed work.
- You are using it to set a starting target for a training block, not a race-day guarantee.
Treat it as a rough guess when
- You are jumping more than 6x in distance, such as predicting a marathon from a mile time trial.
- Your input race was hilly, hot or run conservatively rather than as a true time trial.
- You have not run the long runs for the target distance in training, so the endurance assumption behind the formula does not hold.
- Race day conditions differ sharply from your input race, especially heat, humidity or elevation gain.
Race distance comparison
Not sure which race distance is right for you? Compare four common road races by length, finish time at an even 10:00 per mile, training commitment and difficulty, then choose one that fits your fitness and available training time.
5K
Beginner10K
IntermediateHalf Marathon
ChallengingMarathon
AdvancedIf the 10K is the distance you settle on, the 10K goal time to pace converter breaks that finish time into per mile and per kilometer numbers.

Race day planning checklist

- Set your target pace and print your split sheet
- Plan your pre-race meal 2 to 3 hours before start time
- Check the weather forecast and adjust pace expectations
- Study the course map for hills, turns and aid station locations
- Arrive at least 60 minutes early to park, check in and warm up
- Start conservative, especially in the first mile
- Check splits at each mile marker and adjust effort accordingly
- For half marathons and longer, have a fueling plan (gels, water)
For a more detailed list, see the personalized race day checklist, and work out your gels with the race fueling calculator.
How this race calculator differs from Motera's other race tools
Motera has several race math tools that sound similar but answer different questions. This one predicts a finish time for any distance from a single result.
Race Time Predictor (this page)
What is my finish time at any distance, from 1 mile to 50K, based on one result?
Best for: Runners who want a general cross-distance forecast, not just the marathon.
Marathon Race Time Predictor
What is my marathon time specifically, from a recent race?
Best for: Runners whose only goal is the marathon number.
Race Equivalency Calculator
What performance level does my result represent at another distance, including an age-graded comparison?
Best for: Comparing effort quality across distances or age groups, not predicting a future race.
Race Pace Calculator
Given a known distance and time, what pace per mile or km does that require?
Best for: Converting a time goal into a per-mile pace target, no fatigue modeling involved.
Turning a prediction into a training plan
A predicted time is only useful if it changes what you do in training. Here is how to put the number to work.
Set training paces off the prediction, not your input race
Your predicted time at the target distance, not your current 5K or 10K pace, should anchor your interval, tempo and long-run paces for that race. A VDOT-style training pace calculator can convert the prediction into daily paces.Re-run the prediction every 4 to 6 weeks
As fitness changes, so does the prediction. A fresh time trial or tune-up race keeps your training paces honest instead of locked to a number from two months ago.Treat Low confidence predictions as a training target, not a race target
If you are predicting a marathon from a 5K, use the number to set a training block goal (build the long runs, hit the weekly mileage) rather than writing it on your race bib.Log the real result and compare
After the target race, compare your time to the prediction. The gap tells you whether your training matched the distance, which is more useful feedback than the prediction itself.
Training for that predicted time can claim real ground.
In Motera, a run that loops back to where it started turns the area inside into your territory. Draw a loop on the map with your finger or mouse and see how much ground one training run can take.
- Zones0
- Area0 m²
- Loop0.00 km
- XP+0
Demo numbers. In the app, your real GPS run draws the loop.
© OpenStreetMap, OpenFreeMap
How race predictor algorithms work
RACE CALCULATOR "PREDICTORS", VDOT & ALGORITHMS?! DETERMINE WORKOUT PACES WITH COACH SAGE: TTT EP45
Coach Sage on race calculator predictors, VDOT and the algorithms behind them, and how to set workout paces from a race result. From Vo2maxProductions.
What is a race time predictor?

A race time predictor uses one finish time to estimate your time at other distances. It accounts for the fatigue that builds as a race gets longer, so a predicted 10K is slower than two of your 5Ks. Runners use it to pick a goal before signing up for a race, to see what a parkrun 5K says about a half marathon, or to turn a goal into a pace per mile.
The calculator has five tabs.
- Race Predictor takes one result and returns the mile, 5K, 10K, 15K, half, marathon and 50K. Each row shows the average of Riegel and Cameron as the prediction, both formulas underneath and a confidence rating.
- Pace takes a distance and a time and returns pace per mile or km.
- Time takes a distance and a pace and returns the estimated finish time.
- Quick Predict takes one result and returns Riegel times for the mile, 5K, 10K, half and marathon.
- Splits takes a distance and a target time and returns every split with the cumulative time.
Pace, Time and Splits work in miles or kilometers and have presets for the 5K, 10K, half marathon and marathon. Switching the unit converts the distance and the pace already entered. Use the Pace and Splits tabs together to plan race day pace. The tool runs in your browser with no signup.
It is for runners choosing a goal for their next race, checking what a recent result says about a longer or shorter distance, or planning race day pace. For equal efforts rather than a forecast, the race equivalency calculator is the better fit. To keep your recent results in one place, log them in the running PR tracker.
Keep reading:Running calculatorMarathon calculatorMarathon time calculatorRace day checklist
Race predictor questions
How do race time prediction formulas work?
Race prediction formulas use the mathematical relationship between distance and fatigue. The Riegel formula (T2 = T1 x (D2/D1)^1.06) assumes that for every doubling of distance, your pace slows by a set share rather than holding steady. The Cameron formula scales the time by the distance ratio and by a distance factor that changes with distance, so it lands faster than Riegel at the mile and slower at the marathon. Both assume you are equally well-trained for both distances, which is the main source of error.
What is the most accurate race predictor?
No single formula is universally most accurate, and the key factor is whether your training matches the target distance. A 2016 study of 2,303 recreational runners found the Riegel formula well calibrated up to the half marathon, but it gave marathon times at least 10 minutes too fast for half of runners. For the marathon, a half marathon time times 2.19 (Slate, 2014) comes out slower and has reader race data behind it.
Can I predict a marathon time from a 5K?
You can, but the prediction will be less reliable than predicting from a half marathon. The further apart the distances, the more assumptions the formula makes about your endurance. A 5K to marathon prediction assumes you have the aerobic base and long-run training for 26.2 miles. Many runners who are fast at 5K do not have the marathon-specific endurance, so the prediction is often optimistic.
How do I find my projected marathon time?
Enter your most recent half marathon in the predictor and read the Marathon row. A 1:45:00 half gives 3:41:01, the average of Riegel (3:38:55, the half times 2.085) and Cameron (3:43:08). Slate's x2.19 gives 3:49:57 from the same half, so treat the tool's number as the fast end of your range. For a page built only around the marathon, use the marathon race time predictor.
How do I predict a 10K from a 5K?
Multiply your 5K time by 2.085, which is 2 to the power of 1.06. A 25:00 5K predicts a 52:07 10K on Riegel. That is slower than simply doubling the 5K, because the exponent adds time for fatigue. The tool rates this prediction High confidence.
How does mile prediction work?
Mile prediction runs the same formula downward. Enter a race result, and the 1 Mile row scales it by distance. On Riegel a 5K time times 0.301 gives your mile, so a 25:00 5K predicts a 7:31 mile. Cameron gives 7:16, and the big number in the row is the average, 7:23.
Do I need an app to predict my mile time?
No. The predictor runs in your browser with no signup or download. Enter a 5K, 10K or half marathon result and read the 1 Mile row, which shows the average of Riegel and Cameron with both lines underneath. The Quick Predict tab shows the Riegel mile alone.
How do you predict race pace?
Predict the finish time first, then divide it by the distance. A 25:00 5K predicts a 3:59:47 marathon on Riegel, and 3:59:47 over 26.2188 miles is 9:09 per mile. The Pace tab does the division for you when you enter the distance and the predicted time.
Does this work as a Tanda based calculator?
No. The Tanda method (Giovanni Tanda, Journal of Human Sport and Exercise, 2011) predicts mean marathon pace from an 8-week training window using weekly distance and mean training pace, not from a race result. This predictor takes a race result and runs Riegel and Cameron, so it does not use your training log.
Why are my race predictions different from my real times?
Several factors cause predictions to differ from reality. Training specificity is the biggest one: a runner who trains mostly short intervals will outperform predictions at shorter distances and underperform at longer ones. Weather, course terrain, elevation, race experience, fueling strategy and mental toughness all affect the outcome but are not accounted for in the formulas.
What is the Riegel exponent and why does it matter?
The Riegel exponent (1.06) represents the rate at which performance declines as distance increases. A higher exponent means more slowdown per unit of distance. Riegel's 1981 American Scientist paper, Athletic Records and Human Endurance, applied it to running, swimming and walking efforts lasting about 3.5 to 230 minutes. Some calculators change the exponent because 1.06 can give long race predictions that many runners do not reach, which fits the 2016 finding that Riegel marathon times run fast for half of recreational runners.
How recent should my input race be?
For the most accurate predictions, your input race should be from the last 6 to 8 weeks. Older results may not reflect your current fitness. The race should also be a genuine all-out effort on a standard course with fair weather. A time trial or a very hilly race will produce less reliable predictions.
Are predictions more accurate for shorter or longer distances?
Predictions hold up best when the target is within 4x of the input distance and shorter than the marathon. Predicting a 10K from a 5K (2x) is more reliable than predicting a marathon from a 5K (8.4x), and reliability keeps falling as the ratio grows. The formulas assume equal training for both distances, so if you have not trained for the longer one the prediction will be optimistic. Use the closest race distance you have as your input.
What is the difference between this tool and a race pace calculator?
A race pace calculator converts a known distance and time into a pace per mile or kilometer. A race time predictor takes a known race performance and uses formulas to estimate what you could achieve at a different distance. The predictor accounts for the natural fatigue that occurs as distance increases, while a pace calculator simply divides.
What is a race calculator?
A race calculator helps runners plan for race day by computing pace, finish time, predictions and splits in one place. Enter your distance and time to find pace, distance and pace to find time, a past result to predict a new distance, or a target time to generate mile by mile splits. The tabs on this page do all four. A plain pace calculator typically only converts between distance, time and pace.
How do I calculate my race pace?
Divide your total race time in seconds by the distance in miles or kilometers. A 1:45:00 half marathon is 6,300 seconds divided by 13.1 miles, which equals 481 seconds per mile, or about 8:01 per mile. The Pace tab does the conversion automatically when you enter distance and time.
What is a good pace for a beginner race?
There is no single good pace for a first race. Start from a pace you already hold on training runs, run the first mile a little slower than that, and aim to finish feeling strong. Enter a recent training run in the Pace tab to see that pace per mile or km. Once the first race is done, its result gives you a real number to predict from and a time goal for the second attempt.
How do I use splits to pace my race?
Splits break your race into individual mile or kilometer segments with cumulative times. Print your splits or write them on your arm before the race, then check each mile marker against your split sheet to know if you are on target. Aim for even splits or slightly negative splits, with the second half faster than the first.
Should I run even splits or negative splits?
Negative splits (second half faster) are generally the best strategy. Start 5 to 10 seconds per mile slower than your goal pace for the first couple of miles. Settle into target pace in the middle. Pick up the pace in the final 20 to 30 percent if you feel good. This prevents the common mistake of starting too fast and fading badly in the final miles.
How many weeks of training do I need for each race distance?
General guidelines: a 5K requires 6 to 8 weeks of consistent running, a 10K 8 to 10 weeks, a half marathon 10 to 14 weeks and a marathon 16 to 20 weeks. These assume a base fitness of at least 15 to 20 miles per week. Starting from zero adds additional weeks to build up safely.

