Riegel Formula Calculator: Realistic 2026 Marathon Pace

Stop Trusting Your Marathon Prediction Blindly — Here's the Fix

Quick tip before we dive in: If your Riegel formula calculator says you'll run a 3:30 marathon based on a 21:45 5K, knock 8–12 minutes off that prediction before you trust it. The formula doesn't know you've never run 26.2 miles. You should.

That's the single biggest pain point I see among intermediate runners using a race prediction calculator. You plug in a recent 5K or 10K time, the tool spits out a marathon time that looks achievable, and you build your entire training and race-day pacing plan around it. Then mile 22 hits, your legs turn to cement, and you shuffle across the finish line 15 minutes slower than predicted — wondering what went wrong.

Here's the truth: the Riegel formula is a powerful starting point, not a finish line. Used correctly — with the right reference race, the right adjustments, and an honest assessment of your training — it's one of the most reliable marathon prediction tools available. Used naively, it sets you up for a painful, demoralizing race day.

Let's walk through exactly how to use it the right way, step by step.

Understand What the Riegel Formula Actually Calculates

Before you use any marathon time predictor, you need to understand the math underneath it. Peter Riegel, an engineer and runner, published a formula in 1985 that became the backbone of nearly every race prediction calculator on the internet:

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

Where:

• T₁ = your known finish time for a recent race
• D₁ = the distance of that recent race
• D₂ = the target race distance (26.2 miles for a marathon)
• T₂ = your predicted finish time
• 1.06 = the fatigue exponent, accounting for the fact that you slow down as distance increases

That exponent — 1.06 — is the heart of the formula. It assumes that as distance doubles, your pace slows by about 6%. That's a reasonable approximation for well-trained runners moving up from a 5K to a 10K, or a 10K to a half marathon. But here's the catch: the further you extrapolate, the more error creeps in. Predicting a marathon from a 5K is a 5.25x distance jump. That's a lot of extrapolation.

Pick the Right Reference Race

Use a Race From the Last 6–8 Weeks

The single most impactful thing you can do to improve your marathon prediction accuracy is choosing the right reference race. A 5K you ran four months ago in cool weather tells the calculator almost nothing useful about your current marathon fitness.

Ideally, you want a race that meets three criteria:

• Recent: Within the last 6–8 weeks, during your marathon build
• Long enough to matter: A half marathon is gold standard. A 10K is acceptable. A 5K is a last resort.
• Raced at full effort: Not a tempo run, not a training race where you held back. An all-out effort.

Why a Half Marathon Is Your Best Input

Let's look at a concrete example. Say you recently ran a half marathon in 1:42:30 (6,150 seconds). Here's how the Riegel formula predicts your marathon time:

T₂ = 6,150 × (26.2 / 13.1)^1.06
T₂ = 6,150 × (2.0)^1.06
T₂ = 6,150 × 2.0848
T₂ ≈ 12,821 seconds ≈ 3:33:41

Now compare that to predicting from a 5K of 21:45 (1,305 seconds):

T₂ = 1,305 × (26.2 / 3.1)^1.06
T₂ = 1,305 × (8.45)^1.06
T₂ = 1,305 × 9.63
T₂ ≈ 12,567 seconds ≈ 3:29:27

Same runner, different reference race, and the 5K-based prediction is over four minutes faster. Why? Because a 5K is run at roughly 95–97% of VO2 max pace, while a marathon is run at roughly 75–80% of VO2 max pace. The formula's 1.06 exponent doesn't fully capture that physiological shift over such a large distance gap. The half marathon, being run closer to marathon intensity, produces a more reliable extrapolation.

Adjust for the Marathon-Specific Fatigue Factor

Here's where most runners stop — and where they go wrong. The Riegel formula assumes you're equally well-trained for both distances. But almost nobody is. If you've been doing 40-mile weeks with long runs of 16–18 miles, you're more prepared for a half marathon than a full. The calculator doesn't know that.

Here's a practical adjustment framework I teach runners:

• If your reference race is a half marathon: Add 3–5 minutes to the Riegel prediction if your peak long run is under 18 miles. Add 1–3 minutes if your peak long run is 20+ miles.
• If your reference race is a 10K: Add 5–8 minutes to the prediction. The extrapolation gap is larger, and so is the error margin.
• If your reference race is a 5K: Add 8–12 minutes. Seriously. The 5K-to-marathon jump is enormous, and the formula will almost always give you a time that's too fast.

