From 10K Split to Marathon Time: Riegel Step by Step

The Linear Multiplication Trap

Most runners do this: they finish a 10K in 50 minutes, pull out their phone, and multiply by 4.2. The math gives them 210 minutes. They round it to a 3:30 marathon, pin that number to their fridge, train for sixteen weeks, and arrive at the starting line convinced they are about to break 3:30.

The result is almost always disappointing. They hit mile 20 feeling wrecked, shuffle through the final 10K, and cross the line in 3:48 wondering where the eighteen minutes went.

The problem is not fitness. The problem is arithmetic.

Why Straight-Line Math Fails at the Marathon Distance

Multiplying your 10K time by 4.2 assumes that running a marathon is the same as running a 10K four point two times in a row at identical speed. That assumption ignores a fundamental physiological reality: the longer you run, the slower you get. Fatigue accumulates non-linearly. Glycogen depletes. Muscle fibers fatigue. Your body does not scale in a straight line.

Peter Riegel understood this. In 1981, the engineer and runner published a formula that modeled how race times change as distances increase. The formula does not assume you maintain your 10K pace. It assumes you slow down in a predictable, measurable way.

That formula is the foundation of every serious race time predictor available today, including the Riegel formula calculator on this site.

The Riegel Formula: What It Actually Does

The Riegel formula is expressed as:

T2 = T1 × (D2 / D1)^1.06

Where T1 is your known finish time for a recent race, D1 is the distance of that race, D2 is the distance you want to predict, T2 is your predicted finish time, and 1.06 is the fatigue exponent.

The exponent is the critical piece. If it were 1.0, the formula would be pure linear scaling, which is the exact mistake most runners make. The 0.06 above 1.0 is what accounts for the additional fatigue of running farther. It is a small number that produces a large effect over marathon distance.

Step-by-Step: From 10K Split to Marathon Prediction

Let us walk through a complete worked example using a real set of numbers. Assume you recently ran a 10K in 50 minutes flat. Here is how to use the Riegel formula calculator to predict your marathon finish time from that 10K race pace.

Step 1: Record Your 10K Finish Time Accurately

Write down your official chip time, not your GPS watch time. Race courses are measured to certification standards. Your watch is not. For this example, the 10K finish time is 50:00.

Step 2: Convert to Seconds

The Riegel formula works most cleanly in a single unit. Seconds is the simplest. Convert 50 minutes:

50 minutes × 60 = 3,000 seconds

Your T1 value is 3,000.

Step 3: Establish Your Distance Ratio

A marathon is 42.195 kilometers. A 10K is 10 kilometers. The ratio is:

42.195 / 10 = 4.2195

Step 4: Apply the Riegel Exponent

Raise the distance ratio to the 1.06 power:

4.2195^1.06 = 4.602

This is the fatigue-adjusted multiplier. Notice it is higher than 4.2. That extra 0.4 is the formula accounting for the fact that you cannot sustain 10K race pace for a full marathon.

Step 5: Calculate Your Predicted Marathon Time in Seconds

Multiply your 10K time in seconds by the fatigue-adjusted multiplier:

3,000 × 4.602 = 13,806 seconds

Step 6: Convert Back to Hours and Minutes

Divide by 60 to get minutes:

13,806 / 60 = 230.1 minutes

Divide by 60 again to get hours:

230.1 / 60 = 3.835 hours

That is 3 hours and 0.835 × 60 = 50.1 minutes. Your Riegel-predicted marathon finish time is approximately 3:50:06.

Compare that to the 3:30 the linear multiplication gave you earlier. The twenty-minute difference is not pessimism. It is physiology modeled through mathematics.

When the Riegel Calculator Overpromises

The reason is that the Riegel formula was calibrated using a broad dataset that includes elite and highly trained runners. These athletes have spent years developing the aerobic infrastructure, mitochondrial density, and lactate threshold necessary to sustain a pace relatively close to their shorter race speeds over long distances. Most recreational runners have not. If you run 25 to 35 miles per week and complete a 10K at a hard effort, your body simply does not have the endurance base to carry a proportional fraction of that speed across 26.2 miles. The 1.06 exponent works beautifully for the runner it was modeled around. For everyone else, it tends to be slightly optimistic.

Factors That Skew the Riegel Prediction

Several variables can cause your actual marathon finish time to drift from what the calculator spits out. Understanding these factors will help you interpret the number intelligently rather than treating it as gospel.

Weekly Training Volume

If you are running fewer than 40 miles per week in the lead-up to your marathon, the Riegel prediction will almost certainly be too fast. Low-volume runners tend to experience a steeper fatigue curve than the formula assumes. If you are running 55 or more miles per week with consistent long runs of 18 to 22 miles, your body is better conditioned to hold a pace closer to the predicted time.

Course Profile and Elevation

