Race time predictor

Race time prediction estimates how fast you can complete a target distance based on a performance you have already demonstrated. It converts a known data point — your actual race result — into a planning anchor for a different distance.

This matters because most runners race multiple distances throughout a season. A 10K specialist considering a half marathon needs a realistic time target to set pacing, fueling, and training structure. Without a prediction framework, runners either aim too aggressively (risking a blow-up) or too conservatively (leaving performance on the table).

Prediction models are planning tools, not guarantees. They work best when the source race is recent, the effort was genuine, and you have trained specifically for the target distance. The prediction sets a range; your race-day execution determines where you land within it.

The dominant model in recreational running is the Riegel formula, published in 1981. It describes an empirical power-law relationship between race distance and race time: as distance increases, pace slows at a predictable rate governed by a "fatigue exponent."

The VDOT system from Jack Daniels takes a different approach: it converts your race time into an estimated oxygen cost and percent-VO2max utilization, producing a performance index. That index then maps to training paces and race equivalents across distances. While VDOT uses physiological modeling rather than a pure power law, the practical outputs are broadly consistent with Riegel for standard road distances.

Both models share the same core assumption: that your performance at one distance reflects a level of aerobic fitness that transfers predictably to other distances, provided you are adequately trained for each.

Predictions are most reliable when conditions are controlled and input quality is high. Several factors introduce systematic error:

Race predictions are most valuable when used as planning anchors, not as rigid targets. Here is how experienced runners and coaches apply them:

• Set realistic goal ranges: Use the conservative-to-moderate prediction range as your goal window. Plan pacing around the conservative estimate and adjust upward only if you feel strong in the second half.
• Structure pacing bands: Convert the predicted finish time into per-mile or per-km splits. Aim for even or slightly negative splits — starting conservatively and finishing strong is the most reliable race execution strategy (Abbiss and Laursen).
• Validate with tune-up races: Before a goal marathon, run a tune-up half marathon or 10K. Compare the result to predictions to calibrate your planning.
• Guide training intensity: If your predicted marathon pace is 5:30/km, your marathon-pace long runs should target that pace. Use the prediction to set training speeds for tempo, threshold, and race-specific sessions.

• Using training run data as input: A comfortable 10K training run is not a 10K race effort. Always use an actual race or time trial result.
• Ignoring distance-specific preparation: Predicting a marathon from a 5K without marathon training is like estimating a bench press from a deadlift — the correlation exists but the specificity gap is large.
• Racing the aggressive prediction: The aggressive scenario assumes everything goes right. Most runners perform closer to the moderate estimate. Racing too fast early leads to the classic "positive split blow-up" in the final quarter.
• Neglecting conditions: A prediction based on a cool-weather 10K does not apply to a hot-day marathon. Always account for expected race-day conditions.
• Over-relying on a single model: No prediction model captures the full complexity of race performance. Use predictions as one input alongside training feedback, recent fitness trends, and coaching judgment.

This tool uses the Riegel formula as its primary prediction engine, enhanced with optional training context adjustments: