Riegel Formula: Stop Guessing Marathon Time 10K

The Mistake That's Sabotaging Your Marathon Goal

You ran a 10k last weekend. You felt strong. The clock said 50:00 flat. So you pull out your phone, do some quick math, and tell your running buddy: "I'm in sub-3:50 shape for the marathon."

Here's the problem. You multiplied 50 minutes by 4.7. That's it. That's the entire calculation. And that linear shortcut is exactly why so many recreational runners toe the start line of a marathon convinced they're going to crush a time they have no realistic shot at hitting.

The human body does not scale linearly with distance. A 10k is not a marathon divided by 4.7. Fatigue compounds. Glycogen depletes. Muscle fibers that fired happily at kilometer 6 start refusing to fire at kilometer 36. This is why a Riegel formula race prediction calculator exists in the first place — to model that nonlinear decay instead of pretending it doesn't happen.

Let's walk through how to actually use one, the right way, starting from that 50:00 10k you just ran.

Why Your Old Method Fails

The "Multiply And Hope" Approach

Most self-coached runners do one of three things when predicting a marathon from a 10k:

• Multiply 10k time by 4.7 (the naive linear method)
• Multiply by 5, "to be safe" — which is still linear, just pessimistic
• Look at their 10k pace per mile, slow it down by 30 seconds, and multiply by 26.2

All three share the same flaw. They assume the cost of running an additional mile stays constant as the race gets longer. It doesn't. The 20th mile of a marathon costs you far more — physiologically and mechanically — than the 5th mile did.

Peter Riegel, an engineer and runner, figured this out back in the 1970s. He studied race times across distances and found that performance doesn't scale in a straight line. It scales along a curve. That curve has a power exponent of roughly 1.06. Not 1.0 (perfectly linear), not 2.0 (quadratic). Just a gentle bend upward that captures how we slow down as distance increases.

Step 1: Get A Real 10k Number, Not A Vibe

Before you touch any calculator, you need an honest input. The Riegel formula is garbage-in, garbage-out. Feed it a 10k split from a tempo run where you stopped at a water fountain and chatted with a friend, and it will spit out a marathon prediction that means nothing.

Use a 10k that meets these criteria:

• Race effort, not training effort — you should have been genuinely spent at the finish
• Run within the last 6 to 8 weeks (fitness drifts, and old fitness lies)
• On terrain similar to your goal marathon (a trail 10k does not predict a road marathon well)
• In conditions that weren't catastrophic (a 90°F hilly 10k will underpredict your potential)

For our example, let's say you ran a certified road 10k three weeks ago in 50:00. Cool, flat morning, well-rested, raced hard. That's a solid input.

Step 2: Understand What The Calculator Is Actually Doing

The Riegel formula looks like this:

T2 = T1 × (D2 / D1)^1.06

That probably looks like alphabet soup if math wasn't your favorite subject. So here's the plain-English version using a kitchen analogy.

Imagine you're doubling a recipe. If the recipe scaled linearly, doubling a recipe that takes 30 minutes would always take exactly 60 minutes. But anyone who has cooked for 20 people knows that doubling a recipe does not double the time — there's extra chopping, the pan gets crowded, the oven takes longer to recover. The time creeps up slightly more than you'd expect.

That "creep" is what the 1.06 exponent captures. It's small. But over the jump from 10k to 26.2 miles, that small creep adds up to a meaningful difference.

Here's what the calculator does behind the scenes with your 50:00 10k:

• T1 = 50 minutes (your 10k time)
• D1 = 6.2 miles (10k distance)
• D2 = 26.2 miles (marathon distance)
• It divides 26.2 by 6.2, getting roughly 4.23
• It raises 4.23 to the 1.06 power, getting roughly 4.60
• It multiplies 50 by 4.60

Result: 230 minutes, or 3 hours 50 minutes 15 seconds.