The Riegel formula is distance-based. It does not know whether your marathon is run on a pancake-flat seaside course or a relentless hill course in the mountains. A net downhill course like Boston can produce a faster-than-predicted time for some runners, while a hilly course will slow you down. Always factor in the elevation profile when assessing whether your predicted time is realistic for your goal race.

Weather Conditions

Temperature and humidity have an outsized effect on marathon performance. Research consistently shows that optimal marathon performance occurs around 40 to 50 degrees Fahrenheit for most runners. For every 10 degrees above that, marathon times slow by a measurable margin. If you ran your 10K in cool conditions but your marathon falls on a warm day, expect to run slower than the Riegel prediction.

10K Effort Level

Was your 10K a true all-out race effort, or was it a tune-up run at 90 percent? The formula assumes you ran the reference race at maximum sustainable effort. If you held back, your predicted marathon time will be artificially slow. If you ran a 10K on a downhill course with a tailwind and adrenaline-fueled competition, your predicted marathon time will be artificially fast. Use a recent 10K that reflects your genuine current fitness, run on a reasonably fair course at a hard effort.

How to Adjust the Riegel Prediction for Real-World Use

Given that the formula tends to overpredict for recreational runners, a practical adjustment is to add a small buffer to the calculated time. For runners logging 40 to 50 miles per week, adding 5 to 10 minutes to the Riegel prediction is a reasonable starting point. For runners logging 25 to 40 miles per week, adding 10 to 20 minutes may be more appropriate. Elite and sub-elite runners with high mileage and strong aerobic bases can often run the Riegel prediction as-is or even beat it.

Another approach is to use the Riegel prediction as your upper-bound goal and set a more conservative target as your primary pacing strategy. If the calculator says 3:50, consider starting the marathon at 3:55 pace. If you feel strong at mile 18, you can negative-split the final 8 miles and still finish near your Riegel time. This strategy protects you against the catastrophic slowdown that turns a 3:50 attempt into a 4:10 finish.

Cross-Checking With Other Predictors

No single formula is perfect. The Riegel calculator is one tool among several. Cross-referencing your Riegel prediction with other race time predictors can give you a more robust estimate.

The Jack Daniels VDOT Method

Jack Daniels, the renowned exercise physiologist, developed a VDOT table that predicts race times across distances based on a single race result. The VDOT method tends to be slightly more conservative than Riegel for the marathon distance, which makes it a useful counterweight. If your Riegel prediction is 3:50 and your VDOT prediction is 3:55, splitting the difference at 3:52 or 3:53 is a sensible target.

The Yasso 800s Benchmark

Bart Yasso's famous workout involves running 10 repetitions of 800 meters at a pace that roughly corresponds to your marathon goal time in hours and minutes. If you want to run a 3:50 marathon, you would aim to run each 800 in 3 minutes and 50 seconds with equal recovery. Yasso 800s are not a precise predictor, but they provide a gut-check on whether your goal time is in the right ballpark. If you cannot complete the workout at the pace corresponding to your Riegel prediction, your body is telling you the prediction is too aggressive.

Half Marathon as a Bridge

If you have a half marathon time from the same training block, run it through the Riegel calculator as well. A half marathon is closer to marathon distance, so the prediction error is smaller. Comparing the 10K-based prediction and the half-marathon-based prediction gives you a range. If both land near 3:50, you can be more confident. If the half marathon predicts 3:55, weight that number more heavily because it is derived from a longer and more marathon-specific effort.

Turning Your Prediction Into a Race-Day Strategy

Once you have a realistic predicted finish time, the next step is converting it into a pacing plan. Divide your predicted total time by 26.2 to get your target minutes per mile, or by 42.195 for minutes per kilometer. For the 3:50:06 prediction, that works out to approximately 8:46 per mile or 5:27 per kilometer.

Do not run the first mile at goal pace. Run it five to ten seconds slower. The adrenaline of race morning makes goal pace feel effortless in the first mile, and almost every runner goes out too fast. Banking time early is a myth. The seconds you save in mile 1 will cost you minutes in mile 23. Start conservatively, settle into your predicted pace by mile 3, and hold it steady through mile 20. After mile 20, run by feel. If you have paced correctly, you will have the fuel left to hold pace or even accelerate.

The Bottom Line

The Riegel formula calculator is the best starting point for predicting your marathon finish time from a recent 10K. It is vastly superior to linear multiplication because it accounts for the non-linear nature of fatigue. But it is a model built on averages, and you are an individual. Your training volume, course conditions, weather, and effort level on race day all influence whether you run faster or slower than the number on the screen.

Use the calculator to establish a realistic performance ceiling. Adjust downward if your training volume is moderate. Cross-check with other predictors. Test the goal pace in your longest training runs. And on race day, run the first third with discipline, the middle third with patience, and the final third with whatever you have left. That is how you turn a mathematical prediction into a finish time you can be proud of.