Marathon Pace KM
Menu
← Back to pace chart hub

Marathon Time Predictor (KM + Miles)

Compare marathon time scenarios from a recent race (5K/10K/half), then consider your training context. This returns higher, middle, and lower slowdown scenarios — then links you into pacing tools.

Predictor Results How to use FAQ

Fast workflow: Predict your time → open the Marathon Pace Calculator for checkpoints + printable pace band → read why starting too fast costs minutes.

Prefer combining multiple races? Use: Combine races marathon predictor.

Marathon predictor

Enter a recent race and your training context. The race distance and time drive the calculation; training entries help you interpret it.

h m s

Use your recent 4–6 week average.

If you haven’t done a long run yet, be conservative.

Use experience to judge whether the projected effort is realistic; it does not change the formula.

The result flags tough conditions; the projections themselves assume comparable conditions.

Compare the scenarios with your actual training. A lower-slowdown projection is not a recommendation, and even the slower scenario may be too optimistic.

What to do with your result

Use the scenarios to explore assumptions, then assess the goal against training before building checkpoints.

Avoid the classic mistake: “banking time” early. Read: The math of time in the bank.

Read the guide that matches your input race: predicting from a 5K, predicting from a 10K, or predicting from a half marathon. Each explains how to interpret the conversion alongside your marathon preparation.

How to use this predictor (best practice)

  1. Start with your longest recent race (half marathon > 10K > 5K).
  2. Review your actual training. Weekly distance is context, not a calibrated adjustment to the formula.
  3. Use a range, then pick a target you can execute in your conditions.
  4. Generate checkpoints + pace band in the Marathon Pace Calculator.
  5. Plan execution with splits and negative split pacing.

Marathon predictor FAQ

Is this marathon time predictor accurate?

These are mathematical scenarios using Riegel exponents 1.06, 1.08 and 1.10. Weekly distance and longest run provide context but do not change the calculations. Actual outcomes can fall outside all three scenarios.

Why does it show a range instead of one time?

The scenarios show sensitivity to assumed slowing over distance. They are not a confidence interval or a guaranteed range.

What race distance predicts marathon best?

A half marathon is closer to marathon distance, so it requires less extrapolation than a 5K. No shorter race establishes marathon readiness on its own.

What this predictor assumes

Each scenario uses T2 = T1 × (D2 / D1)exponent, with distances in kilometres and times in seconds. Exponents 1.06, 1.08 and 1.10 show different assumptions about slowing over longer distances. Results are rounded to 30 seconds; splits use that displayed target. These are sensitivity examples, not a validated personal prediction or confidence interval.

Weekly distance, longest run and experience help you judge the output; they do not establish an individually calibrated endurance adjustment. The three calculations assume comparable performance conditions. Explore conditions separately.

My 1:50:57 half marathon gives approximately 3:51:19 at exponent 1.06. I did not achieve my sub-four goal at Sydney. Read the case study before treating a projection as an earned target, and see the methods and limitations.

Explore the Running Lab prediction and pacing collection for recorded race comparisons and the assumptions behind using one race to plan another.

Turn a half-marathon target into a race schedule

The half-marathon pace chart calculates 21.0975 km checkpoints. A prediction estimates performance; a split schedule describes the arithmetic of a chosen target.