The Multiply-by-Four Trap in Marathon Prediction

The "Just Multiply by Four" Trap

Most first-time marathoners do something remarkably predictable. They run a 10K, glance at their finish time, and mentally multiply it by four — maybe four and a half if they're feeling cautious. A 50-minute 10K becomes a "sub-3:30 marathon, easy." A 45-minute 10K becomes "I'm definitely breaking 3:15."

Then race day arrives. Mile 20 arrives with it. And the math falls apart.

The problem isn't motivation or training. The problem is that distance and fatigue don't scale linearly. Doubling the distance doesn't double the time — it multiplies it by something slightly more than two, and that "slightly more" compounds dramatically as you move from 10 kilometers to 42.2. This is exactly why a Riegel formula calculator exists, and why using one before you lock in your marathon training paces can save you from a painful, bonk-filled race day.

Why Your 10K Pace Won't Hold for 26.2 Miles

Think of it like carrying a backpack up a hill. The first mile feels fine. The second mile, the pack weighs the same, but your legs remember the first mile. By mile five, the pack hasn't changed — but you have.

Your body metabolizes energy differently over different durations. A 10K race primarily challenges your aerobic capacity and lactate threshold. You're running hard, but you're done in under an hour. A marathon, by contrast, chews through glycogen stores, tests muscular endurance, and introduces a fatigue variable that simply doesn't exist at shorter distances.

This is why raw multiplication fails. You need a model that accounts for the fact that humans slow down as distance increases — and not by a constant amount, but by an accelerating one.

What the Riegel Formula Actually Does

Peter Riegel, an engineer and runner, published a formula in 1985 that has become one of the most widely used race time predictors in the running world. The formula is elegantly simple:

T2 = T1 × (D2 / D1)^1.06

Where: - T1 is your known race time (say, your 10K result) - D1 is that race distance (10 kilometers) - D2 is your target distance (the marathon, 42.195 kilometers) - T2 is your predicted finish time - 1.06 is the fatigue exponent — the number that captures how much you slow down as distance grows

That exponent is the secret ingredient. If it were 1.0, the formula would be simple multiplication. At 1.06, it bakes in a realistic — if slightly optimistic — estimate of how fatigue compounds over longer efforts.

Step-by-Step: Using the Riegel Formula Calculator for Marathon Prediction

Let's walk through this as a practical tutorial. You've run a 10K. You want to know what marathon finish time to train toward. Here's how to get there.

Step 1: Establish Your Baseline 10K Time

Use a recent race — ideally within the last 8 to 12 weeks — run on a flat, accurately measured course under reasonable conditions. A parkrun time on a hilly trail in July heat won't give you a clean baseline. A chip-timed 10K road race in moderate weather will.

Write down your finish time in minutes. If you ran 52:15, convert that to 52.25 minutes (15 seconds = 0.25 minutes). Decimal format makes the math cleaner, though most online calculators will accept standard time formats and do this conversion for you.

Step 2: Enter Your Time Into the Riegel Formula Calculator

Most running calculator sites will have a dedicated marathon time prediction tool. You'll typically see two input fields: one for your known race distance, and one for your known finish time. Select "10K" (or enter 10 kilometers), type in your time, and select "Marathon" as your target distance.

The calculator applies the Riegel formula behind the scenes. You don't need to do any manual math — but understanding what it's doing helps you interpret the result intelligently.

Step 3: Read the Prediction — Then Contextualize It

Let's say you ran a 50:00 10K. Here's what the calculator does:

- D2 / D1 = 42.195 / 10 = 4.2195 - 4.2195 raised to the 1.06 power = approximately 4.60 - T2 = 50 × 4.60 = 230 minutes - 230 minutes = 3 hours, 50 minutes

So the Riegel formula predicts a marathon finish time of roughly 3:50:00 based on a 50-minute 10K.

That's a useful number. But it's not a guarantee. It's a starting point — the ceiling of what's physiologically possible if your endurance base, nutrition, and race-day execution all align with your current speed.

Step 4: Stress-Test the Prediction Against Your Training

This is the step most runners skip, and it's the one that matters most.

The Riegel formula assumes you're equally well-trained for both distances. But most runners who run a 10K are not equally trained for a marathon. They might have the speed for a 50-minute 10K but lack the 50+ mile weeks needed to sustain that fitness over 26.2 miles.

Ask yourself: - Can you currently run 18 to 20 miles at a pace within 60 to 90 seconds per mile of your 10K pace? - Are your long runs consistently in the 14 to 20 mile range? - Have you done any marathon-pace work within long runs?

If the answer to any of these is no, your real marathon time will likely be slower than the Riegel prediction. A common adjustment: add 5 to 15 minutes to the predicted time if your mileage base is under 40 miles per week.

Step 5: Convert the Prediction Into Training Paces

Once you have a realistic marathon goal time, work backward to set your training paces. If your adjusted target is 4:00:00 (9:09 per mile), then: - Easy runs: 10:30 to 11:30 per mile (roughly 60 to 90 seconds slower than marathon pace) - Marathon pace workouts: 9:09 per mile - Long run pace: 10:00 to 11:00 per mile - Tempo runs: 8:30 to 8:45 per mile

These paces become the scaffolding for your entire training block. The Riegel prediction gave you the target. Now your training plan fills in the path to reach it.

When the Riegel Formula Overpredicts (and What to Do About It)

The Riegel formula has a known tendency to be optimistic for marathon predictions, especially for recreational runners. The 1.06 exponent was derived partly from elite performance data, and elites have a few advantages that most of us don't: massive aerobic bases, years of accumulated mileage, and the biomechanical efficiency to maintain pace deep into a race.

For runners completing their first marathon, or those running under 35 miles per week, a slightly modified exponent — around 1.07 or 1.08 — often produces a more realistic prediction. Some calculators let you adjust this. If yours doesn't, take the standard Riegel output and add 5 to 10 minutes as a buffer.

On the flip side, if you're a high-mileage runner (50+ miles per week) with multiple marathons under your belt, the standard 1.06 exponent may be spot-on or even slightly conservative. Experienced marathoners with strong endurance relative to their raw speed often outperform the Riegel prediction.

The Bottom Line: A Tool, Not a Crystal Ball

A Riegel formula calculator is one of the most useful tools in a marathoner's planning toolkit. It takes a known data point — your 10K time — and translates it into a physiologically grounded marathon prediction that accounts for the nonlinear relationship between distance and fatigue.

But it's a model, not a prophecy. Its accuracy depends entirely on how well your training matches the assumptions baked into the formula. Use it to set an initial target. Then let your long runs, your tempo sessions, and your cumulative fatigue tell you whether that target needs adjusting.

The runners who cross the finish line smiling aren't the ones with the most optimistic predictions. They're the ones who used the prediction as a starting point — and then did the work to earn it.