Marathon time predictor calculator

A marathon time predictor calculator turns one trusted shorter race into a realistic 42.195 kilometre goal before you write a sixteen-week plan. Pete Riegel's endurance model scales a known distance D1 and finish time T1 to the official marathon with a single power: T2 equals T1 times the ratio 42.195 over D1, raised to one point zero six. The exponent a little above one is why a forty-minute ten-kilometre does not simply multiply by 4.22 into a marathon; average pace slows as the race lengthens. This capability locks the target at the World Athletics marathon, accepts kilometres and seconds only, and rejects missing or non-numeric fields so a blank form never invents a Boston-qualifying fantasy. Use it after a five-kilometre, ten-kilometre, fifteen-kilometre, or half-marathon result when you want a transparent clock time you can recompute by hand.

How the Riegel marathon time predictor works

Start from one completed race that is shorter than a marathon and that you trust: a measured course, a chip or gun time you would write in a training log, and no huge downhill that made the clock unrealistic. Convert that finish into total seconds so the arithmetic stays unit-clean. A twenty-five-minute five-kilometre is one thousand five hundred seconds; a forty-minute ten-kilometre is two thousand four hundred seconds; a ninety-minute half marathon is five thousand four hundred seconds.

Send the race length in kilometres, not miles, because the official marathon is defined as 42.195 kilometres and mixing units would inflate the projection by about sixty percent. Riegel's 1977 endurance rule then sets the predicted marathon time T2 equal to T1 multiplied by the quantity 42.195 divided by D1, all raised to the classic exponent one point zero six.

When D1 is a five-kilometre the ratio is large and the predicted pace is noticeably slower than 5K pace, which matches how recreational and elite athletes actually slow from 5K to 42.2 kilometres. When D1 is a half marathon the ratio is exactly two, so the formula reduces to T1 times two to the one point zero six, a number coaches have used for decades as a first marathon goal.

The exponent is fixed at one point zero six for reproducibility; this page does not fit a custom exponent from a multi-race history and does not age-grade the result. After the power is evaluated the response cleans floating-point noise to stable significant digits, formats both the known race and the predicted marathon as clock strings, and reports the distance ratio plus seconds-per-kilometre paces so you can audit every intermediate step on paper.

Where a marathon time predictor calculator earns its keep

First-time marathoners constantly ask what a recent ten-kilometre or half-marathon says about a spring or autumn 42.2 kilometre goal, and a single trusted oracle that returns seconds plus a readable clock string speeds plan writing and family conversations. Club coaches who write sixteen-week schedules need a documented formula athletes can recompute by hand rather than a black-box machine-learning estimate that changes when the vendor retrains.

Race directors and charity-team apps that show projected finish bands for pacing groups want the official marathon distance baked in so nobody types 26.2 miles against a kilometre 10K by mistake. Data engineers preparing synthetic marathon datasets for pacing dashboards need deterministic finish labels from known shorter races without network calls or model drift. If you later need a free target distance, pure pace unit conversion, age-graded scoring, or multi-race custom exponent fitting, treat those as separate search intents and landings rather than overloading this marathon time predictor calculator.

Always frame results as educational planning estimates, not medical or performance guarantees; course hills, weather, fueling, taper quality, and fitness changes can move a real marathon well away from any closed-form projection.