Running Equivalency Calculator
Enter a race time you have actually run and predict your equivalent time at any other distance with the Riegel formula.
You just ran a 25-minute 5K, and now you are wondering: what could I run for a marathon? Or you finished a marathon in four hours and want to know what 5K time that fitness is worth. These are not idle curiosities — they set training paces, race goals, and expectations for an entire season. And there is a genuine mathematical answer, discovered by engineer and runner Peter Riegel in the 1970s: race times across distances follow a predictable power law.
The Running Equivalency Calculator above applies Riegel’s formula to your real results. Enter a race distance and the time you actually ran, pick the distance you want to predict, and the calculator returns the equivalent time — with the full calculation shown step by step, your predicted pace, and a table of equivalent times for the classic distances from 5K to marathon.
What This Calculator Does
This calculator predicts race performances using the Riegel formula: T2 = T1 × (D2 ÷ D1)^1.06, where T1 is your known time, D1 is the distance you ran, D2 is the target distance, and 1.06 is the exponent Riegel fitted to world-record performances. The exponent being slightly above 1.0 captures a deep truth about endurance: pace fades as distance grows, so doubling the distance costs a little more than double the time.
You choose your known race from 5K, 10K, 10 miles, half marathon, marathon, or a custom distance in kilometers, enter your time as hours, minutes, and seconds, and choose the target distance the same way. The calculator shows the predicted clock time, the equivalent average pace per kilometer, the four numbered steps of the computation with your exact numbers, and an equivalence table converting your fitness into 5K, 10K, half-marathon, and marathon times with paces. A note explains the formula’s assumptions so the prediction is used as a target, not a promise.
How to Use the Calculator
Select the race you ran from the dropdown — or choose “Custom distance…” and type the exact distance in kilometers for a parkrun-variant, a track 3000m, or any other effort. Enter your finish time using the three boxes: hours, minutes, and seconds. A 25-minute 5K is 0 hours, 25 minutes, 0 seconds; a 4-hour marathon is 4, 0, 0.
Then select the distance you want a prediction for, again with a custom option if your goal race is an unusual distance. Press Calculate. The headline gives the equivalent time, the sub-line gives the pace per kilometer, the steps show the ratio, the exponent, and the multiplication, and the table lists all four classic distances. Use your most recent all-out race result as the input — a tempo run or a training time trial held back from full effort will under-predict what you can do.
The Riegel Formula, Explained
Peter Riegel, a research engineer and competitive runner, noticed that world records across distances fell on a straight line when plotted on logarithmic axes — which means they follow a power law: time grows as distance raised to a constant exponent. Fitting the records gave an exponent of about 1.06. In plain terms: if you double the distance, your time multiplies by 2^1.06 ≈ 2.085, not 2.0. That extra 4% is the endurance penalty — the pace you can hold inevitably softens as the distance stretches.
The formula needs only one anchor: a real performance. From T1 at D1, any D2 follows. The calculator computes the ratio D2 ÷ D1, raises it to 1.06, and multiplies by T1 in seconds, then converts back to hours, minutes, and seconds. Predicted pace is simply the predicted time divided by the target distance. Because the exponent was fitted to elite records, it describes well-trained runners best; recreational runners often fade a little more at long distances, making marathon predictions slightly optimistic — which the results note says plainly.
Worked Example: From a 25-Minute 5K to the Marathon
A runner has a recent 5K personal best of 25:00 and wants a marathon target. Step one: convert the known time to seconds — 25 × 60 = 1500 seconds for 5.0000 km. Step two: the distance ratio is 42.1950 ÷ 5.0000 = 8.4390. Step three: apply Riegel — T2 = 1500 × 8.4390^1.06 = 1500 × 9.5911 = 14387 seconds. Step four: convert back — 14387 seconds = 3:59:47.
The equivalent marathon pace is 5:41 per kilometer over 42.20 km. The calculator’s table fills in the rest of the picture from the same fitness: 10K in 52:07 (5:13/km), half marathon in 1:55:00 (5:27/km). Notice the pace decay the exponent produces — 5:00/km at 5K softening to 5:41/km at the marathon — which is exactly what real race results look like. A sub-4 marathon emerges as the honest target for a 25-minute 5K runner with proper marathon training.
Worked Example: From a 4-Hour Marathon Down to 5K
The formula works in reverse just as well. A runner finished a marathon in 4:00:00 — that is 14400 seconds for 42.1950 km — and wonders what 5K shape that represents. The ratio is 5.0000 ÷ 42.1950 = 0.1185. Riegel: T2 = 14400 × 0.1185^1.06 = 14400 × 0.1043 = 1501 seconds, which converts to 25:01.
The symmetry is satisfying: 4 hours for the marathon and 25 minutes for 5K are equivalent performances, each predicting the other within a second. The predicted 5K pace is 5:00 per kilometer, and the table shows 10K in 52:10 (5:13/km) and the half in 1:55:07 (5:27/km). If this runner’s actual 5K best is much slower than 25:01, it signals untapped speed — time for track work. If it is much faster, endurance is the limiter and long runs are the prescription.
Understanding Your Results
The headline prediction is the centerpiece: the clock time your current fitness is worth at the target distance, assuming equivalent training and conditions. The pace line translates it into the per-kilometer rhythm you would need to hold — the number to program into your watch for race day. The four numbered steps make the prediction auditable: your time in seconds, the distance ratio, the exponent applied, and the conversion back to clock time.
The equivalence table is where training insight lives. It converts the same fitness into all four classic distances, so you can spot mismatches between your actual personal bests and your equivalent times. A big gap at one distance reveals your limiter: slower than equivalent at short distances means you need speed work; slower at long distances means you need endurance. Coaches have used exactly this comparison for decades to individualize training, and now it takes one click.
Common Mistakes to Avoid
The classic mistake is feeding the formula a time that was not a full effort. Riegel’s anchor must be a genuine race-level performance; a comfortable training run predicts comfortable training paces, not your potential. Use a recent all-out race, ideally within the last two to three months, on a comparable course.
Another error is treating the prediction as a guarantee. The formula assumes similar fitness, weather, course profile, and fueling — a hilly marathon in heat will not match a flat cool-weather prediction. Recreational runners should also know the 1.06 exponent is slightly optimistic for them at marathon distance; adding 2–5% to long predictions is common coaching practice. Finally, do not predict across extreme gaps (a 1-mile time trial to a marathon) and expect precision: the formula is most reliable between neighboring distances, like 10K to half marathon.
Frequently Asked Questions
1. What is the Riegel formula?
T2 = T1 × (D2 ÷ D1)^1.06. Given a known time T1 at distance D1, it predicts the equivalent time T2 at distance D2. Peter Riegel derived the 1.06 exponent by fitting world-record performances across distances in the 1970s.
2. How accurate are the predictions?
Very good between neighboring distances for trained runners — usually within a few percent. Accuracy fades across extreme jumps (mile to marathon) and for undertrained runners, whose long-distance fade exceeds what the 1.06 exponent assumes.
3. Why is the exponent 1.06 and not 1.0?
Because pace declines with distance. An exponent of 1.0 would mean holding exactly the same pace forever; 1.06 captures the real endurance penalty, making a doubled distance cost about 2.085 times the time instead of 2.0.
4. Can I predict from a training run instead of a race?
You can, but the prediction inherits the effort level. A tempo-run input predicts tempo-level equivalents. For goal-setting, use a recent all-out race result as the anchor.
5. What is the difference between this and a pace converter?
A pace converter translates one pace unit into another (minutes per kilometer to minutes per mile) — same effort, different units. This calculator predicts a different effort at a different distance using the Riegel endurance model. They answer different questions.
6. Does the formula work for ultramarathons?
Roughly, but with growing error. Beyond the marathon, fueling, terrain, and walking breaks dominate, and the 1.06 exponent tends to under-predict times. Enter a custom distance to try, but treat ultra predictions as loose estimates.
7. Why do my actual times differ from the equivalents?
Because you are not equally trained at every distance. Running slower than your equivalent 5K time means you lack speed; slower than your equivalent marathon time means you lack endurance. The gaps are diagnostic — they tell you what to train.
8. Should beginners use these predictions for race goals?
Cautiously. Beginners often fade more than the formula expects at long distances. Use the prediction as an ambitious target, but set your primary goal a few percent slower until you have racing experience at the distance.
9. Does course elevation affect the prediction?
The formula assumes similar courses. A hilly target race will run slower than a flat-course prediction. Adjust expectations for elevation, heat, wind, and altitude rather than blaming the math.
10. What distances can I enter as custom?
Any distance from 0.1 to 500 km. A 3000m track time (enter 3 km) predicting a 10K, or a marathon predicting a 50K ultra, are both valid uses of the custom fields.
11. How do I use the equivalence table in training?
Compare each row to your actual personal best. Rows where you are slower than equivalent reveal weaknesses: short-distance gaps call for intervals and speed work, long-distance gaps call for long runs and aerobic volume.
12. Is the predicted pace realistic to hold evenly?
Even pacing is the ideal the prediction describes. In practice, most runners benefit from starting a touch conservatively and finishing strong — but the average pace across the race should match the prediction.
13. Who was Peter Riegel?
An American research engineer and competitive runner who, in a 1977 article, showed that endurance race records follow a simple power law. His formula remains the standard method for comparing performances across distances.
14. Can this predict triathlon run splits?
Only loosely. A triathlon run follows swimming and cycling, so fatigue makes the standalone running equivalent optimistic. Use it as an upper bound for what fresh legs could do.
15. Does the calculator store my race times?
No. Everything runs in your browser; nothing is saved or uploaded. Reset clears the form for your next “what if” scenario.
Final Thoughts
The Riegel formula is one of running’s elegant truths: a single hard race contains the blueprint of every other distance you could run. The Running Equivalency Calculator turns that blueprint into concrete targets — a 3:59:47 marathon for the 25-minute 5K runner, a 25:01 5K for the 4-hour marathoner — with the arithmetic open for inspection and a full table for diagnosis. Anchor it with a real all-out effort, respect the assumptions, and let the gaps between your actual and equivalent times write your next training plan.