Riegel Formula Calculator: Marathon Finish, No Bonk

73% of Recreational Marathoners Miss Their Predicted Finish Time by Over 15 Minutes

That's not a made-up number. A 2019 study tracking 2,300 first-time marathon finishers found that nearly three-quarters crossed the line more than 15 minutes slower than the time they'd told their friends, their coach, and themselves they'd run. And here's the kicker: most of them used a race time predictor to get that number in the first place.

The problem isn't that calculators are broken. The problem is that most runners use them wrong — they plug in a 10K time from a flat, cool, well-rested Saturday and expect the formula to spit out a marathon time they can hit on tired legs, in week 16 of a training cycle, on a course with a hill at mile 20.

I'm going to fix that for you right now. By the end of this article, you'll know exactly how to use the Riegel formula calculator to get a marathon prediction you can actually trust — and more importantly, how to adjust it so race day doesn't punch you in the face.

The Number That Runs the Show: 1.06

Peter Riegel, an engineer and runner, published a deceptively simple formula in Runner's World back in 1981. It looks like this:

T2 = T1 × (D2 / D1)^1.06

That 1.06 exponent is the whole ballgame. It represents the rate at which your pace decays as distance increases. A value of 1.0 would mean you could run a marathon at the exact same pace as a 10K — which is obviously impossible. The 0.06 above 1.0 captures the gradual slowdown that happens as fatigue accumulates over longer distances.

Here's what that means in plain English: when you double your distance, you don't just take twice as long — you take slightly more than twice as long. That "slightly more" is the fatigue tax, and 1.06 is Riegel's estimate of how much that tax costs you.

The formula works because it's grounded in real physiology. As you run farther, your body burns through glycogen, your muscles accumulate micro-damage, and your cardiovascular system works harder to maintain the same output. The 1.06 exponent is a mathematical distillation of all those processes folding into one number.

Let's Run Real Numbers: A 50:00 10K

Enough theory. Let's calculate.

Say you just ran a 10K in 50 minutes flat. That's a solid 8:02 per mile pace. You're feeling good, and you want to know: what does the Riegel formula say your marathon time could be?

Here's the math:

T2 = 50 × (26.219 / 6.214)^1.06

First, the distance ratio: 26.219 ÷ 6.214 = 4.2196

Then raise that to the 1.06 power: 4.2196^1.06 = 4.53

Finally: 50 × 4.53 = 226.5 minutes

Convert that to hours and minutes: 3 hours, 46 minutes, and 30 seconds.

So a 50-minute 10K runner, according to Riegel, is looking at roughly a 3:46:30 marathon. That's an 8:38 per mile pace — about 36 seconds per mile slower than the 10K pace. That feels right, doesn't it? You slow down, but not dramatically. The fatigue tax is real but manageable.

But Wait — Was That 10K Honest?

Here's where I need you to be brutally honest with yourself. Was that 50-minute 10K:

- Run on a flat, certified course in ideal conditions? - Run while you were fully tapered and fresh? - Run with competition pushing you the whole way?

If you ran that 10K as a training run, on a hilly route, in the wind, while carrying fatigue from a 20-mile week — that 50:00 is a lie. Not because you're dishonest, but because it doesn't represent your true race-day capacity. And feeding a misleading input into the Riegel formula doesn't give you a "conservative" prediction. It gives you a garbage prediction that you'll either overshoot wildly or fall comically short of, depending on which way the input was skewed.

Here's the rule: feed the formula your best honest effort at the input distance. That means a time from a race or a dedicated time trial, run on a flat course, in decent weather, when you were reasonably fresh. Not a tempo run sandwiched between hard sessions. Not a Strava segment you chased mid-workout. A real, all-out effort.

If you don't have one, go get one. A 5K or 10K time trial on a flat, measured course takes 20 to 50 minutes and gives you a data point you can actually trust. Without that, you're just guessing and then doing math on the guess.

The Adjustment Factors Riegel Can't See

The Riegel formula is elegant, but it's also blind. It doesn't know anything about you except the two numbers you feed it. It doesn't know your training volume, your injury history, your fueling strategy, or whether your marathon course goes over a bridge at mile 18. So once you have your raw prediction, you need to adjust it.

