Race Prediction Calculator

Predict your race times for any distance based on recent performance

Recent Race Performance

Hours
Minutes
Seconds
Your VDOT
Jack Daniels' running score
38.3

Base Performance

25:00
5 km @ 5:00/km

Race Predictions

5K(5 km)
25:00
5:00/km
10K(10 km)
52:07
5:13/km
15K(15 km)
1:20:07
5:20/km
Half Marathon(21.0975 km)
1:55:00
5:27/km
Marathon(42.195 km)
3:59:47
5:41/km
50K(50 km)
4:47:02
5:44/km
100K(100 km)
9:58:27
5:59/km

Training Paces

Easy/Long
65-79% effort
6:30/km
Marathon Pace
80-85% effort
5:30/km
Threshold
88-92% effort
4:51/km
Interval
95-100% effort
4:30/km
Repetition
105%+ effort
4:06/km

What Is a Race Prediction Calculator?

A race prediction calculator estimates your finish time for a target race distance based on a recent race performance. Rather than guessing, you provide one data point — say, a 5K or 10K time — and the calculator applies a scientifically grounded fatigue model to project how long you would take to cover longer (or shorter) distances.

The core insight is that runners slow down at a predictable, non-linear rate as distance increases. A runner who races a 10K at 5:00 per kilometre cannot simply double that time for a 20K; the body accumulates fatigue in a way that demands progressively more conservative pacing. Prediction models quantify that slowdown using an exponential relationship between time and distance.

This race time predictor goes further by computing your VDOT (VO₂max equivalent), derived from the famous Jack Daniels running formula, and your five key training pace zones. Together these outputs let you plan goal races, gauge fitness, and structure workouts — all from a single recent effort.

The calculator supports every standard road race distance from 5K through 100K, making it equally useful for a first-time 10K runner scoping a half marathon debut and an experienced ultrarunner projecting 50K performance from a recent marathon. Results display in hours:minutes:seconds and show pace per kilometre and per mile, so you can use whatever unit system you prefer.

Whether you call it a race time predictor, a finish time estimator, or a running pace calculator, the underlying math is the same: a well-validated equation that has been used by coaches and athletes for over four decades to set realistic goals, build confident race-day strategies, and measure improvement across training cycles.

The Riegel Formula and How Race Prediction Works

The primary formula this calculator uses is the Riegel formula, published by Peter Riegel in a 1977 paper in American Scientist. It remains the gold standard for running race prediction and is the basis of most prediction tools used by coaches and running apps worldwide.

The formula models the relationship between race time and distance as a power function. The exponent — 1.06 for most road race distances — captures the physiological reality that effort does not scale linearly with distance. Riegel derived this constant by fitting performance data from elite athletes across many distances, and subsequent research has validated it for recreational runners too.

The calculator applies a slightly higher exponent for the marathon (1.08) and ultra distances like the 50K (1.10), reflecting the additional physiological demands of very long efforts — glycogen depletion, heat stress, and cumulative musculoskeletal fatigue all cause a steeper slowdown at extreme distances.

A secondary Cameron formula is also computed for reference. It uses a linear correction factor that adds a small penalty proportional to the difference in distance, giving a slightly different estimate that some coaches find useful for cross-checking.

Riegel Race Prediction Formula

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

Where:

  • T₂= Predicted finish time for the target distance (seconds)
  • T₁= Known finish time for the base distance (seconds)
  • D₂= Target race distance (km)
  • D₁= Base (known) race distance (km)
  • e= Fatigue exponent: 1.06 for 5K–21K, 1.08 for marathon, 1.10 for 50K+

VDOT Score and Your Five Training Pace Zones

Alongside race predictions, this calculator outputs your VDOT, the aerobic capacity equivalent made famous by legendary coach Jack Daniels. VDOT is not a direct VO₂max measurement — it is a performance-based index derived from your race time and distance that correlates closely with maximal oxygen uptake. A higher VDOT means a more aerobically fit runner.

