Fitness & Sports

Race Predictor Calculator

Solve your own fatigue exponent from two race results instead of assuming Riegel's 1.06, then project every distance from it.

Race Predictor Calculator

Results recalculate instantly on every keystroke. Nothing you type is transmitted.

Your first race
Your second race
Your personal fatigue exponent
Solved from your two races, not assumed.
What that exponent says about you
Projected times on your own exponent
What Riegel's 1.06 would predict
What Cameron's formula predicts
The disagreement at the marathon
How far you can trust this projection
Marathon pace on your exponent
How the exponent is solved
Why a single fixed exponent fails
What this cannot know
Where to go next

What this result does not account for

  • A curve through two points: it cannot see training volume, long-run history, terrain, weather or fuelling.
  • Most reliable between about half and twice the anchor distance.
  • Assumes both races were genuinely maximal and from the same block of fitness.
  • Breaks down beyond the marathon, where terrain and fuelling dominate.
  • Two races months apart describe two different runners.
Zero-Server Execution Updated 11 Aug 2026 Reviewed by Dr. Ayesha Rahman IEEE-754 Double Precision

In short: Riegel's formula assumes everybody fades at the same rate, 1.06. Almost nobody does. A runner with a 20:00 5K and a 42:00 10K has a personal exponent of 1.0704, which projects a 3:16:07 marathon against Riegel's 3:13:13. Run the 10K in 41:00 instead and the exponent falls to 1.0356 — a 3:02:06 marathon, six minutes faster than Riegel predicts. The gap between the two is the point.

Formula

T₂ = T₁ × D₂D₁k     k = ln(T₂ ÷ T₁)ln(D₂ ÷ D₁)

The first form projects a time; the second solves the fatigue exponent k from two known results. Riegel fixes k at 1.06; this page measures it.

Worked Example

  1. Pick two honest races. Both should be recent, genuinely raced, and from the same block of fitness. A parkrun you jogged is not a data point.
  2. Enter distances and times. Times take mm:ss or h:mm:ss. A bare number is read as minutes.
  3. Read your exponent. k = ln(T2/T1) ÷ ln(D2/D1). Below 1.05 you hold pace unusually well; above 1.08 endurance is your limiter.
  4. Compare the three columns. Your exponent, Riegel's 1.06 and Cameron's variable exponent. Where they disagree, the gap is the honest uncertainty.
  5. Plan against the slower figure. When projections disagree, the conservative one is the one that keeps the last 10 km survivable.

A 20:00 5K and a 42:00 10K give k = ln(2520/1200) ÷ ln(2) = 1.0704, projecting a 3:16:07 marathon — nearly three minutes slower than Riegel's 3:13:13, because this runner fades faster than the textbook assumes.

Strengths & Limits Of This Model

Where this engine is strong

  • Measures your own fatigue rate instead of assuming the population average.
  • Prints Riegel and Cameron alongside, so the disagreement is visible.
  • Anchors on the longer race to shorten the extrapolation.
  • Refuses to project from a physiologically implausible pair.

Where it stops

  • Requires two honest races to be worth more than a generic calculator.
  • An exponent solved from two points is exquisitely sensitive to one mispaced race.
  • Says nothing about whether you have trained for the distance you are projecting.
  • Long extrapolations remain uncertain however the exponent was obtained.

Risk & accuracy notice. A projected time is a description of a curve, not a training plan. Running a marathon off a 5K projection without the long-run volume to support it is the most common route to injury and to a collapse after 30 km. Build the distance first; use the projection to choose a pace, not to justify skipping the training.

Practical Use Cases

Setting a realistic marathon goal

The commonest use, and the one where a generic exponent does the most damage. A runner whose personal k is 1.10 will be shown a marathon target sixteen minutes faster than reality by a standard calculator.

Diagnosing speed against endurance

A high exponent says your short-distance speed outruns your aerobic base, which is a training prescription: more volume, more long runs. A low one says the opposite.

Checking whether a race was well executed

If a new race falls well off your established curve, either your fitness changed or that race was mispaced. Both are worth knowing.

Choosing a target distance

Comparing projections across distances shows where your current profile is most competitive, which is often not the distance you have been training for.

Methodology & Editorial Standards

Given two results the engine solves k = ln(T₂/T₁) ÷ ln(D₂/D₁), an exact solution of the power law through two points rather than a fitted average. Riegel’s fixed 1.06 and Cameron’s distance-varying exponent are printed alongside as comparison columns, and the marathon disagreement between them is quantified, because where published models differ that difference is the honest uncertainty in the projection. Extrapolation error grows with the distance ratio, so projections are anchored on the longer of the two supplied races and the engine states which one it used. An exponent below 1.0 implies the longer race was run faster than the shorter one, so the engine names the likely cause and withholds the table instead of projecting from it. The half marathon is treated as 21,097.5 m and the marathon as 42,195 m, because a power law with an exponent above 1 amplifies input error.

Computation runs in IEEE-754 double precision at full internal precision; rounding to two decimal places occurs strictly at the display layer, so no cumulative drift enters the result. All monetary outputs use accounting presentation — grouped thousands, two decimals, negatives in parentheses — so figures can be transcribed directly into a model or working paper. Division-by-zero and out-of-domain inputs return an em-dash rather than a misleading number.