Notice that's about 15 seconds slower than the naive 4.7 multiplier would have given you (which would predict 3:50:00 flat). On a single prediction that gap looks tiny. But it widens dramatically as your 10k time drops. A 40:00 10k predicts 3:04:08 with Riegel — over a minute slower than the 3:02:48 the linear method would hand you. That minute matters when you're chasing a Boston qualifier.

Step 3: Plug It Into The Calculator Properly

Using a Riegel formula race prediction calculator is straightforward, but there are a few fields where beginners trip up.

Input your recent race distance correctly

Most calculators let you pick from a dropdown: 5k, 10k, half marathon, marathon, custom. Select 10k. Do not select "10 miles" because you ran a 10-mile race and figure it's close enough. The exponent is distance-sensitive. Get the input distance right.

Enter your finish time, not your average pace

This is the single most common error. Runners memorize their pace — "I ran 8:03 per mile" — and type that into a field expecting total time. The calculator then interprets 8:03 as eight minutes three seconds total, and predicts you'll finish a marathon in under ten minutes. Always enter total finish time: hours, minutes, seconds.

Choose the marathon as your target distance

Some calculators let you predict multiple distances at once. Useful if you're curious, but for marathon planning specifically, make sure 26.2 miles (or 42.195k) is the selected output.

Read the prediction, then sit with it

The calculator will hand you a number. For our 50:00 10k runner, that number is 3:50:15. Do not immediately round it down to 3:45 because you "feel good about it." Do not round it up to 4:00 because you're nervous. Write it down. Move to step 4.

Step 4: Adjust For Reality The Calculator Can't See

Here's where most articles about the Riegel formula stop, and here's exactly where they fail you. The formula is a mathematical model. It assumes the runner who produced the input 10k is equally well-trained for the marathon. That is almost never true for recreational runners.

Think of the Riegel prediction as a ceiling, not a floor. It tells you what you could run if your marathon-specific training matched the quality of your 10k training. If your longest long run has been 14 miles, you are not hitting that ceiling.

Apply these reality checks before you commit to a goal time:

Check your weekly mileage

If you're running 25 miles per week, the Riegel prediction is optimistic. Runners hitting 40+ mpw typically come closer to the formula's output. Add a minute or two to the prediction if your volume is low.

Check your long run history

Have you run at least two runs of 18+ miles in this training block? If no, the prediction is a stretch goal, not a target. The marathon rewards endurance specificity that a 10k simply doesn't test.

Check the course and weather profile

A 10k run on a flat, 55°F morning predicts a marathon on a flat, 55°F morning. Boston? Net downhill but with Heartbreak Hill and often warm. Chicago? Flat but can be windy. Adjust accordingly.

For our example runner with the 3:50:15 prediction: if they're running 35 mpw, have done one 18-miler, and are targeting a hilly March marathon, a realistic adjusted goal lands closer to 3:55 to 4:00. The Riegel number is the north star. The adjusted number is the route you'll actually hike.

Step 5: Convert The Prediction Into Race-Day Pacing Bands

Once you've settled on a realistic goal time — let's say 3:55:00 for our runner — the final step is translating that into something useful during the race itself. A finish time is abstract. A pace band is concrete.

3:55:00 over 26.2 miles works out to roughly 8:57 per mile. That's your average. But smart marathon pacing isn't flat. A common strategy:

• Miles 1–3: 9:05 (ease in, let the crowd thin)
• Miles 4–20: 8:55 (steady working pace)
• Miles 21–26.2: whatever you have left

Write these splits on your wrist, tape them to your singlet, or load them into your watch. The Riegel prediction gave you the destination. The pace band gives you the turns.

The Bottom Line On Riegel Predictions

The Riegel formula is the best simple tool we have for translating a 10k into a marathon estimate. It's not a crystal ball. It's a well-engineered starting point that respects the nonlinear reality of human fatigue — something the multiply-by-4.7 crowd will never understand until they're walking mile 23 of a marathon they "should have" cruised through.

Use a real 10k. Enter the total time, not the pace. Trust the exponent. Then adjust downward for the gaps the formula can't see. Do that, and the number you carry to the start line will be one you can actually run.