The VDOT calculation converts your race performance into a running velocity (in metres per minute), estimates the VO₂ demand of that velocity, and then adjusts for the percentage of VO₂max you can sustain over the race duration. The result is a single number — typically between 30 (beginner) and 85+ (elite) — that lets you compare fitness across different distances and track improvement over time.

From your base pace, the calculator also derives five training pace zones:

  • Easy/Long (×1.3 of base pace): Conversational aerobic runs that build your aerobic base without accumulating fatigue. These should make up 65–80% of your weekly volume.
  • Marathon Pace (×1.1): Comfortably hard, sustainable for up to four-plus hours. Used in long run segments and medium-long tempo efforts.
  • Threshold/Tempo (×0.97): Comfortably hard lactate threshold work. Classic 20–40 minute continuous tempo runs or cruise intervals.
  • Interval/VO₂max (×0.90): Short, hard efforts at or near VO₂max. Typical 800m–1 mile repeats to develop top-end aerobic capacity.
  • Repetition/Speed (×0.82): Very fast, short efforts (200m–400m) to build neuromuscular economy and raw speed.

Training at these prescribed intensities, rather than running every session at the same moderate effort, is the cornerstone of structured running training. The zones are personalised to your current fitness, making the race prediction calculator a complete training planning tool, not just a goal-race estimator.

Accuracy, Limitations, and When to Trust the Numbers

The Riegel formula is remarkably accurate for runners who are well-trained for the target distance. Studies show prediction errors within 2–5% for most runners when predicting between adjacent distances — for example, using a 10K to predict a half marathon. Errors grow when predicting across very large distance gaps (5K to marathon) or when training history does not include long efforts at race effort.

The key limitation is that the formula assumes equivalent training and fitness for both distances. A runner who has only trained for 5K speed but has never done long runs will perform worse on the marathon than the formula predicts, because their aerobic base and long-run fuelling capacity are underdeveloped. Conversely, a high-mileage runner who has specifically prepared for the marathon may beat the Riegel prediction by running more efficiently at longer distances than their 5K time implies.

Other factors the formula does not account for include:

  • Course profile (hills, turns, terrain type)
  • Weather conditions (heat, humidity, wind)
  • Pacing strategy (going out too fast is the most common reason runners underperform predictions)
  • Race-day nutrition and hydration execution
  • Injury, illness, or tapering status at race time

Despite these caveats, race prediction calculators are used at every level of the sport. The IAAF, World Athletics, major marathon organisers, and coaching organisations routinely reference Riegel-based models for seeding, goal-setting, and qualification standards. Using the prediction as a starting point and then adjusting conservatively for course difficulty and your training specificity is the most practical approach.

As a rule of thumb: if your most recent race was more than 8–12 weeks ago, or if you have significantly changed your training volume since then, the prediction reflects your past fitness, not your current level. Regular re-entry of fresh race results keeps the calculator aligned with where you actually are.

How to Use This Race Prediction Calculator

Using the calculator is straightforward. Enter your most recent race distance in kilometres — use the quick-select buttons for 5K, 10K, half marathon, or full marathon — and input your finish time in the hours, minutes, and seconds fields. The results update instantly.

The Race Predictions table shows Riegel-formula projected times for 5K, 10K, 15K, half marathon, marathon, 50K, and 100K, along with your projected per-kilometre pace for each distance. The Training Paces panel below it shows your five training zones derived from your base performance. Your VDOT appears prominently so you can track it race to race as a fitness benchmark.

To get the most useful output:

  1. Use a recent, well-executed race rather than a training run time. You naturally run closer to your true maximum in a race, which gives the formula the data it needs.
  2. Choose a distance close to your target whenever possible. A half marathon time predicts a marathon time more accurately than a 5K time does.
  3. If you are targeting a mountainous course, a city marathon with many turns, or a trail race, mentally add 3–10% to the predicted time depending on difficulty.
  4. Use the projected training paces to structure your next training block, not just to set a race goal. Running easy days at the right pace is especially important — most recreational runners train their easy runs too fast.

The calculator is a decision-support tool. Use the prediction to set an ambitious but realistic goal, build a race-day pacing plan, and communicate your current fitness level to a coach or training partner. Combine it with experience and course knowledge for the best race-day result.

