Riegel Formula Calculator: Set Marathon Pace From 10K

Run a sub-42:00 10K? Your marathon ceiling is 3:11:37—here's how to actually hit it

Most runners plug their 10K time into a Riegel formula calculator, see a marathon prediction, and either chase it blindly or dismiss it as fantasy. The gap between those two reactions is where the real work happens. I've spent six seasons refining how to use Peter Riegel's endurance equation—not as a crystal ball, but as a pacing anchor that keeps me honest on race day. Here's the workflow I use, built from trial, error, and a lot of misjudged splits.

Know what the Riegel formula actually calculates

The Riegel formula is elegant in its simplicity:

T2 = T1 × (D2 / D1)^1.06

Where T1 is your known race time at distance D1, and T2 is the predicted time at distance D2. The exponent 1.06 represents the fatigue curve—the rate at which your pace decays as distance increases. A 10K at 42:00 minutes predicts a marathon of roughly 3:11:37. That's not a goal. That's a physiological ceiling based on your current aerobic capacity.

The critical distinction

The formula assumes you're equally trained for both distances. If you've been doing 30-mile weeks with speedwork but no long runs over 16 miles, your 10K reflects your speed, not your endurance. The prediction will be optimistic. I learned this the hard way: ran a 41:30 10K in April, predicted a 3:09 marathon, limped home in 3:24 in May. The calculator wasn't wrong. My training was incomplete.

Use your most recent 10K, not your PR

This is the single most common mistake I see. Runners input their lifetime 10K best—a race run three years ago under perfect conditions with tapered legs—and expect the marathon prediction to hold. It won't.

Use a 10K from the last 8–12 weeks, ideally run under similar conditions to your target marathon. If you're training through it without a full taper, add 60–90 seconds to your time before inputting it. A training-run 10K at 43:30 with tempo effort is a more honest input than a tapered 41:45 from six months ago.

Where to source your input time

• Race results from the last 3 months (gold standard)
• Time trial on a measured course with similar elevation profile
• Garmin/Strava-verified 10K split within a longer effort (least reliable but usable)

Build a training pace ladder from the prediction

Once you have your predicted marathon time, don't just file it away. Use it to construct your entire training pace spectrum. If the calculator says 3:11:37, that's 7:20 per mile. Here's how I translate that into weekly training:

This ladder keeps everything proportional. If your threshold pace feels impossibly fast relative to your predicted marathon pace, your 10K input was likely inflated. The paces should feel challenging but structurally connected.

Validate the prediction at 18–20 miles

A Riegel prediction is only as good as your longest validation effort. Three to four weeks before your goal marathon, run 18–20 miles with the final 8–10 at your predicted marathon pace. This is the moment of truth.

If the calculator predicted 7:20/mi and you're running 7:20 for miles 12–20 feeling controlled, the prediction is viable. If you're grinding to hold 7:35 by mile 17, you need to revise your race-day target upward by 5–10 seconds per mile. I've never run a marathon faster than my final long-run marathon-pace block suggested I could. The Riegel formula gives you the theoretical ceiling; the long run confirms whether you can reach it.

Reading the validation correctly

If you nail the pace block but feel wrecked for four days afterward, your endurance is there but your recovery capacity isn't. Add 3–5 seconds per mile to your race-day plan. If you nail it and feel ready to train again in 48 hours, you may have room to be slightly more aggressive. The prediction is a starting point, not a mandate.

Adjust for course and conditions

The Riegel formula is distance-agnostic. It doesn't know whether you're running Berlin or Boston. You have to layer reality on top of the math.

For a net downhill course like Boston, I subtract 90–120 seconds from the predicted time. For a hilly marathon like NYC, I add 3–5 minutes. For temperatures above 65°F at the start, add 1% to your predicted time for every 5° above 55°F. These adjustments aren't arbitrary—they come from comparing Riegel predictions against actual finishing times across dozens of races.

Use the prediction as a negative split anchor

The biggest tactical mistake I made for years was treating my Riegel-predicted time as an even-pace target. Marathon pacing isn't linear. The formula's 1.06 exponent exists because fatigue accumulates, but you can manage how it accumulates.

My current approach: run the first 5K 5–8 seconds per mile slower than predicted average pace. Run miles 4–20 at predicted pace. Then decide. If I'm feeling strong at mile 20, I have the aerobic capacity to negative split the final 10K. If I'm hanging on, I've banked nothing but I haven't dug a hole either. This strategy has put me within 2 minutes of my Riegel prediction on three consecutive marathons.

Re-run the calculator every 6 weeks

Your fitness isn't static. A 10K you ran in February tells you nothing useful about your May marathon if you've been training consistently. I re-run a 10K time trial or race every 6 weeks during a marathon build and input the new time into the Riegel calculator. The trajectory matters as much as the absolute number.

If my prediction improves from 3:14 to 3:10 to 3:08 across three inputs, I know the training is working and my marathon target is solidifying. If the prediction stalls or regresses, I need to examine whether I'm overtraining or under-recovering before I adjust the goal.

Respect the formula's limits

The Riegel formula works best for distances between 5K and the marathon, and for runners with relatively balanced speed and endurance profiles. If you're a former sprinter who has only been endurance training for a year, your 10K speed will overstate your marathon potential—the fatigue curve is steeper for you than the 1.06 exponent assumes. If you're a lifelong endurance athlete who struggles to break 50 minutes in the 10K but can run 7:30 pace forever, the formula may underestimate you.

Know which type of runner you are. The calculator is a tool, not an oracle. Use it to set boundaries on your expectations, to structure your training paces, and to check your ego at the door. Then go do the work.