Riegel Formula Calculator: 3 Steps 10K Marathon Prediction

87% Accuracy From One Number: What Riegel Actually Built

In 2018, a dataset of 8.7 million race results was run through Peter Riegel's 1985 endurance formula. The result? Marathon finish times were predicted within 3.1% accuracy for 82% of sub-3:30 runners—using nothing but a 10K time and a single exponent. No heart rate data. No VO2max. No training logs. Just one equation: T2 = T1 × (D2/D1)^1.06.

If you're sitting on a 10K finish time and trying to engineer a realistic marathon target, the Riegel formula calculator is the most efficient tool to get there. But the tool is only as good as the inputs you feed it and the context you apply to the output. Let's walk through this as a build—five steps, each anchored to a specific number, so you can move from raw 10K data to a defensible marathon prediction.

Step 1 — Lock In Your 10K Anchor Time (T1)

The 0.5% Rule for Selecting a Valid Input

Your T1 is the seed value for the entire calculation. Garbage in, garbage out. The Riegel formula assumes T1 represents a maximal, recent, race-effort performance—not a tempo run, not a training time trial on a treadmill at 1% incline, and definitely not a 10K split from a half marathon where you negative-split by two minutes.

Here's the filter I use when validating a runner's input:

• Recency: The 10K must be from the last 90 days. Aerobic capacity drifts by approximately 0.5% per week after peak fitness. A 10K from four months ago will underpredict your marathon by roughly 2%.
• Effort: The race should reflect a true maximal effort. If you ran a 10K as a tune-up and finished feeling like you had another mile in you, subtract 90–120 seconds before inputting.
• Course profile: A net-downhill 10K will inflate your prediction. A trail 10K at 900m elevation will deflate it. Aim for a road 10K with elevation gain under 50 meters.

Let's anchor the rest of this walkthrough to a concrete example. Suppose your validated 10K finish time is 52:30. That is 3,150 seconds. Write that number down—every subsequent step branches from it.

Step 2 — Set the Distance Ratio (D2/D1 = 4.2195)

Why 4.2195 and Not 4.22

The Riegel formula divides your target distance (D2) by your known distance (D1). For a marathon prediction from a 10K:

D2/D1 = 42.195 km / 10.000 km = 4.2195

That fifth decimal place matters. Rounding to 4.22 introduces a 0.06% error—small in isolation, but it compounds across the exponentiation step and the final time conversion. Over a 3:52 marathon prediction, that rounding error costs you roughly 14 seconds. When you're trying to determine whether 3:52:00 or 3:52:15 is your pacing target, precision is the difference between hitting the wall at mile 22 and cruising through it.

The Riegel formula calculator handles this ratio internally—you input "10K" and "marathon" and the tool computes 4.2195 behind the scenes. But understanding the ratio gives you the ability to sanity-check the output. If a calculator returns a marathon prediction that implies a ratio of 4.15 or 4.30, something is wrong with the engine.

Step 3 — Apply the 1.06 Exponent

The Number That Models Human Fatigue

This is the heart of Riegel's contribution. A simple linear extrapolation (T2 = T1 × 4.2195) would predict our example runner's marathon as 13,291 seconds (3:41:31). That is aggressively optimistic. Humans slow down as distance increases—glycogen depletes, muscle fibers fatigue, thermoregulation costs rise.

Riegel's exponent of 1.06 models that slowdown. It applies a nonlinear penalty to the distance ratio:

4.2195^1.06 = 4.4289

That delta—moving from 4.2195 to 4.4289—represents a 4.95% fatigue penalty applied to the linear prediction. This is the formula's way of saying: "You cannot sustain your 10K pace for 4.22 times the distance. You will slow down by approximately 5%."

For context, the exponent varies across distance ranges in more advanced models. Some researchers have found that 1.07–1.08 fits marathon data better for recreational runners (slower than 4:00), while 1.05–1.06 fits better for elite sub-2:30 performers. The standard Riegel formula calculator uses 1.06 as a universal constant—a reasonable middle ground, but not infallible.

Step 4 — Multiply and Convert to Marathon Time

From 3,150 Seconds to 3:52:31

Now we execute the full equation:

T2 = 3,150 × 4.4289 = 13,951 seconds

Convert that to hours, minutes, seconds:

• 13,951 ÷ 3,600 = 3.8753 hours
• 0.8753 × 60 = 52.52 minutes
• 0.52 × 60 = 31 seconds

Marathon prediction: 3:52:31

That is the raw Riegel output for a 52:30 10K runner. The calculator performs this chain of operations instantly, but seeing the arithmetic laid out helps you understand what the tool is actually doing. It also helps you catch errors—if a calculator returns 3:41 or 4:05 for this input, you know the exponent or ratio is misconfigured.

Translating Prediction to Pacing

A 3:52:31 marathon requires an average pace of 8:53 per mile (5:31 per kilometer). That pace assumes even splitting, which is statistically rare. Most marathoners run a positive split of 2–4%—meaning the second half is 5–12 minutes slower than the first. If you're building a race plan from the Riegel output, target:

• First half: 1:54:00 (8:43/mile)
• Second half: 1:58:31 (9:03/mile)

Step 5 — Apply the ±3.5% Confidence Window

Where the Formula Breaks and How to Compensate

The Riegel formula is a mathematical model, not a crystal ball. In validation studies, the formula's standard error for marathon prediction from a 10K input sits at approximately ±3.5%. For our 3:52:31 prediction, that creates a confidence window of:

3:44:24 to 4:00:38

That is a 16-minute spread. Where you land within that window depends on variables the formula cannot see:

• Weekly mileage: Runners logging 40+ mpw tend to outperform the prediction. Runners under 25 mpw tend to underperform by 4–6%.
• Long run history: If your longest run in the last 8 weeks is 16 miles, expect to land in the slower half of the window. If you've completed two 20-milers, the faster half is realistic.
• Course and conditions: A flat marathon at 50°F favors the fast end. Boston on a warm day shifts you toward the slow end regardless of fitness.
• 10K-to-marathon specificity gap: A runner with a strong 10K PR but limited marathon experience will almost always underperform the Riegel prediction. The formula assumes your endurance is proportional to your speed—it often is not.

My recommendation: treat the Riegel output as your ceiling—the best-case scenario if every variable breaks in your favor. Build your pacing plan around a target 2% slower than the raw prediction. For our example runner, that means planning for 3:57:00 and treating anything faster as a bonus.

Final Calibration: When to Trust the Number and When to Override It

The Riegel formula calculator is a starting point, not a finish line. It excels when your 10K is recent, your training volume is consistent, and your target marathon is on a comparable course. It degrades when any of those conditions break.

Use the five-step process above every time you input a new 10K time. Validate T1. Confirm the 4.2195 ratio. Respect the 1.06 exponent. Execute the math. Then widen the output into a confidence window and position yourself conservatively within it. That is how you turn a single race time into a marathon prediction you can actually race against.