How it works
The quick overview
The Running Pace calculadora works out your running pace calculadora in seconds, using the 2026 figures most UK households actually check against.
Running Pace calculadora reads like a one-page cheatsheet: the widget at the top, the formula in a box, a worked example underneath, and the edge cases before the FAQ. No scrolling marathon.
If a value drops into a red band, act; if it is borderline, track. Measure at the same time of day for consistency — then work out the number and the rest of this page explains what the answer means.
Convert between pace, speed and time over any distance — plus split times for 5K, 10K, half and full marathon targets.
On this page you will see Split time, Marathon and Running pace 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 Marathon Time Predictor and the Speed Converter — those two calcs are the ones readers usually open right after this page.
Worked through on one example
Let's walk a concrete example through Running Pace calculadora.
Convert between pace, speed and time over any distance — plus split times for 5K, 10K, half and full marathon targets.
When to use this calculadora
Running Pace calculadora is aimed at people arriving with questions like these:
- "Marathon pace chart"
- "Min per km pace"
- "5K time calculadora"
- "What is running pace"
- "How to calculate running pace"
- "Running pace formula"
When to reach for something else
Every tool has an edge where it stops being the right answer. Running Pace calculadora 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.
Where this calculation usually breaks
Every time you work out the number for a new scenario, one of these creeps in — it's worth knowing them ahead of time.
- Ignoring the unit multiplier (k, M, %, basis points) on the input and feeding the raw number in anyway.
- Assuming the default settings match your context — check the calc's assumptions box before trusting the figure.
- Re-entering the result of a previous step as an input without keeping the full-precision number in front of you.
- Reading a negative answer as an error when the maths is telling you the inputs are in the wrong order.
- Cross-comparing to a tool that uses a different formula family (e.g. Mifflin vs Harris-Benedict) without saying so.
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:
- Marathon Time Predictor — Project a marathon finish time from a recent race (5K, 10K, half) using the Riegel and Cameron formulas.
- Speed Converter — Convert mph, km/h, m/s and knots with context: UK road signs use mph, most of Europe uses km/h, sailors use knots and SI uses m/s.
- 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 Running Pace calculadora 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.