⏵ Free tool · No signup

Running Race Equivalent Calculator: What Can You Run?

Punch in one recent race and you will see the equivalent finish time and pace at every standard distance, from the 5K all the way to the 100 miler. It runs on the same Daniels VDOT and Riegel endurance math the Summit Line app uses to read your fitness and project your race day.

⏵ YOUR RECENT RACE

ONE RESULT IN

Race distance
Finish time
hr
min
sec

Enter your most recent, hardest race for the best read. The closer it is in distance to the race you are targeting, the tighter the prediction.

Your fitness score (VDOT)
40.0

Solid recreational fitness. Plenty of room to build.

⏵ WHAT YOU CAN RUN

YOUR EQUIVALENT TIMES

DistanceFinishPace / mi
  1. 5K23:597:43
  2. 10Kyour race50:008:03
  3. Half Marathon1:50:198:25
  4. Marathon3:53:218:54
  5. 50K4:48:589:18
  6. 50 Mile8:05:249:43
  7. 100K10:29:2810:08
  8. 100 Mile17:42:2310:38

Road rows (5K to marathon) come from your Daniels VDOT. The ultra rows (50K and up) use the Riegel endurance formula with a higher fatigue exponent, so they stay honest. Every prediction assumes you are trained for that distance.

⏵ This is the generic version

One race is one data point. Summit Line dials the projection in to YOUR actual course profile, your real pace-by-grade from months of runs, your fitness trend, and your projected race-day splits, so the number you chase is earned, not guessed.

How race equivalency works

Two races run on the exact same fitness do not come out at the same pace. Longer races are slower per mile, because the fatigue piles up. All an equivalency model does is take one performance and map it onto another distance at the same effort. Here is the logic this calculator runs on, so the table above makes sense.

One race becomes a single fitness score (VDOT)

First the calculator turns the race you enter into a Daniels VDOT, one number that sums up the aerobic engine behind that run. It pulls that from the relationship between how fast you ran and the fraction of your VO2max you can hold for that long. A quicker time at a given distance means a higher VDOT, and that one score becomes the anchor for every other distance in the table.

Because every row comes off that same VDOT, the numbers all agree with each other. The 5K, the half, and the marathon are one runner on one day, not three guesses that have nothing to do with each other.

VDOT gives you equivalent paces for the standard road distances

From your VDOT, the model runs the Daniels math backward to land on the equivalent pace at each road distance. That is why your 10K pace is faster than your half pace, which is faster than your marathon pace. Same engine, just held longer, so the pace per mile eases off a bit. What you get is the goal pace a runner of your fitness would aim for if they trained for that race on purpose.

These road rows, the 5K through the marathon, are the ones I would trust most in the table, because the physiology underneath them is exactly what VDOT was built to measure.

Past the marathon, the Riegel endurance formula takes over

Ultras are a different sport. A 50K, 50 miler, 100K, or 100 miler is not really about aerobic power anymore, it is about fatigue resistance, fueling, and how durable you are. So for those rows the calculator switches to the Riegel endurance formula, where time scales with distance raised to a fatigue exponent, and it bumps that exponent up above the marathon to account for how much steeper the cost gets on the long days.

That keeps the long numbers honest. A flat linear scale-up would hand you a ridiculously fast 100 miler off a quick 10K, and the higher fatigue exponent drags that back down to earth.

The honest caveat: a prediction is not a finish

Every row assumes you have put in the training that distance asks for. A 5K-fit runner has the engine for a fast marathon on paper. But without the long runs, the time on feet, and a fueling plan you have actually rehearsed, that marathon stays on paper. And the further the predicted distance sits from the race you entered, the more the number is just leaning on guesses about your endurance.

Use the table to set a target your fitness points to, then build the block that earns it. That gap, between what your engine is worth and what you have actually trained for, is exactly what Summit Line is built to close.

Race equivalent calculator FAQ

What is a race equivalent calculator?

You give it one race you already ran and it tells you what you could run at other distances on the same fitness. Run a 21-minute 5K and it spits back the marathon, the half, the 10K, even the 50K or the 100 miler that roughly match that engine. Think of it as one snapshot of your fitness, projected sideways across every distance, so you can see what your current shape is worth at a race you have not lined up for yet.

How accurate is the prediction?

On the roads, from the 5K to the marathon, a decent model lands within a few percent if your training actually matches the distance. The further out you go, the more it drifts. And that makes sense, because finishing a 100 miler comes down to fueling, heat, vert, sleep, and how much your body can take, and none of that shows up in one short race. So trust the road numbers, and treat the ultra numbers as a best case ceiling that only holds if you have put in the long-run work.

What is VDOT and how does it work?

VDOT is a single fitness score from Jack Daniels. It comes out of a race result, off the relationship between how fast you run and the percentage of your VO2max you can hold for that long. A VDOT near 40 is recreational, 50 is a competitive amateur, and 60 or higher is sub-elite. This calculator works out your VDOT from the race you punch in, then uses that one number to back out equivalent paces at every distance, so each row is the same engine.

Why do longer races use a different formula?

Short races come down to aerobic power, and that is exactly what VDOT measures. Ultras are a different animal. Out there it is fatigue resistance, fueling, and how durable you are, which is a whole other thing. So above the marathon this tool switches to the Riegel endurance formula with a higher fatigue exponent, which means the 50K, 50 miler, 100K, and 100 miler get docked harder than a plain scale-up would tell you. That keeps the long numbers honest instead of way too rosy.

Can I predict a marathon from a 5K?

Yes, and people do it all the time. Drop in your recent 5K and the marathon row shows the time and goal pace for someone of that fitness. Here is the catch. That number assumes you have done the marathon work, the long runs, the time on feet, the fueling. If you are 5K-fit but have never gone past 10 miles, you will not hit it. So treat it as a target your fitness points to, then go earn it with the right block.

Should I use a 5K or a longer race for the best estimate?

Pick the race closest in distance and effort to what you are aiming at. If you want a marathon number, a recent half marathon beats a 5K by a mile, because it taps more of the aerobic endurance a marathon actually asks for. The rule is simple. The further your input race is from the distance you are guessing at, the more the math is leaning on assumptions about your endurance. Your most recent, hardest, most similar race is always the best thing to feed it.

Turn the prediction into a plan

Summit Line reads your real fitness off your own runs, projects your race-day pace on your actual course profile, and builds the block that closes the gap between what your engine is worth and what you have trained for. Pace from your own data, an AI race brief, and a finish you have already rehearsed.

These equivalents are model estimates from the Daniels VDOT and Riegel endurance formulas. They assume you are trained for the target distance, and they get less precise the further the predicted distance is from the race you entered, especially out at the ultra distances where fueling, heat, vert, and durability run the show. Use them as a target, not a guarantee.