Race Time Predictor: What One Race Actually Tells You (5K to 100 Miles)
Race Time Predictor: What One Race Actually Tells You (5K to 100 Miles)¶
I built a free race time predictor. You enter one recent race result — distance and finish time — and it spits out predicted finish times across every major distance from 5K to 100 miles. No signup, no account, no email required.
Try it here: Race Time Predictor
It takes about 20 seconds to use. But before you plug in your numbers and start planning your 100-mile debut off a 5K PR, I want to explain exactly what this tool does, why the math works, and where it stops being useful.
The Formula Behind It (Plain English)¶
The predictor uses the Riegel formula, developed by researcher Peter Riegel and published in American Scientist in 1981. The equation is:
T2 = T1 × (D2 / D1)^1.06
Where T1 is your known finish time, D1 is that race distance, D2 is the distance you want to predict, and T2 is the predicted time.
The exponent — 1.06 — is the key. If the exponent were exactly 1.0, the prediction would be simple proportional scaling (twice the distance equals twice the time). But running doesn't work that way. You slow down as distance increases, because fatigue accumulates faster than distance does. The 1.06 exponent captures that degradation curve.
Riegel derived this exponent by fitting it against a large dataset of world-record performances across distances. It's been validated against real-world finishing times at distances from roughly 800 meters up to the marathon, and for most runners in that range, it's a reasonably accurate model of the relationship between race distance and finishing time.
That range matters, and I'll come back to it.
What the Tool Gets Right¶
For distances that are reasonably close to your input distance, the formula holds up well. Some examples of what it does reliably:
- You have a recent half marathon time, and you want to know if a marathon PR is realistic.
- You ran a 10K last month and want a realistic 5K goal for an upcoming race.
- You're considering signing up for a 50K and want a rough time estimate based on a recent marathon.
In these cases — input and target distances within roughly a factor of two of each other — the Riegel formula is a well-validated starting point.
The tool is also completely honest in one important way: it doesn't pretend to be more than it is. A prediction is not a training plan. It's a ceiling estimate under ideal conditions.
Where It Gets Shakier: The Extrapolation Problem¶
A single race result is a weak proxy for your actual fitness. This gets worse the further you extrapolate.
Riegel's original validation was primarily across distances up to the marathon. When you use a 5K result to predict a marathon — an 8x difference in distance — you're asking the formula to extrapolate far beyond what it was calibrated on. The math still produces a number. That number is less trustworthy.
Think of it like this: a weather forecast is quite accurate for tomorrow, pretty good for 3 days, uncertain at a week, and speculative at two weeks. The Riegel formula works the same way. Predicting your 10K time from a 5K is a solid forecast. Predicting your marathon from a 5K is two weeks out.
There's also a fitness-specific problem. A single race captures your performance on a specific day, under specific conditions, with specific training behind it. It says nothing about your aerobic base, your weekly mileage, how consistent your last 12 weeks were, or how your fitness is trending. Two runners can run the same 5K time and have wildly different marathon potential, because one has 60-mile weeks of aerobic base behind it and the other has four weeks of training after a long break.
Why Ultras Are Different¶
Beyond the marathon, the Riegel formula with its standard 1.06 exponent systematically under-predicts finish times. Ultras are slower, relative to the formula, than marathons are.
The reasons are well understood: cumulative fatigue compounds nonlinearly at extreme distances, mandatory aid station stops add time, navigation slows you down, and most ultras involve significant elevation gain and trail terrain that road pace can't account for.
The predictor uses a higher exponent — 1.08 — for distances beyond the marathon. This correction brings ultra predictions closer to real-world finishing times for trail and ultra events.
But even with that adjustment, I want to be direct: if you're extrapolating from a road race to a 50-mile or 100-mile trail event, the number is a rough ceiling, not a race plan. Vertical gain, terrain, heat, crew logistics, and time-on-feet are the variables that actually determine your ultra finish time. The formula knows none of these. A road marathon time can tell you whether you're in the ballpark for a 50K, but it can't tell you whether you'll finish a mountain 100 in 24 hours or 30 hours or at all.
One Race vs. Your Actual Training Data¶
Here's the honest pitch for why this tool is a starting point, not an endpoint.
A single race result treats fitness as static. Your training history treats fitness as a trend. These are fundamentally different things, and trend data is much more predictive.
If you ran a 4:10 marathon two years ago and you've been building mileage steadily since then, your current marathon shape is probably significantly better than 4:10 — but the predictor has no way to know that. It will output 4:10 as if today is race day.
NavRun's race predictions feature pulls your last 8 weeks of Strava data and estimates your current fitness based on what you've actually been doing — not what you did once. It factors in your recent pace, your weekly mileage, and whether your fitness is trending up or down. The result is a prediction that reflects your current shape, not a historical snapshot.
The free predictor tool is useful if you have a race result and want a quick number. The training-based predictions are useful if you want to know what you're actually capable of right now.
How to Use It Honestly¶
A few guidelines that will help you get value from the tool:
Use a recent result. A race from 8+ weeks ago is less informative than one from last weekend. Training changes fast.
Use a comparable distance when possible. A half marathon predicting a marathon is better than a 5K predicting a marathon. The closer the distances, the more accurate the extrapolation.
Treat ultra predictions as ballpark figures. If the tool says 12 hours for a 50-miler, think "somewhere between 11 and 14 hours, depending on terrain and conditions" — not "my goal is 12:00:00."
Read the race day pacing article. Knowing your predicted time is only useful if you know how to pace to it. Race Day Pacing: Negative vs. Even Splits covers how to translate a finish time goal into a mile-by-mile execution plan.
Try It¶
The tool is free. No login. No email. No upsell during use.
Race Time Predictor → /tools/race-time-predictor/
If you want predictions grounded in your actual training — not a single data point — connect your Strava and NavRun will read your last 8 weeks and build estimates from there.
See training-based race predictions →
Related: