5K to Marathon Predictor: Why the Gap Is So Wide

Here is the direct answer. A 5K to marathon predictor cannot pin down one exact time. It can only point to a wide, honest range. The 5K-to-marathon jump is the least reliable race conversion in running. Simple pace math can guess a 10K time from a 5K quite well. That same math falls apart over a marathon. The marathon runs on endurance, not on raw speed.

The table below shows a plain scaling guess next to a realistic, endurance-aware range for the same 5K time.

5K time	Naive scaling guess	Realistic range
18:00	2:53	2:58 – 3:13
20:00	3:12	3:17 – 3:32
22:00	3:31	3:36 – 3:51
25:00	4:00	4:05 – 4:20
28:00	4:29	4:34 – 4:49

Can a 5K predict my marathon time?

A 5K can give you a rough marathon range. It cannot give you one exact number. A large study followed 2,303 recreational runners. It tested how well simple pace math holds up across race distances (Vickers & Vertosick, 2016). The math worked well through the half marathon. At the marathon, it broke down. It missed real finish times by 5 to 20 minutes. It almost always guessed too fast.

2,303

recreational runners studied to test pace-math accuracy across distances (Vickers & Vertosick, 2016)

That gap is not a small error. Twenty minutes can be the whole difference between a strong marathon and a rough one. A 5K shows your speed on a good day, for about 20 minutes of effort. A marathon asks your body to hold form for two hours, three hours, or more. Those are two very different tests of fitness.

This is why a smart marathon estimate shows a range. It should never show just one line. The range should grow wider as the guess gets less sure. The marathon depends on more than a 5K time can ever show.

Why is the 5K-to-marathon jump the least reliable conversion?

The 5K-to-marathon jump is the least reliable conversion. It spans the biggest gap in common road racing. Race math works best when two distances sit close together. A 5K predicts a 10K fairly well. Both races draw on similar fitness (RunnersConnect, 2024). Now stretch that same math out to about 8 times the distance. The errors stack up fast.

Research on scaling math backs this up. Studies show simple formulas work fine in the middle of the range. Their limits show up hardest at the far ends. Those ends are very short races and very long ones (García-Manso et al., 2012). The marathon sits at one far end. A short, fast 5K sits near the other. Put those two ends together. You get the widest, shakiest gap of all.

Think of it like guessing a full song from three seconds of the chorus. You can guess the mood. You cannot promise the rest of the words.

What decides your marathon time if not your 5K speed?

Your marathon time is decided mostly by endurance, not by your 5K speed. Three things matter most. A fast 5K shows none of them.

Weekly training volume. The same 2,303-runner study found that mileage moves marathon time a lot. This held true even for two runners with matching 5K times. Runners who trained 50 miles a week finished faster. They beat 30-mile-a-week runners by 25 to 32 minutes (Vickers & Vertosick, 2016).

Fuel storage. Your body stores a limited amount of carb fuel. It is called glycogen. Most runners hold enough for about 30 kilometers of hard running (Rapoport, 2010). A 5K never gets close to that limit. The race is over long before fuel runs low. The marathon lives right past that edge, mile after mile.

Durability. Sports scientists now study a trait called durability. It measures how much your body's key numbers slip during a long effort. It is not just what those numbers read when you are fresh (Maunder et al., 2021). Two runners can share the exact same 5K fitness. The more durable runner holds their form deep into the marathon. The other runner fades hard. A 5K time cannot tell you which one you are.

30 km

typical distance before glycogen stores run low in most runners (Rapoport, 2010)

None of these three things show up in a 20-minute race. All three decide your marathon day.

Does a faster 5K always mean a faster marathon?

No. A faster 5K time does not guarantee a faster marathon. Picture two runners with the same 20:00 5K. One runs 25 miles a week and races often. The other runs 50 miles a week, with a long run near 20 miles. Their 5K times match exactly. Their marathon times likely will not.