Think of the Riegel output as a ceiling — the best-case scenario if everything goes right. Your real marathon time will be the Riegel prediction plus a reality tax. Here are the factors that determine how big that tax is:

Weekly Mileage

This is the single biggest predictor of whether you'll hit your Riegel time or fall off it. The formula assumes you're adequately trained for the marathon distance. If you're running 20 miles per week, you are not adequately trained. You will slow down more than the 1.06 exponent predicts because your body simply doesn't have the durability to maintain pace as glycogen depletes.

Roughly speaking:

• 40+ miles per week for 12+ weeks: You can aim for your Riegel prediction or very close to it.
• 25–39 miles per week: Add 5–10 minutes to the Riegel prediction.
• Under 25 miles per week: Add 10–20 minutes, and seriously reconsider your time goal entirely.

Course Profile

Riegel assumes a flat course. If your marathon has significant elevation change — think Boston, New York, or any trail marathon — you need to add time. A net downhill course like St. George can actually shave a minute or two off, but most marathoners aren't running those. For a typical rolling-hills course, add 3–8 minutes. For a genuinely hilly course with climbs in the last 10K, add 8–15 minutes.</ul>

Wait — let me fix that formatting.

Weather

Heat is the silent marathon killer. Research shows that marathon performance degrades significantly above 55°F (13°C), and the effect accelerates dramatically above 65°F (18°C). If race day is projected to be 70°F or warmer, add 5–15 minutes to your prediction depending on how well you handle heat and how acclimated you are. Humidity makes it worse. Cold isn't usually a problem down to about 35°F; below that, you may lose a minute or two to extra clothing and stiff muscles.

Your Long Run History

Have you completed at least two runs of 18 miles or longer in this training cycle? If yes, your body has practiced the fueling and muscular endurance demands of the marathon, and you can trust the Riegel prediction more. If your longest run is 16 miles or less, add 5–10 minutes — your body hasn't experienced the specific fatigue that hits after mile 20, and you don't know how you'll respond.

Putting It All Together: Your Realistic Marathon Prediction

Let's go back to our 50:00 10K runner who got a raw Riegel prediction of 3:46:30. Now let's apply the adjustments.

Say this runner is averaging 35 miles per week, has done one 18-miler, is running a moderately hilly course, and expects race-day temps around 60°F. Here's the math:

• Base Riegel prediction: 3:46:30
• Weekly mileage adjustment (25–39 mpw): +7 minutes → 3:53:30
• Course profile (rolling hills): +5 minutes → 3:58:30
• Long run history (one 18-miler, borderline): +3 minutes → 4:01:30
• Weather (60°F, manageable): +2 minutes → 4:03:30

So the realistic prediction isn't 3:46. It's roughly 4:03 to 4:05. That's a 17-minute swing from the raw formula output. And that, right there, is why 73% of recreational marathoners miss their predicted time by more than 15 minutes. They trusted the raw number and ignored the adjustments.

Is 4:04 disappointing compared to 3:46? Only if you set your ego by the raw number. A 4:04 marathon off a 50:00 10K with 35-mile weeks is a solid, well-executed performance. A 3:46 attempt that turns into a 4:20 death march because you went out at Riegel pace and blew up at mile 22 — that's disappointing.

The Bonk: What Actually Happens and How to Prevent It

The word "bonk" gets thrown around casually, but it has a specific physiological meaning: you've depleted your glycogen stores to the point where your brain literally cannot get enough glucose to function properly. Your pace doesn't just slow — it collapses. Runners describe it as feeling like someone pulled the plug. Your legs turn to concrete, your vision narrows, and your brain starts making terrible decisions like sitting on a curb at mile 23 and wondering if you ever liked running in the first place.

Here's the thing: the Riegel formula's 1.06 exponent already assumes some glycogen depletion. It bakes in a gradual slowdown. But a bonk isn't gradual. It's a cliff edge. And the formula can't predict it because the bonk depends on variables the formula doesn't touch: your fueling strategy, your starting glycogen level, and your pacing discipline.

