Skip to content
Conversion

Run Conversion Calculator

Run Conversion Calculator

Enter a recent race time and predict your finish times at other distances with the Riegel formula.

Predictions assume similar fitness, weather, and course conditions. Treat them as targets for training, not guarantees.

You just ran a 5K in 25 minutes flat, and now you are eyeing a half marathon in three months. The question every runner asks at that moment is simple: what time should I aim for? Guessing too ambitiously leads to a painful blow-up at mile ten; guessing too conservatively leaves fitness on the table. What you need is a principled way to translate a performance at one distance into an equivalent performance at another.

That is what the Run Conversion Calculator does. Enter any recent race time — a mile, a 5K, a 10K, a half marathon, or a marathon — and it predicts your equivalent finish times at all the other distances using the Riegel formula, the most widely trusted race-prediction equation in running. Alongside each predicted time it shows the required pace per mile and per kilometer, so you can take the numbers straight to your training plan and your race-day pacing strategy.

Coaches have used versions of this math for decades to set goal times, design workouts, and decide whether a runner is ready to move up in distance. Now you can do the same in seconds: type in the time, press Calculate, and get a full table of equivalent performances with paces included.

What This Calculator Does

The Run Conversion Calculator takes one known performance and converts it into predicted performances across five standard race distances: 1 mile, 5K, 10K, half marathon, and marathon. The engine is the Riegel formula, published by engineer and runner Peter Riegel in 1977 after he analyzed world records across distances and found a remarkably consistent relationship between race distance and race time.

For every distance other than your input, the calculator outputs a predicted finish time plus the average pace per mile and per kilometer needed to achieve it. It also restates your current pace, so you can compare at a glance. Everything is computed from your single input time — no extra data entry, no complicated setup.

How To Use The Calculator

Choose the distance of your known race from the dropdown, then enter your finish time using the hours, minutes, and seconds boxes. Use a recent race run in decent conditions — a time from two years ago or a race run in extreme heat will give misleading predictions. Press Calculate and the results appear instantly: your input time restated, the Riegel formula used, and a table of predicted times with paces for the other four distances.

Read the table as a set of equivalent performances, not promises. If your 5K predicts a 3:59 marathon, that is the marathon your current fitness is capable of with proper endurance training — not a time you can run tomorrow without the long runs to back it up. Use the pace columns to set training paces: tempo runs, for example, are often run near your predicted 10K pace. Press Reset to try a different input time or distance.

The Riegel Formula Explained

The formula is beautifully simple: T2 = T1 × (D2 ÷ D1)^1.06, where T1 is your known time, D1 is the known distance, D2 is the target distance, and T2 is the predicted time. The exponent 1.06 is the key insight — it is slightly more than 1, which captures the fact that pace slows as distance grows. If the exponent were exactly 1, doubling the distance would exactly double the time; the extra 0.06 accounts for fatigue.

Why 1.06? Riegel found it by fitting the curve to world-record performances, and decades of race data have confirmed it holds up remarkably well for trained runners. Some coaches use slightly different exponents for beginners (up to 1.08, since less-trained runners slow down more) or elites (closer to 1.04), but 1.06 remains the standard all-purpose value — and it is the one this calculator uses.

The calculator applies the formula four times, once per target distance, using exact metric distances: 1 mile = 1,609.344 m, 5K = 5,000 m, 10K = 10,000 m, half marathon = 21,097.5 m, marathon = 42,195 m. Each predicted time is rounded to the nearest second, and paces are computed by dividing the predicted time by the distance in miles or kilometers.

Worked Example 1: From a 25-Minute 5K

Take a runner with a 25:00 5K — that is 1,500 seconds over 5,000 meters. Here is the exact arithmetic the calculator performs for each prediction:

Marathon: distance ratio = 42,195 ÷ 5,000 = 8.4390. Raise to 1.06: 8.4390^1.06 ≈ 9.5911. Multiply: 1,500 × 9.5911 = 14,386.7 seconds, rounded to 14,387 s = 3:59:47. Half marathon: ratio = 21,097.5 ÷ 5,000 = 4.2195; 4.2195^1.06 ≈ 4.6002; 1,500 × 4.6002 = 6,900.3 s = 1:55:00. 10K: ratio = 2.0000; 2.0000^1.06 ≈ 2.0849; 1,500 × 2.0849 = 3,127.4 s = 52:07. 1 mile: ratio = 1,609.344 ÷ 5,000 = 0.3219; 0.3219^1.06 ≈ 0.3007; 1,500 × 0.3007 = 451.1 s = 7:31.

The paces fall out naturally: the marathon prediction needs 14,387 ÷ 26.2188 miles = 9:09 per mile (5:41 per km), while the miler’s 7:31 needs 7:31 per mile (4:40 per km). Notice the pattern the 1.06 exponent creates — pace per mile gets slower as the distance grows, exactly as real racing feels.

Worked Example 2: From a 50-Minute 10K

Now a faster runner with a 50:00 10K (3,000 seconds). Marathon: ratio = 42,195 ÷ 10,000 = 4.2195; 4.2195^1.06 ≈ 4.6002; 3,000 × 4.6002 = 13,800.6 s = 3:50:01. Half marathon: ratio = 2.10975; 2.10975^1.06 ≈ 2.2080; 3,000 × 2.2080 = 6,619 s = 1:50:19. 5K: ratio = 0.5; 0.5^1.06 ≈ 0.4796; 3,000 × 0.4796 = 1,439 s = 23:59. 1 mile: ratio = 0.1609; 0.1609^1.06 ≈ 0.1439; 3,000 × 0.1439 = 433 s = 7:13.

