Marathon Time Calculator — calculate marathon time for training and performance. Evidence-based formula and benchmarks.
The Marathon Time Calculator predicts a 42.195-kilometre finish from another measured running performance. Its fixed target makes the headline result a marathon time and the accompanying pace rows describe the same estimate per kilometre and per mile.
A marathon projection stretches the source performance over a large distance change when the input is short. The Riegel relationship cannot assess long-run consistency, fueling, heat tolerance, course elevation, or the race-day decisions that often separate a plausible estimate from an actual finish.
For a shorter or longer endurance-distance comparison, see Half Marathon Calculator and Ultra Marathon Calculator. Distance-specific predictions do not account for individual endurance preparation or course conditions.
Use an event time that represents current fitness and be especially cautious when it is much shorter than a marathon.
The default three-hour-thirty-minute example is only a starting display; it does not imply that the runner has marathon-specific preparation.
The widget calculates target time = source time × (42.195 km ÷ source distance)^1.06. It then divides the marathon duration by 42.195 for pace per kilometre and by the equivalent mileage for pace per mile.
A half marathon in 1 hour 45 minutes projects to approximately 3 hours 39 minutes under the 1.06 exponent. The time increase is larger than a simple doubling because the model includes a distance-related slowdown, but it does not model individual fatigue or marathon-specific training.
The predicted finish is a starting hypothesis for goal setting. Runners with strong endurance training may perform better than a short-race projection, while insufficient weekly volume, missed fueling, illness, heat, or an ambitious early pace can lead to a slower result.
Average pace is not a split plan. A course with climbs, turns, or exposed weather may reward effort-based pacing instead of holding one number. The calculator does not account for a positive split, a conservative start, or planned aid-station time.
Prefer an input from a longer race when available; a half marathon gives more direct evidence about sustained effort than a short track test. Keep the source date and conditions visible, especially if fitness has changed since the result.
Use the estimate alongside training indicators such as long-run completion and recovery. The page does not decide whether the runner should start a marathon or how quickly mileage should increase.
If the source is a half marathon, the distance ratio is close to two and the prediction depends less on a long extrapolation than a 5K-based estimate. It still assumes the runner's endurance decay resembles the model's fixed exponent.
Compare pace at the same unit and rounding level. The mile and kilometre rows are conversions of the same finish duration, so small differences in rounded seconds should not be mistaken for separate model outputs.
For a first marathon, use the projection as one piece of information alongside training consistency, long-run recovery, and fueling practice. A strong shorter race cannot establish that those marathon-specific skills are ready.
A marathon prediction is more useful when reviewed beside completed training, recovery, and familiarity with fueling. None of those details enters the calculation, so a close match between the estimate and a past shorter race does not confirm marathon readiness. Save the source event and conditions, then treat the displayed pace as a conversation starter for a plan that also considers course profile and individual experience.
The fixed target equals 26.219 miles. The displayed pace conversion uses that equivalent distance and the same rounded finish time, so a few seconds of rounding can make the calculated pace differ slightly from a pace rounded independently from raw inputs.
At the same source and target distance the predicted time equals the source time; for a shorter input, the time ratio grows according to the 1.06 exponent. This check helps explain why the page does not simply multiply a short race time by a fixed marathon factor.
Do not read a projected marathon time from a short event as a promise. The farther the target is from the observed distance, the more the result depends on the model's general endurance assumption.
Do not enter a time in minutes while leaving the hours field at zero if the input is over 59 minutes and the user expects a normalized clock. The engine sums the numeric fields; use hours and minutes consistently for clarity.
Do not compare an estimate to a marathon with a different course or weather profile as if both were equivalent tests. The tool has no elevation, temperature, wind, or race-day interruption inputs.
The output is a general mathematical estimate and not a health assessment, race entry qualification, or individual coaching plan. Training and race-day decisions should account for personal condition and appropriate professional guidance.