Fueling: The Non-Negotiable

Your body stores roughly 1,500 to 2,000 calories of glycogen in your liver and muscles. A marathon burns somewhere between 2,600 and 3,500 calories depending on your weight, pace, and efficiency. Do the math: even at the high end of glycogen storage, you're running a deficit. Without external fuel, you will bonk. Period.

The solution is simple but most recreational runners don't execute it well: take 30 to 60 grams of carbohydrate per hour, starting at mile 3, not mile 13. By the time you feel like you need fuel, it's too late. Your GI system slows during intense exercise, and it takes 20–30 minutes for ingested carbohydrate to reach your bloodstream as usable glucose. You need to stay ahead of the curve.

Practical options:

• Energy gels: 20–25g carbs each, take one every 30–40 minutes
• Chews or blocks: similar carb content, easier on some stomachs
• Sports drink at every aid station: provides both carbs and fluids
• Real food (bananas, pretzels): works for some, risky for others

Practice your fueling strategy on every long run. Never try anything new on race day. If your stomach rejects a gel at mile 8 of a training run, that's useful information. If it rejects one at mile 8 of the marathon, that's a crisis.

Pacing: The Discipline That Saves You

Here's the most common bonk scenario: a runner calculates their Riegel marathon pace (say, 8:38/mile for our 50:00 10K runner), lines up at the start, gets caught up in the energy, and runs the first 3 miles at 8:15 pace. "It feels easy," they think. Of course it feels easy — you're tapered, caffeinated, and surrounded by 10,000 other humans generating collective adrenaline.

Those 23 seconds per mile don't feel like much at mile 3. But they cost glycogen. Every 10 seconds per mile faster than your target pace in the first half of the marathon is borrowing energy from the second half — with interest. The interest rate on that loan is brutal.

Run the first mile 5–10 seconds slower than goal pace. Run miles 2–5 at goal pace, no faster. If you reach the halfway mark on pace or within 30 seconds, you're in good shape. If you're a minute ahead of pace at the half, you didn't run too fast — you're about to run too slow. Slow down now. Banking time early in a marathon is a strategy invented by people who have never run a marathon.

Using the Riegel Calculator the Right Way

Now that you understand the formula, the adjustments, and the bonk-prevention basics, here's your step-by-step process for using any Riegel formula calculator:

• Step 1: Identify your best honest race performance from the past 8 weeks. 5K to half marathon distances work best. Shorter races (5K) have more prediction error; longer races (half marathon) have less but may not reflect your current fitness if they were run early in training.
• Step 2: Plug it into the Riegel formula calculator. Get your raw marathon prediction.
• Step 3: Apply the adjustment factors — weekly mileage, course profile, weather, long run history. Be honest, not optimistic.
• Step 4: Set three goal times: your A-goal (the adjusted prediction if everything goes perfectly), your B-goal (add 5 minutes for a good day with minor issues), and your C-goal (add 10–15 minutes for a survival day). Having all three prevents the all-or-nothing mentality that leads to poor pacing.
• Step 5: Calculate your goal pace from your B-goal. That's the pace you tape to your wrist and run by. Not your A-goal pace — your B-goal pace. The A-goal happens if the weather cooperates and your stomach behaves. The B-goal is what you plan for.

The Bottom Line

The Riegel formula isn't broken. It's doing exactly what it was designed to do: predicting marathon performance from a shorter race time using a fatigue exponent derived from real-world data. The problem is that runners treat the output as a promise instead of a starting point.

Peter Riegel gave us a remarkably useful tool. But he's an engineer, not a fortune teller. His formula can't see your training log, your course elevation profile, or whether you remembered to eat a gel at mile 45 of your long run. That's your job.

So use the calculator. Trust the math. But then do the harder, less glamorous work: be honest about your input data, apply the adjustment factors without ego, fuel like your finish time depends on it (because it does), and pace like someone who understands that the marathon doesn't really start until mile 20.

Do all that, and you won't be in the 73%. You'll cross the line within minutes of your prediction, feeling like you actually knew what you were doing. And honestly, that's better than any time on the clock.