# Race Time Predictor

- **URL:** https://codeasystem.com/calculators/fitness/race-time-predictor-calculator/
- **Category:** fitness
- **Description:** Predict finish times at new race distances from a recent result using the Riegel formula; from 5K through the marathon.
- **Primary output:** Predicted time for 21.0975 km: 1:50:19

## Inputs
- Recent race distance (name: `recentDistance`, type: select)
- Finish time (name: `finishTimeMinutes`, type: number, example: 50)
- Target race distance (name: `targetDistance`, type: select)

## Outputs
- Predicted time for 21.0975 km: 1:50:19
- Equivalent average pace: 5:14 min/km
- Prediction basis: Riegel exponent 1.06 from a 10 km result of 50:00

## Formula / methodology
```
T₂ = T₁ × (D₂ ÷ D₁)^1.06
```

Peter Riegel’s 1977 empirical model scales a known performance to any other distance using the exponent 1.06; slightly worse than linear, capturing the aerobic endurance premium of longer races. It remains the standard used by Runner’s World, Strava and most race predictors.

The prediction assumes equivalent training commitment for the new distance; entering a fresh all-out 10K and reading a marathon time presumes you actually put in marathon mileage.

## Assumptions & limitations
- Recent race was a genuine hard effort on flat terrain.
- Comparable training volume for the predicted distance.
- Exponent 1.06 fits middle-distance-to-marathon spans best.

## How to use
1. **Choose your recent race**; The fresher and harder the effort, the better; ideally within the last six weeks.
2. **Enter the finish time**; Decimal minutes: 1:52:30 for a half equals 112.5.
3. **Pick a target distance**; Read the projected clock time plus the required average pace per kilometre.

## Example
A 50-minute 10K projects to roughly 1:50 for a half marathon; provided long-run training backs up the ambition.

Result for these inputs:

```
Predicted time for 21.0975 km: 1:50:19
```

## About this calculator
### Where Riegel comes from

Analyzing world-record performances across distances, Riegel found time grew almost with distance^1.07; he published 1.06 for trained athletes, and five decades of race-data validation have kept it in place essentially unchanged.

### Short vs long predictions behave differently

Projecting down (half → 10K) tends to be optimistic unless you train speed; projecting up (10K → marathon) is optimistic unless you train endurance. The formula describes physiology, not your training log; close the gap with specific work.

### Making the prediction reality

- Match weekly long-run percentage to the target event.
- Add race-pace tempo sessions at the predicted pace.
- Retest with a tune-up race to recalibrate before the big day.

## FAQs
### Can I predict a marathon from a 5K?

Technically yes, practically poorly; the training-specificity gap grows with distance ratio. Use the closest available distance, ideally no more than 2× apart.

### Why does everyone quote 1.06?

It fits elite and recreational data reasonably across road distances; alternatives (1.04–1.08) tweak hot-weather or ultra cases but rarely change decisions.

### My predicted marathon seems too fast

Almost always a fueling or mileage gap rather than a formula problem. Compare your longest long run and weekly volume against marathon norms.

## Related calculators
- [Running Pace Calculator](https://codeasystem.com/calculators/fitness/running-pace-calculator/)
- [VO2 Max Calculator](https://codeasystem.com/calculators/fitness/vo2-max-calculator/)
- [Target Heart Rate Calculator](https://codeasystem.com/calculators/fitness/target-heart-rate-calculator/)
- [Calories Burned Calculator](https://codeasystem.com/calculators/fitness/calories-burned-calculator/)

---
Last updated: 2026-08-23 · Version: 1.0.0 · [HTML version](https://codeasystem.com/calculators/fitness/race-time-predictor-calculator/)