Worked Examples

5K Runner Predicting a Marathon Time

Problem:

A runner recently ran a 5K in 25:00. What does the Riegel formula predict for a marathon?

Solution Steps:

  1. 1Convert the 5K time to seconds: 25 × 60 = 1,500 seconds.
  2. 2Apply the Riegel formula with the marathon-adjusted exponent (1.08): T₂ = 1500 × (42.195 / 5)^1.08.
  3. 3Calculate the distance ratio: 42.195 / 5 = 8.439.
  4. 4Raise 8.439 to the power of 1.08: 8.439^1.08 ≈ 10.01.
  5. 5Multiply: 1500 × 10.01 = 15,015 seconds.
  6. 6Convert to hours:minutes:seconds: 15,015 ÷ 3600 = 4 hours, 10 minutes, 15 seconds → 4:10:15.

Result:

Predicted marathon time: 4:10:15 (average pace ≈ 5:55/km)

10K Runner Projecting a Half Marathon

Problem:

A runner ran a 10K in 50:00 flat. What half marathon time can they expect?

Solution Steps:

  1. 1Convert 50:00 to seconds: 50 × 60 = 3,000 seconds.
  2. 2Apply the Riegel formula with standard exponent (1.06): T₂ = 3000 × (21.0975 / 10)^1.06.
  3. 3Distance ratio: 21.0975 / 10 = 2.10975.
  4. 4Raise 2.10975 to the power of 1.06: 2.10975^1.06 ≈ 2.2063.
  5. 5Multiply: 3000 × 2.2063 = 6,619 seconds.
  6. 6Convert: 6619 ÷ 3600 = 1 hour, 50 minutes, 19 seconds → 1:50:19.

Result:

Predicted half marathon time: 1:50:19 (average pace ≈ 5:14/km)

Half Marathon to Full Marathon Prediction

Problem:

A runner finished a half marathon in 1:45:00. What marathon time does the calculator project?

Solution Steps:

  1. 1Convert 1:45:00 to seconds: (1 × 3600) + (45 × 60) = 3600 + 2700 = 6,300 seconds.
  2. 2Marathon prediction uses the adjusted exponent of 1.08: T₂ = 6300 × (42.195 / 21.0975)^1.08.
  3. 3Distance ratio: 42.195 / 21.0975 = 2.0 exactly.
  4. 4Raise 2.0 to the power of 1.08: 2.0^1.08 ≈ 2.1141.
  5. 5Multiply: 6300 × 2.1141 = 13,319 seconds.
  6. 6Convert: 13,319 ÷ 3600 = 3 hours, 41 minutes, 59 seconds → 3:41:59.

Result:

Predicted marathon time: 3:41:59 (average pace ≈ 5:16/km)

Deriving Training Paces from a 5K Time

Problem:

A runner ran 5K in 25:00. What are their prescribed training pace zones?

Solution Steps:

  1. 1Base pace per km: 1500 seconds ÷ 5 km = 300 sec/km = 5:00/km.
  2. 2Easy/Long pace (×1.3): 300 × 1.3 = 390 sec/km = 6:30/km.
  3. 3Marathon pace (×1.1): 300 × 1.1 = 330 sec/km = 5:30/km.
  4. 4Threshold/Tempo pace (×0.97): 300 × 0.97 = 291 sec/km = 4:51/km.
  5. 5Interval/VO₂max pace (×0.90): 300 × 0.90 = 270 sec/km = 4:30/km.
  6. 6Repetition/Speed pace (×0.82): 300 × 0.82 = 246 sec/km = 4:06/km.

Result:

Training zones range from 6:30/km (easy) to 4:06/km (speed repetitions)