This engine was reconciled against an independent reference implementation and hand-verified for the worked example above before release. Our full five-stage review process is published on the About Us page.

Dr. Ayesha Rahman Clinical & Life Sciences Lead · ApexConverter

Exercise physiology and sports-science metrics. Last reviewed: 11 August 2026.

Disclaimer. This calculator is provided for informational and modelling purposes only and does not constitute financial, tax, legal, medical, or engineering advice. Verify all figures with a qualified professional before acting on them.


Race Predictor Calculator — 20 Expert FAQs

20 analyst-written answers to the questions practitioners actually ask — optimised for voice and answer-engine retrieval.

How does a race time predictor work?

It fits a power law between distance and time: T₂ = T₁ × (D₂/D₁)^k. The exponent k describes how much your pace fades as distance grows. If k were 1.0 your pace would never slow, so you would run a marathon at 5K pace. Real values sit a little above 1.

What is the Riegel formula?

Peter Riegel's power law with the exponent fixed at 1.06, published in Runner's World in 1977 and refined in 1981. He derived 1.06 from competitive results between 800 m and the marathon. It is the most widely used race predictor in the world and is a reasonable average — but an average is not you.

Why solve for my own exponent instead of using 1.06?

Because the error compounds with the extrapolation. Two runners with identical 5K times but exponents of 1.04 and 1.10 are separated by well over twenty minutes at the marathon. Your exponent is measurable from two races you have already run, so assuming it is a choice, not a necessity.

What is a good fatigue exponent?

There is no good or bad, only a profile. Elite distance runners cluster near 1.05, recreational runners near 1.06, and runners with limited aerobic base at 1.08 or above. A low exponent means you hold pace well over distance; a high one means speed is ahead of endurance.

Which two races should I enter?

Two recent, genuinely maximal efforts from the same period of fitness, at clearly different distances. A 5K and a 10K, or a 10K and a half. The further apart the distances, the more reliable the exponent — but only if both were truly raced.

Can I use just one race?

Yes. Clear the second time and the page falls back to Riegel's 1.06 and says so. You get a projection, but it is the textbook assumption rather than a measurement of you.

What is the Cameron formula?

A 1998 refinement in which the exponent falls as the anchor race lengthens: 1.06 − 0.0026 × the anchor distance in miles. It exists because a fixed 1.06 over-predicts for elite runners and under-predicts for slower ones over long extrapolations. It is shown here as a third opinion.

Why is my exponent below 1.0?

Because the longer race was run at a faster pace than the shorter one, which no physiology supports in two maximal efforts. Almost always the short race was a training effort, a hilly course, or from a different year. The page refuses to project from such a pair.

How far can I trust a marathon predicted from a 5K?

Not very. Projections are most reliable between roughly half and twice the anchor distance. A marathon is over eight times a 5K, so the arithmetic is precise but the assumption behind it is doing enormous work. Use a half marathon as the anchor if you have one.

Does the predictor account for training?

No, and that is its central weakness. The curve knows two results and nothing else. A runner who has never exceeded 25 km in training will not run the marathon the curve projects, regardless of how good their 10K is, because the limiter is durability rather than pace.

Why anchor on the longer race?

Because it shortens the extrapolation. Projecting a marathon from a half is a factor of two; projecting it from a 5K is a factor of eight. The engine anchors on the longer of your two results for exactly that reason and says so in the output.

Do hills and weather affect the prediction?

Substantially, and the model cannot see either. A hilly or hot race produces a slow time that inflates your apparent exponent and makes every longer projection pessimistic. Use results from comparable conditions.

Should I use my predicted time as my goal time?

As a starting point, not a commitment. When the three columns disagree, plan against the slower one. A marathon started two per cent too fast does not cost two per cent at the finish; it costs far more, because the collapse is non-linear.

How often should I recalculate?

After every race that is genuinely raced. Your exponent shifts as your training shifts: a winter of long runs lowers it, a block of track work raises it. Recomputing after each race turns the exponent into a training feedback signal.

Why do different calculators give different answers?

Because they assume different exponents, or use table lookups such as Daniels' VDOT rather than a power law. They agree on the shape of the curve and disagree on how fast pace fades. That disagreement is real uncertainty, not a bug in one of them.

Is this the same as VDOT?

No. VDOT converts a race result into an oxygen-cost figure and reads equivalent performances off tables derived from Daniels and Gilbert's work. A power law is simpler and, once your own exponent is solved, personalised in a way generic VDOT tables are not. They usually agree closely at nearby distances.

Can I use this for ultramarathons?

Not reliably. Beyond the marathon the power law breaks down: terrain, night running, fuelling and sleep dominate, and the exponent required to describe a 100-mile result bears little relation to the one that describes road racing.

Does age change my exponent?

Indirectly. Masters runners often show a lower exponent, holding pace over distance well while losing top-end speed. That is a real shift in profile and it is exactly the kind of thing a fixed 1.06 conceals.

What if my two races were months apart?

Then the exponent describes a runner who no longer exists. Fitness moves. Use results from the same training block, ideally within six to eight weeks of each other, or the number mixes two different athletes.

Why does the marathon projection look so much slower than my friend's?

Most likely because they used a fixed 1.06 and you solved your own. If your exponent is above 1.06, every generic calculator on the internet will flatter you. The uncomfortable number is usually the useful one.

Related Fitness & Sports Engines