Race Predictor Calculator - Riegel Race Time Forecast

A race predictor calculator estimates your finish time, pace, and speed at a different distance by applying Pete Riegel's 1977 formula to a recent race or time-trial result. Runners, triathletes, and coaches use it to test how a known 5K, 10K, half marathon, or mile effort translates into another distance. The calculation is fast, reproducible, and works in kilometers or miles.

• • Predict a marathon from a half marathon: Convert a measured half-marathon result into a realistic marathon finish time, pace, and average speed.
• • Plan a 10K or half-marathon goal: Use a recent 5K or 10K race as the baseline to forecast a target time on a longer standard distance.
• • Compare training efforts across distances: Translate a track repeat, tempo run, or time trial at one distance into an equivalent finish time elsewhere.
• • Set realistic pace targets for race day: Read the predicted pace per kilometer or mile to plan splits, fueling intervals, and pacing strategy.

The tool answers a narrow question: if I just ran X distance in Y time, what could I run at a different distance tomorrow? It does not adjust for heat, altitude, course profile, or fatigue; those factors are reviewed separately. Predictors built around Riegel's formula have been used since the late 1970s because the exponent 1.06 captures a steady fatigue curve for trained distance runners. The output is a planning anchor.

For a focused look at pace without the distance translation, Pace Calculator works directly from a known pace and distance.

The conversion step turns both distances into a shared unit and applies Riegel's formula to estimate the new finish time.

• Known time: Hours, minutes, and seconds converted to total seconds (1 h = 3,600 s, 1 min = 60 s).
• Known distance: Distance of the recent race or time trial, converted internally to kilometers using 1 mi = 1.609344 km.
• New distance: Target distance you want a predicted time for, also converted internally to kilometers.
• Exponent 1.06: Pete Riegel's published running-fatigue constant for trained distance athletes.

The exponent 1.06 is the heart of the formula. If race times scaled linearly with distance, doubling the distance would simply double the time. In practice, fatigue and slower paces on longer efforts mean that doubling the distance more than doubles the time, so the ratio is raised to a power slightly above 1.0.

Predicted pace and average speed are derived outputs. Pace is the predicted time divided by the chosen unit; speed is the chosen distance divided by predicted time in hours (mph for miles, km/h for kilometers). The race predictor uses the 1.609344 kilometers-per-mile conversion that NIST publishes so kilometer and mile entries stay consistent.

According to Vickers and Vertosick (BMC Sports Science, Medicine and Rehabilitation, 2016), Riegel's race-time formula predicts finish time as T2 = T1 x (D2/D1)^k with k of 1.08 for elite runners and 1.05 to 1.06 for recreational male runners aged 40 to 70. The race predictor uses the standard k = 1.06.

Once the predicted time is known, Running Pace Race Split Calculator turns that finish time into per-kilometer or per-mile splits for race-day pacing.

Four ideas keep the prediction from being misread as a personal-best forecast: same-distance vs cross-distance comparisons, the meaning of the 1.06 exponent, how pace and speed relate, and how kilometers and miles convert.

These four ideas work together. Riegel's exponent assumes the runner is trained for the new distance with similar effort and conditions. Pace and speed translate the result into something usable on race day, and the kilometer/mile conversion keeps the prediction accurate regardless of source units.

When the comparison is between two results at the same distance rather than across distances, Race Time Improvement Calculator reports time saved and percent change.

Enter the recent race result, pick the new distance, and read the predicted finish time, pace, and speed in the chosen unit. The same steps work for road, track, and trail distances.

1. 1 Enter the known race distance and unit: Add the distance of the recent race in the chosen unit.
2. 2 Enter the known finish time: Add hours, minutes, and seconds exactly as the timing source reports them. Chip, gun, and watch times are all acceptable, but stay consistent across comparisons.
3. 3 Enter the new distance and unit: Choose the target distance and use the same unit as your training plan or race entry.
4. 4 Read the predicted finish time: Use the predicted h:mm:ss as a goal benchmark and combine it with course knowledge to set a realistic range.
5. 5 Plan splits from the predicted pace: Translate the predicted pace into per-kilometer or per-mile splits for race-day pacing.

A runner who logs a recent 5K at 22:30 enters 5 as the known distance, 0:22:30 as the time, and 10 as the new distance. The calculator returns 46:55, 4:41 per kilometer, and 12.79 km/h, anchoring a 4:40-4:45 pace target.

A predicted marathon time becomes a pace plan when Marathon Pace Calculator converts that finish time into the pace needed across 26.2 miles.

A race predictor turns a single completed effort into a multi-distance planning tool without extra training data or expensive software.

• • Translate one result into many distances: A recent 5K, 10K, or half-marathon effort can be projected to 10K, half, marathon, or mile times without running each distance first.
• • Set race-day pacing benchmarks: Predicted pace per kilometer or mile becomes the starting point for splits, fueling intervals, and walk-break plans.
• • Compare training plans against a standard: A predicted time gives a numeric target to compare against training paces and long-run finishes across a build cycle.
• • Switch between kilometers and miles: The calculator accepts both units so a 5K, 10K, or marathon result in miles can predict a kilometer-based race.
• • Coach runners without their full training log: Coaches can use one verified race result to estimate a goal time without needing power, heart rate, or training history.

The biggest practical benefit is reducing guesswork. Picking a goal time for a first marathon or trail event is hard without a reference. Riegel's formula gives a defensible benchmark the runner refines once training data and course information are layered on top. For clubs, the tool also seeds runners into waves when only one recent effort is available.

For athletes who stack swim, bike, and run segments, Triathlon Finish Time Calculator adds the predicted times together to estimate an overall finish.

Riegel's formula assumes a specific set of training and racing conditions. Several real-world factors change the meaning of the prediction and are worth reviewing before locking in a goal time.

• • The calculator uses only distance and time. Heart rate, lactate threshold, VO2 max, training load, and fatigue are not part of the calculation.
• • Riegel's exponent was derived from adult runners and does not include age-grade or sex-specific curves. Age-graded tables are a better choice when comparing across age groups.
• • The 1.06 exponent is a population average. Any individual runner's fatigue curve will deviate from it.

According to World Athletics - 2025 Scoring Tables, its 2025 scoring tables use statistical performance data from 2022 to 2024 to compare performances across events. Scoring tables answer a different question than Riegel's formula: they estimate how good a single performance was relative to other athletes.

Treating the prediction as a planning anchor rather than a personal-best forecast is the safest use of the tool. Choose a realistic goal pace, then adjust it once course and weather are known.

When the predicted distance falls in the 13.1-mile range, Half Marathon Pace Calculator turns that finish time into a per-mile pacing plan specific to the half marathon.