Tips & Best Practices

  • Use a race performance from the last 8–12 weeks for the most accurate predictions — older results may not reflect your current fitness level.
  • For hilly or trail courses, add 5–15% to the predicted finish time depending on total elevation gain.
  • The Riegel formula is most accurate when predicting between distances within roughly 3× of each other; larger jumps (e.g. 5K to marathon) carry more uncertainty.
  • Run your easy training days genuinely easy — the calculator's easy pace is slower than most runners expect, and that is by design.
  • Re-enter a new result after every race to track your VDOT trend over time; consistent VDOT gains are a reliable sign of improving fitness.
  • For a debut marathon, use a half marathon time as your input rather than a 5K or 10K — it is physiologically closer and gives a more reliable projection.
  • Treat the predicted marathon pace as a ceiling on your first few miles, not a floor — going out too fast is the single biggest cause of marathon blowups.
  • Training pace zones are specific to your current fitness; recalculate them after every significant race or fitness test to keep workouts appropriately challenging.

Frequently Asked Questions

For runners with comparable training for both distances, the Riegel formula typically predicts within 2–5% of actual race performance. Accuracy is highest when predicting between adjacent distances — such as 10K to half marathon — and decreases for larger jumps like 5K to marathon. Factors the formula cannot account for include course terrain, weather, pacing strategy, and whether your training has specifically prepared you for the target distance.
The standard Riegel exponent of 1.06 was derived primarily from data on distances up to the half marathon. At marathon and beyond, additional physiological stresses — glycogen depletion, muscle breakdown, and cumulative heat stress — cause a steeper slowdown than the standard exponent predicts. The calculator uses 1.08 for the marathon and 1.10 for 50K+ to better reflect the real-world performance of most runners at these distances.
VDOT is an aerobic fitness index developed by legendary running coach Jack Daniels in his book 'Daniels' Running Formula.' It represents the effective VO₂max implied by your race performance — accounting not just for your aerobic capacity but also your running economy and race execution. VDOT is useful because it lets you compare fitness across different race distances, track improvement over time, and look up evidence-based training paces. A VDOT gain of 1–2 points over a training cycle is a meaningful fitness improvement.
Always use a race time for best results. In a race environment you push closer to your physiological limit than in training, giving the formula the competitive-effort data it needs. A hard training time run on a measured course can serve as a substitute if a recent race is unavailable, but expect the prediction to be slightly conservative since most runners still hold back slightly outside of races. The more recent the performance — ideally within the last 8–12 weeks — the more accurately it reflects your current fitness.
The five training zones serve different physiological purposes and should each be used in the right proportion. Most runners should spend 70–80% of their volume at easy/long pace, which builds aerobic base without excessive fatigue. Threshold runs (one or two sessions per week) raise your lactate threshold, the most important fitness marker for distance runners. Interval and repetition sessions are the icing on top — high-quality but low-volume work that sharpens top-end speed. Running easy days too fast is the most common training mistake; let the easy pace calculation keep you honest.
The calculator includes 50K and 100K predictions using a higher fatigue exponent (1.10) to account for the extreme demands of ultra distances. These predictions are best treated as rough guides rather than precise targets, because ultramarathon performance is far more variable than road race performance — trail terrain, elevation gain, heat, night running, and fuelling strategy can all shift finish times dramatically. For ultras, experienced runners and coaches typically adjust Riegel predictions upward by 10–20% for difficult courses.
The Cameron formula uses a linear correction factor: T₂ = T₁ × (D₂/D₁) × (1 + 0.001 × (D₂ − D₁)). Unlike Riegel's pure power model, Cameron applies a penalty proportional to the absolute distance difference between races. The two formulas produce similar results for distances close together but can diverge noticeably for large distance jumps. This calculator shows both for reference; the Riegel (adjusted) prediction is typically the primary recommendation for goal-setting.

Sources & References

Last updated: 2026-06-05

💡

Help us improve!

How would you rate the Race Prediction Calculator?

<>

Editorial Note

MyCalcBuddy Editorial Team

This page is maintained as an educational calculator reference.

Source

Formula Source: Standard Mathematical References

by Various

UpdatedLast reviewed: May 2026
CheckedFormula checks are based on standard references and internal QA review.

Privacy choices

MyCalcBuddy uses necessary storage for the site to work. Optional analytics, notifications, and future advertising features stay off unless you allow them.