How it works
marathon time calculadora — the short version
The Marathon Time Predictor works out your marathon time calculadora in seconds, using the 2026 figures most UK households actually check against.
The marathon time calculadora question usually comes up mid-conversation — with a partner, a client, a tax adviser. Marathon Time Predictor is the tool you can pull up on a phone and settle it in thirty seconds.
A number is a prompt to talk to your GP, not a diagnosis. Rest 5 minutes before taking the reading — then work out the number and the rest of this page explains what the answer means.
Project a marathon finish time from a recent race (5K, 10K, half) using the Riegel and Cameron formulas.
On this page you will see Race time prediction and Riegel formula treated as first-class terms — each one is linked to the calculators and references that use it, so you can follow the thread without retyping queries into a search bar.
If it helps, jump straight to the Health hub or compare with the Running Pace calculadora and the VO₂ Max calculadora — those two calcs are the ones readers usually open right after this page.
A worked example, step by step
An example grounded in actual health figures beats a generic one every time:
Project a marathon finish time from a recent race (5K, 10K, half) using the Riegel and Cameron formulas.
Moments this tool earns its keep
Marathon Time Predictor is aimed at people arriving with questions like these:
- "Riegel formula"
- "Marathon predictor"
- "Half marathon to marathon"
- "What is marathon time"
- "How to calculate marathon time"
- "Marathon time formula"
Where the number stops being useful
Every tool has an edge where it stops being the right answer. Marathon Time Predictor is no exception:
- For legally binding tax or medical decisions — cross-check with HMRC, NHS or a qualified professional.
- For very large or very small extremes the rounding error outgrows the useful precision.
- When the underlying rate or threshold has changed since the page was last reviewed — always verify with the primary source.
- When the input you have is already a derived figure (net of something) — feeding it in as "gross" will double-subtract.
Five things that trip everyone up
Every time you work out the number for a new scenario, one of these creeps in — it's worth knowing them ahead of time.
- Misreading the unit in the label — 'per year', 'per month' and 'per day' versions of the same figure differ by 12× or 365×.
- Taking a ratio and multiplying it by the wrong side of the inputs — always write the ratio as A/B with labels before running.
- Trusting a screenshot of someone else’s calculation — rerun it yourself with the same inputs, numbers drift.
- Assuming percentages add up. 10% off then 10% more is not the original price — it is 99% of it.
- Not refreshing the page when thresholds are date-sensitive. If the page was cached yesterday, bank rates may already be yesterday’s.
The sources behind the numbers
Where the maths needs an external authority, we cross-check against:
- England Athletics
- RRCA
Works well alongside
If this question keeps coming up for you, the same cluster of tools usually comes next:
- Running Pace calculadora — Convert between pace, speed and time over any distance — plus split times for 5K, 10K, half and full marathon targets.
- VO₂ Max calculadora — Estimate VO₂ max from the Cooper test, Rockport walk test, or max HR — with fitness-category banding.
How we keep this accurate
Our calculadoras run on pure, unit-tested functions — the same logic lives in the browser and in the CI test suite. When tax rates, thresholds or official figures move, the update lands within 24 hours of the announcement. You can read the editorial policy and corrections policy.
Found an out-of-date number on Marathon Time Predictor or anywhere else in the Health toolkit? Send it to the editorial desk and we'll patch it. Or browse the full calculadora directory for the next tool you need.