How to Use a Riegel Formula Calculator for Predicting Half Marathon Finish Time from a 10k Race Pace

Feed the Calculator Race Pace—Not Training Pace

Here's the fix that matters most: your Riegel formula calculator only works when you input a recent 10K race time. Not a tempo run. Not a track session where you felt fresh. An actual chip-timed 10K where you left everything on the course. The Riegel formula—T2 = T1 × (D2/D1)^1.06—is built on the assumption that T1 represents a maximal, all-out effort. Feed it a training pace, and your predicted half marathon finish time will look achievable. Feed it a race result, and you'll get a number you can actually plan around.

The distinction sounds obvious until you audit your own inputs. A runner who completes a 10K training run in 52:00 might genuinely race that same distance in 48:30. That 3.5-minute gap, when pushed through the Riegel formula calculator, swings the half marathon prediction by nearly 8 minutes. Eight minutes is the difference between a pacing strategy that works and one that collapses at mile 10.

Understand What the Formula Actually Does

Peter Riegel developed this formula in the early 1980s, and it remains the backbone of most running calculators online. The formula compares two race distances and predicts performance at the longer distance based on fatigue accumulation. The exponent—1.06—represents how much slower you become as distance increases.

The Math, Plainly

For predicting a half marathon from a 10K, the ratio of distances is fixed: 21.0975 km divided by 10 km equals 2.10975. Raise that to the 1.06 power, and you get approximately 2.207. Multiply your 10K race time by 2.207, and you have your predicted half marathon finish.

Concrete example: You race a 10K in 49:20 (2,960 seconds). Multiply 2,960 by 2.207, and you get 6,533 seconds—roughly 1:48:53. That's your Riegel-predicted half marathon time. Write it down. That number is your anchor for every pacing decision that follows.

Stop Using Stale 10K Results

This is where most runners quietly sabotage their own predictions. A 10K time from eight months ago doesn't reflect your current fitness. The Riegel formula calculator has no concept of time decay—it treats a result from last Tuesday and a result from last summer with identical weight.

The fix: use a 10K completed within the last 6 to 8 weeks. If your most recent 10K is older than that, run a 10K tune-up race or a hard, simulated 10K time trial on a flat, measured course before trusting any half marathon prediction. Your training adaptations—positive or negative—between that race and your half marathon should be minimal.

What Counts as "Recent Enough"

• Ideal: 10K raced within 4 weeks of your half marathon
• Acceptable: 10K raced within 8 weeks
• Risky: 10K raced 3 to 6 months ago (adjust prediction manually)
• Useless: Anything older than 6 months—run a new benchmark

Account for Course Difficulty Before You Trust the Number

The Riegel formula assumes equivalent course conditions for both races. It doesn't know that your 10K was run on a flat, sea-level loop while your target half marathon features 800 feet of elevation gain and a hill at mile 11. It doesn't factor in temperature, humidity, or wind.

Here's how to adjust: after the calculator gives you a raw prediction, apply a course-difficulty modifier. For a hillier half marathon than your benchmark 10K, add 2 to 5 minutes to the predicted time. For a half at significantly higher altitude, add 3 to 8 minutes depending on elevation change. For extreme heat (above 70°F at race start), add 1 to 3 minutes per 10 degrees above 55°F.

These aren't arbitrary numbers—they're based on how environmental factors compound over distance. A 10K in 75°F heat slows you by maybe 90 seconds. That same heat over 21.1 km slows you by closer to 4 minutes because thermal fatigue is non-linear.

Don't Treat the Prediction as a Target—Treat It as a Ceiling

The biggest strategic mistake runners make with a Riegel-predicted half marathon time is treating it as the goal. It's not. It's the upper boundary of what you're currently capable of under ideal conditions. Race day rarely delivers ideal conditions.

Use the prediction to set three pacing tiers:

• Conservative target: Riegel prediction + 3 to 5 minutes. This is your A-goal pace—the one you actually race at for the first 10 miles.
• Aggressive target: Riegel prediction exactly. You only pursue this if you reach mile 10 feeling strong and conditions are favorable.
• Survival pace: Riegel prediction + 8 to 10 minutes. This is your fallback if weather turns or your legs feel heavy early.

This three-tier system transforms the calculator output from a single number into a complete race strategy. You're no longer racing toward one time—you're managing a range of outcomes based on real-time feedback.

Validate the Prediction Against Your Training

A Riegel formula calculator can tell you what's physiologically possible. It can't tell you whether your endurance base supports it. A 10K race taps different energy systems than a half marathon, and a runner with strong speed but marginal endurance will consistently underperform their Riegel prediction at longer distances.

Cross-check your prediction against your long-run data. If your Riegel prediction suggests a 1:48 half marathon (roughly 8:15 per mile), you should be comfortable completing 10 to 12 mile training runs at 8:45 to 9:15 pace without excessive fatigue. If your long-run pace is significantly slower than that ratio suggests, your endurance isn't yet where it needs to be, and the prediction will prove optimistic.

The Long-Run Sanity Check

A reliable rule: your easy long-run pace should fall between 60 and 90 seconds per mile slower than your Riegel-predicted half marathon race pace. If the gap is larger than 90 seconds, your speed is outpacing your endurance—the prediction will be too aggressive. If the gap is smaller than 60 seconds, you may be running your long runs too hard, and the prediction could actually be conservative.

Run the Calculator Again After Your Tune-Up Race

Many half marathon training plans include a tune-up race 2 to 3 weeks before the goal event—often a 10K or 15K. This is your final, most accurate data point. Run it hard. Then immediately plug that result into the Riegel formula calculator.

This late-stage prediction accounts for the fitness you've built during the entire training block. If the new prediction is faster than your earlier one, you've improved—adjust your pacing tiers accordingly. If it's slower, you've got critical information: either your training hasn't worked as planned, or you're carrying fatigue that needs another week of taper to resolve.

Either way, you're making decisions based on current data, not hope. That's what the Riegel formula calculator is for—not promising you a finish time, but giving you the most honest estimate available so you can race intelligently.