How to Predict Your Race Time from Any Distance

Race prediction uses a single race result to estimate your finish time at a different distance. The most widely used method is the Riegel formula, which applies a fatigue exponent to scale your performance up or down. A 25-minute 5K, for example, predicts roughly a 52-minute 10K. Whether you are stepping up from a 10K to a half marathon or wondering what your marathon fitness says about your 5K speed, race prediction gives you a data-driven starting point.

The Riegel Formula

In 1977, researcher Peter Riegel published a simple power-law equation that remains the standard for race time prediction:

T₂ = T₁ × (D₂ / D₁)^1.06

Where:

• T₁ is your known race time
• D₁ is the distance of that race
• T₂ is the predicted time for the new distance
• D₂ is the target distance
• 1.06 is the fatigue exponent, reflecting the nonlinear cost of running farther

The exponent of 1.06 means that doubling the distance does not simply double your time. It adds roughly 6% on top because the body fatigues at a rate that compounds with distance. This relationship holds surprisingly well across a wide range of distances and ability levels.

Example Predictions

The table below shows predicted times from common 5K finishing times, using the Riegel formula. These assume equivalent fitness and training at each distance.

Notice that the marathon time is not simply four times the 5K time. A 25-minute 5K runner at 5:00 per kilometer would cover the marathon distance in about 3:31 at that pace, but the Riegel prediction is 3:58 because the fatigue exponent accounts for the endurance cost of running 42.2 kilometers.

Where Predictions Break Down

The Riegel formula assumes you are equally trained for both distances, and that is rarely true. Predictions tend to be optimistic at longer distances for several reasons:

• Training specificity matters. A fast 5K runner who has never run more than 10 miles in training will not hit their predicted marathon time. The formula models physiological potential, not actual race readiness.
• Fueling becomes a factor. Races under 90 minutes rely primarily on glycogen stores. Beyond that, nutrition strategy, hydration, and gut tolerance become performance variables that the formula does not account for.
• Ultra distances diverge further. Above the marathon, the 1.06 exponent underestimates fatigue. Muscle damage, sleep deprivation, and terrain make predictions unreliable beyond 50K.
• Predicting shorter from longer is more reliable than the reverse. If you have a recent marathon time, your predicted 10K is likely accurate because you have already demonstrated the aerobic base.

VDOT: A More Sophisticated Approach

Legendary coach Jack Daniels developed the VDOT system as a more nuanced alternative. VDOT is not a direct VO2max measurement but a single number that represents your current running fitness based on race performance. A 20-minute 5K corresponds to roughly a VDOT of 45, while a 16-minute 5K sits around VDOT 58.

The advantage of VDOT over raw Riegel predictions is that Daniels built his tables from thousands of actual race performances rather than a single mathematical exponent. His data captures the real-world relationship between distances more accurately, especially at the extremes.

VDOT also maps your fitness to training pace zones, which makes it a complete training system rather than just a prediction tool. Once you know your VDOT, you can derive your easy pace, tempo pace, interval pace, and repetition pace from a single lookup.

Training Paces from Race Results

One of the most practical applications of race prediction is deriving your daily training paces. Using a recent race result, you can calculate the following zones:

• Easy pace — 60-70% of race intensity. For a 25-minute 5K runner, this is roughly 6:15-6:45 per kilometer. Most of your weekly mileage should be at this effort.
• Tempo pace — your lactate threshold pace, roughly equivalent to a pace you could sustain for 60 minutes in a race. For the same runner, approximately 5:15-5:25 per kilometer.
• Interval pace — VO2max training, run in 3-5 minute repeats with equal rest. This approximates 3K to 5K race pace, around 4:50-5:00 per kilometer for a 25-minute 5K runner.
• Repetition pace — short, fast repeats of 200-400 meters for neuromuscular speed. Faster than 5K pace, typically 4:20-4:35 per kilometer.

These paces work because they target specific physiological systems. Running too fast on easy days compromises recovery, while running too slow during intervals fails to trigger VO2max adaptation. A race result anchors all of your training to your actual fitness rather than to an arbitrary number.

How to Use Predictions Wisely

Race predictions are a planning tool, not a guarantee. The most common mistake is treating a predicted time as an automatic outcome. A few guidelines for using predictions effectively:

• Use your most recent race result. A 5K time from three years ago does not reflect your current fitness. Ideally, use a result from the past 6-8 weeks.
• Train for the distance. If you are predicting a marathon time from a 5K, you still need to build up to 50-70 kilometers per week with long runs of 30-35 kilometers. The prediction tells you what is possible, not what is automatic.
• Set a range, not a single target. Use the prediction as the fast end of a realistic window. Add 3-5% for your conservative goal and 5-10% for a safe pacing strategy in your first race at a new distance.
• Retest regularly. As your training progresses, run a tune-up race to update your predictions. A 5K time trial 4-6 weeks before your goal race gives you a fresh data point.

Factors That Affect Race Performance

Even with perfect training, external factors can shift your actual finish time by 5-15% relative to a prediction. Consider these variables when setting race-day expectations:

• Course elevation. A hilly course adds roughly 12-15 seconds per mile for every 100 feet of net elevation gain. Downhill courses can be faster but increase eccentric muscle damage.
• Weather. Heat is the biggest performance killer. Research shows a 1-2% pace slowdown for every 5 degrees Celsius above 15 degrees. Wind and humidity compound the effect.
• Taper. A proper 2-3 week taper that reduces volume by 40-60% while maintaining intensity can improve race performance by 2-3%. Skipping the taper leaves free speed on the table.
• Race-day nutrition. For races over 90 minutes, taking in 30-60 grams of carbohydrate per hour prevents late-race glycogen depletion. Practice your fueling strategy in training.
• Pacing strategy. Even splits or a slight negative split (running the second half faster) outperform aggressive starts. Going out 10 seconds per mile too fast in a marathon can cost minutes in the final 10K.