Converting Your 5K PB to a 10K Goal Time

You've got a recent 5K time and you're trying to work out what that translates to over 10K. Multiply your 5K time by 2.06 and you'll get a solid baseline prediction for your 10K — a 20:00 5K predicts roughly 41:12 for 10K. I use this conversion constantly with athletes stepping up in distance, but the number I give a runner on day one is never the whole story. This is a starting estimate, not a guarantee. The real answer depends on what kind of runner you are, which I'll walk through below.

The Simple Formula and Why It Works (Roughly)

The maths behind this comes from Riegel's formula: T10K = T5K × (10/5)^1.06 = T5K × 2.06. The exponent is 1.06, not a flat 2.0, because pace naturally slows as distance doubles — fatigue accumulates, it doesn't scale linearly. That small exponent is doing a lot of work in the prediction.

When the Formula Breaks Down

Here's the accuracy window plainly stated: for well-trained runners with balanced training, this prediction lands within roughly 30-60 seconds of your actual 10K time. But general formula accuracy across all runner types is only about 80% — meaning roughly one in five runners will miss materially. I've coached this exact mismatch more than once.

Two specific breakdown cases matter. First, a 5K PB run off minimal aerobic base — say, a fast track 5K on low weekly mileage — overpredicts your 10K performance, because the formula assumes you have the aerobic endurance to sustain the extrapolated pace for twice the distance. I've watched fast-twitch 5K racers assume a flat conversion, chase it in their debut 10K, and blow up hard in the final 2-3km when the endurance simply wasn't there.

Second, a stale 5K PB — three or more months old, especially one set at the end of a dedicated training block — underpredicts your current fitness if you've kept training since. If you're speed-biased, apply a higher exponent, around 1.08 instead of 1.06. That lowers the predicted 10K performance — it predicts a relatively slower 10K than the flat formula suggests, and in my experience it's the more honest number for that runner profile.

Are You a 5K Specialist or an Endurance Runner?

Here's a concrete three-question self-check I use with athletes, framed as a decision rule rather than a vague spectrum.

First: is your weekly mileage under 25km, with the 5K as your longest hard effort? If so, you're speed-biased — expect to add 20-30 seconds to the standard prediction. Second: do you regularly run 8km+ easy long runs and rarely do short, fast reps? Then you're endurance-biased, and the standard prediction likely undersells you by 20-40 seconds. Third: is your training genuinely balanced across both? Then the standard 2.06x formula should hold within the 30-60 second window.

Why You Should Treat the Number as a Range, Not a Target

Every calculator online spits out a single number, and that's a problem. I'd reframe every prediction as a 90-second window instead — a 20:00 5K predicts somewhere between 40:45 and 42:15 for 10K, not one fixed figure. I recommend the range-based framing over the calculator norm precisely because a single number implies false precision that race day rarely honours.

Race-day variables — course profile, weather, and pacing execution — each shift the outcome independently of your underlying fitness. A hilly course or a warm morning can cost you 60-90 seconds on their own, entirely separate from whether your prediction was accurate in the first place.

Building in a Buffer for Your First 10K

For a first-ever 10K, subtract 10-15 seconds per km from the predicted pace for your opening 5K, then reassess at halfway. Start slower than the raw predicted pace and aim to negative split rather than chase the prediction from the gun.

I coached two runners toward the same debut 10K goal time. One followed the raw predicted pace from the start and faded badly over the last 3km, finishing well outside their target. The other used the 10-15 second per km buffer, felt comfortable through halfway, and negative split to a finish inside their predicted range. Same fitness level, same goal — the buffer made the difference. Debut 10K runners most commonly fail by going out at predicted pace and fading from unfamiliarity with the distance, not from lack of fitness.

Turning Your Predicted Time Into a Training Goal

A predicted time is only useful if the training between now and race day is actually built to close the aerobic gap between 5K sharpness and 10K endurance. Speed alone doesn't get you there — you need the long-run mileage and threshold work to sustain that pace for twice the distance. For the full workout progression, long-run build, and readiness markers, see our guide on how to train for the step up from 5K to 10K.

Frequently Asked Questions

Is the "multiply by 2.1" rule accurate, or too simple?

It's close, but 2.06 is more accurate than the commonly cited 2.1. Riegel's formula gives an exponent of 1.06, not a flat doubling, because pace naturally slows as distance increases due to accumulating fatigue. For well-trained, balanced runners, this lands within 30-60 seconds of the actual 10K time.

Why might my actual 10K time differ from my predicted time?

The formula assumes balanced training between speed and endurance. If your 5K PB came from a fast track effort on minimal weekly mileage, the formula overpredicts your 10K. If your 5K PB is stale — three or more months old — it likely underpredicts your current fitness. Race-day conditions add further variance.

Should I be more conservative for my first 10K?

Yes. For a debut 10K, start 10-15 seconds per km slower than your raw predicted pace and aim to negative split rather than chase the predicted number from the gun. Debut 10K runners most commonly fail by going out at predicted pace and fading in the final 2-3km, not from lack of fitness.

Does the conversion account for hills or race conditions?

No. The Riegel formula is a pure time-distance extrapolation and assumes comparable conditions between your 5K and your 10K. Hills, heat, wind, and a crowded start all shift the outcome independently of fitness, which is exactly why the predicted number should be treated as a range, not a fixed target.

What training factors make someone's 10K relatively stronger or weaker than predicted?

Weekly mileage and long-run distance are the biggest factors. Runners with low weekly mileage and a 5K-only focus tend to fade relative to the prediction. Runners who regularly run 8km+ easy long runs, even without much speed work, tend to outperform the standard prediction at 10K.

How reliable is a prediction if my 5K PB is old?

Less reliable the older it is. A 5K PB from more than three months ago, especially one set at the end of a dedicated training block, tends to underpredict your current 10K fitness if you've kept training since. Use your most recent representative 5K effort where possible.

Should sprinters and endurance-biased runners use different expectations?

Yes. Speed-biased runners should apply a higher fatigue exponent, around 1.08 instead of 1.06, which predicts a relatively slower 10K than the flat formula suggests. Endurance-biased runners with a strong long-run habit often outperform the standard prediction by 20-40 seconds.

What should I do with my predicted time once I have it?

Treat it as a training target, not a race-day guarantee. The prediction is only useful if your training between now and race day actually closes the aerobic gap between 5K sharpness and 10K endurance — building long-run distance and threshold work matters more than the number itself.

Some Other Pages You May Like