The high-mileage runner has built a bigger fuel tank. Their form holds up better under fatigue. The low-mileage runner has the same top-end speed, but less practice holding pace for hours on end. On paper, a naive guess treats them the same. On race day, they often finish 15 to 30 minutes apart.

This is the real reason a 5K-based marathon guess needs a range, not one number. A 5K measures the part these two runners share. It cannot measure the part that splits them apart once the race gets long.

How wide should my realistic marathon range be?

Your realistic range should widen if your training does not match marathon needs. A runner who already runs 40 to 50 miles a week can trust a tighter range. This is even more true with long runs past 30 kilometers. A runner who only races short and fast should expect the slow end of the range. They may land even slower than that.

Use the table above as a starting point, not a promise. If your weekly mileage sits well below marathon needs, lean toward the slow end. If you already have big long runs banked, lean toward the fast end. Either way, plan your early race pace off the slower number. Going out on the fast-end guess is risky. It is the surest way to run low on fuel before the finish line.

A second race result tightens this range fast. Add a recent 10K or half marathon time. A predictor can then read your endurance signal directly. It no longer has to guess that signal from one short, fast race alone.

Your recent long runs matter here too. A 16-mile or 20-mile long run, done at a steady pace, tells a predictor far more about your marathon than another fast 5K ever could. It shows how your form holds up late, after your legs are tired and your fuel is low. That is the exact part of race day a short race cannot test.

How does PIRX handle the 5K-to-marathon gap?

Most free calculators feed your 5K into one fixed formula. They hand back a single number. That number hides how shaky the 5K-to-marathon jump really is. PIRX is a proprietary machine-learning prediction engine. It is built to handle that gap in the open, not hide it.

PIRX breaks your fitness into 5 drivers. They are Aerobic Base, Threshold Density, Speed Exposure, Load Consistency, and Running Economy. A fast 5K time mostly lifts your Speed Exposure driver. It says little about Aerobic Base or Load Consistency. Those two drivers carry the most weight in a marathon. PIRX reads your real training data to score those drivers directly. It does not guess them from one short race. Each driver's effect shows up in seconds. All 5 drivers sum to your total change.

The output is a Projected Time with a Supported Range. The size of that range matches how much real endurance data backs it up. As one PIRX coach puts it, "a single number pretends the marathon is just a longer 5K. Your training data knows better, and so should your prediction." Add a long run, a tempo session, or a tune-up race. The range tightens right in front of you.

98%

validated prediction accuracy (PIRX users)

This is what makes PIRX different. A one-size-fits-all calculator cannot see this gap. A wrist VO2 max guess cannot see it either. Both treat a 5K and a marathon as the same race, just longer. PIRX does not make that mistake.

New to race projections? Start with the complete guide to predicting your race time. Coming from a half marathon instead? See what marathon you can run off your half. Want to check your finish-day plan? Read how to pace a marathon and is my goal time realistic.

Stop guessing what your training is worth. Don't rely on generic watch algorithms that treat every runner the same. Connect your Garmin, COROS, or Strava to PIRX in under 30 seconds. See your 5 performance drivers, and get a marathon projection built from your own endurance data, not just one fast 5K.

Sources

• Vickers, A.J. & Vertosick, E.A. (2016). An empirical study of race times in recreational endurance runners. BMC Sports Science, Medicine and Rehabilitation. (2,303 recreational runners; pace math underestimates marathon time by 5 to 20 minutes; weekly mileage moves marathon time 25 to 32 minutes.)
• RunnersConnect (2024). How accurate are race calculators? (Predictions are most accurate when the distance gap between races is small.)
• García-Manso, J.M. et al. (2012). The limitations of scaling laws in the prediction of performance in endurance events. Journal of Theoretical Biology.
• Rapoport, B.I. (2010). Metabolic factors limiting performance in marathon runners. PLOS Computational Biology. (Glycogen stores typically run low around 30 kilometers.)
• Maunder, E. et al. (2021). The importance of 'durability' in the physiological profiling of endurance athletes. Sports Medicine.