This runner’s equivalent marathon is 3:50:01 — breaking 3:50 is a realistic stretch goal with a full training cycle. The 5K prediction of 23:59 shows the same fitness from the speed side. Comparing the two examples, you can see the formula is symmetric: it converts up and down in distance with equal ease.

Understanding Your Results

The headline restates your input time so you can confirm it was entered correctly. The table is the heart of the output: each row gives a distance, the predicted finish time, and the per-mile and per-kilometer paces that produce it. Use the times as goal-setting anchors and the paces as training tools — for instance, many coaches prescribe tempo runs at roughly your predicted 10K pace and long runs 60–90 seconds per mile slower than your predicted marathon pace.

The closing line shows your current pace, which is useful context: if your predicted marathon pace is 9:09 per mile but your easy runs are at 10:30, the gap tells you how much specific endurance work the goal requires. And remember the fundamental assumption: predictions describe what your current fitness is worth at each distance, assuming you train specifically for it. A 5K specialist cannot run their predicted marathon time without marathon training, no matter what the formula says.

Common Mistakes To Avoid

The most common mistake is feeding the calculator a stale or unrepresentative time. A personal best from three years ago reflects old fitness; a race run in 90-degree heat reflects bad conditions. Use a recent, all-out effort in reasonable weather. Second, many runners treat predictions as guarantees and set aggressive goals for a distance they have never trained for — the classic error is jumping from a 5K straight to a marathon prediction without the months of long runs that make it real.

Third, course differences matter: a hilly, trail, or high-altitude race will not match a flat road prediction. Fourth, beginners often find predictions slightly optimistic, because the 1.06 exponent was calibrated on trained runners — if you are new, add a few percent as a buffer. Finally, do not forget that pacing strategy affects outcomes: the formula assumes even pacing, so a race started too fast will underperform the prediction regardless of fitness.

Frequently Asked Questions

1. What is the Riegel formula?

It is the equation T2 = T1 × (D2 ÷ D1)^1.06, developed by Peter Riegel in 1977, which predicts race time at one distance from a known time at another. The 1.06 exponent captures how pace slows as distance increases.

2. How accurate are Riegel predictions?

Very good for trained runners on similar courses — typically within a few percent. Accuracy drops for beginners, extreme weather, hilly courses, or when jumping to a distance you have not trained for.

3. Can I predict a marathon time from a 5K?

Yes, and this calculator does exactly that — a 25:00 5K predicts a 3:59:47 marathon. But the prediction assumes you complete proper marathon training; the 5K fitness alone is not enough without the long runs.

4. Can I work backwards from a goal time?

Absolutely. Enter your goal as if it were a known time — for example, enter a 4:00:00 marathon to see what 5K, 10K, and half marathon times correspond to that fitness level, then train to hit those shorter benchmarks first.

5. Why does pace slow down at longer distances?

Energy systems and fatigue. Short races run mostly on readily available energy, while longer races depend on aerobic endurance and fuel management. The 1.06 exponent in the formula is the mathematical expression of that slowdown.

6. What distances does this calculator cover?

Five standard road-race distances: 1 mile, 5K, 10K, half marathon, and marathon. Enter a time at any one of them and get predictions for the other four.

7. Should beginners use a different exponent?

Some coaches suggest 1.07–1.08 for beginners, who tend to slow down more at longer distances. This calculator uses the standard 1.06; new runners should treat predictions as slightly optimistic targets.

8. How do I use the predicted paces in training?

Common practice: tempo runs near your predicted 10K pace, interval sessions near your predicted 5K pace, and long runs 60–90 seconds per mile slower than your predicted marathon pace.

9. Does the calculator account for hills or altitude?

No. Predictions assume flat road courses at low altitude in fair weather. Hilly, trail, or high-altitude races will be slower — adjust your goal accordingly.

10. Why is my predicted time slower than my personal best?

Because the input reflects your current fitness. If your PB is old or was set in perfect conditions, the calculator is telling you what you are worth right now, not what you once achieved. That is useful information, not an insult.

11. What is a good half marathon time for a 25-minute 5K runner?

According to the Riegel formula, 1:55:00 — which requires averaging 8:46 per mile (5:27 per km). Our worked example walks through the exact math.

12. Can predictions help with race-day pacing?

Yes — that is one of their best uses. Divide the predicted time into even splits (the pace columns do this for you) and run the first half slightly conservatively to avoid blowing up late.

13. How often should I re-run the calculation?

After every meaningful race or time trial. As your fitness improves, fresh inputs give fresh predictions, and watching the predicted times drop is one of the most motivating measures of progress.

14. Does the formula work for ultramarathons?

Less reliably. Beyond the marathon, factors like nutrition, terrain, and walking breaks dominate, and the 1.06 relationship breaks down. This calculator covers up to the marathon for that reason.

15. Is the Riegel formula better than other prediction methods?

It remains the most validated simple method, matching or beating more complex models in studies of real race data. Its strength is doing a lot with a single input — one recent race time.

Final Thoughts

Every runner has wondered what their fitness is really worth at a new distance, and guessing is a poor substitute for math that has held up since 1977. The Run Conversion Calculator turns one honest race time into a full set of equivalent performances — goal times to chase, paces to train at, and splits to race by. Enter your latest result, study the table, pick the target that excites you, and then do the training that makes the prediction come true.