Using our half marathon example above: the raw Riegel prediction was 3:33:41. If your longest training run has been 17 miles, add 4 minutes. Your realistic marathon target is now approximately 3:37–3:38. That's the number you should pace for.

Factor in Course and Conditions

Course Elevation Changes Everything

A marathon time predictor assumes a flat, fast course. If your goal race has 800 feet of climbing, your prediction needs to come down. A rough guideline: add 1–2 minutes for every 500 feet of net elevation gain on the course. Boston, for example, has a net downhill profile but includes the Newton Hills — and the Riegel formula won't account for the cumulative fatigue of those climbs at mile 20+.

Weather Is the Great Equalizer

The calculator also assumes ideal conditions: 45–55°F, low humidity, minimal wind. For every 10°F above 55°F, expect your marathon time to slow by 1–3% depending on your heat acclimation. If race day is forecast to be 72°F and humid, take your adjusted prediction and add another 5–7 minutes. I've seen runners hit perfect training numbers, then watch their race fall apart in 68-degree sunshine because they paced for the calculator's output, not the conditions.

Use the Prediction to Build a Pacing Band, Not a Single Number

This is the technique that separates runners who nail their predictions from runners who don't. Instead of taking a single number from the Riegel formula calculator and chasing it, build a pacing band.

Here's how:

• Take your adjusted prediction (after fatigue and course adjustments). Let's say it's 3:38:00.
• Set your conservative goal at +3 minutes — so 3:41:00.
• Set your stretch goal at -2 minutes — so 3:36:00.
• Run the first 20 miles at conservative goal pace (8:24/mile in this example).
• If you feel strong at mile 20, accelerate toward your stretch goal.

This approach does two things. First, it prevents the most common marathon mistake: going out too fast because you're chasing a calculator number. Second, it gives you permission to negative split, which is how most marathon PRs are actually run.

Validate With Multiple Data Points

No single race prediction calculator should be your only source of truth. The Riegel formula is one model. Other models — like the Cameron formula, the VDOT system, or the race equivalence calculator — use slightly different exponents and assumptions. If you plug your half marathon time into three different calculators and they all land within a 2–3 minute window, you can be confident in that range. If they diverge significantly, that's a sign your reference race might have been an outlier — maybe it was unusually hilly, or you had a great day, or the course was short.

Here's a quick validation checklist:

• Run your reference time through at least two different prediction models
• Compare the predictions to your current training paces — does your easy run pace align with what the predictor suggests your marathon pace should be?
• Check your threshold pace: marathon pace should be roughly 15–20 seconds per mile slower than your lactate threshold pace
• Look at your recent long run finishes: could you have continued for another 8–10 miles at your predicted marathon pace?

If the numbers align across these checks, trust your prediction. If they don't, the calculator is probably too optimistic — and you should adjust down.

Re-Run the Calculator Mid-Training

Your fitness isn't static. A half marathon you ran 8 weeks ago doesn't reflect the adaptations from your last two months of marathon training. If possible, run a tune-up race — even a 10K or 15K — 3–4 weeks before your goal marathon. Plug that new time into the Riegel formula calculator and compare it to your earlier prediction.

If the new prediction is faster, great — but don't immediately chase the faster time. Use it to confirm that your fitness is trending in the right direction. If the new prediction is slower than the old one, that's valuable information too. It might mean your earlier race was an outlier, or that your training hasn't been as effective as you thought. Either way, you'd rather know now than at mile 23.

The Bottom Line on Accurate Marathon Prediction

The Riegel formula calculator is a tool, not an oracle. It gives you a mathematically derived starting point based on the physiological relationship between race distances. What it can't account for is your specific training history, your course, your weather, and your mental readiness on race day. That's your job.

The runners who get their marathon predictions right aren't the ones who find the most sophisticated calculator. They're the ones who understand the formula's limitations, choose the right reference race, apply honest adjustments, and pace conservatively. Do that, and you'll cross the finish line feeling like you raced to your potential — not like you were chasing a number that was never realistic.