Pace Calculator
Convert between time, distance and pace for any sport — leave any one of the three blank and the engine solves for it, in min/km, min/mi, km/h, mph or m/s.
Pace Calculator
Results recalculate instantly on every keystroke. Nothing you type is transmitted.
What this result does not account for
- No fatigue model — holding one pace across every distance is arithmetically valid and physiologically impossible.
- Takes no account of gradient, wind, heat, altitude or surface.
- GPS distance is typically accurate to 1–2 per cent, and worse in cities or under tree cover.
- Treadmill belt speeds are often miscalibrated by several per cent.
In short: Pace is time divided by distance. Run 10 km in 50:00 and your pace is 5:00 per kilometre, 8:03 per mile, or 12.00 km/h. This engine solves for whichever value you leave blank: enter any two of time, distance and pace and it returns the third, converted into every common unit.
Formula
pace = time ÷ distance
speed = distance ÷ time
min/mi = min/km × 1.609344
Distance is normalised to kilometres internally; every other unit is a conversion of the same underlying speed. 1 mile = 1.609344 km exactly, by international agreement since 1959.
Worked Example
- Convert the entered distance to kilometres (×1.609344 for miles, ÷1,000 for metres).
- Convert the entered time to seconds.
- Divide seconds by kilometres to obtain seconds per kilometre.
- Multiply by 1.609344 for seconds per mile; divide 3,600 by seconds per kilometre for km/h.
- Multiply the per-kilometre figure by each race distance to produce the split table.
10 km in 50:00 → 3,000 seconds ÷ 10 km = 300 s/km = 5:00 per kilometre, which is 8:03 per mile, 12.00 km/h, 7.46 mph and 3.33 m/s.
Strengths & Limits Of This Model
Where this engine is strong
- Solves in any direction between time, distance and pace
- Every common unit printed simultaneously, so nothing has to be converted by hand
- Works for running, cycling, swimming and rowing alike
Where it stops
- Deliberately contains no training theory — use the Running Pace Calculator for zones
- Average pace conceals the split pattern that actually determines a race
Practical Use Cases
Reading a treadmill in your own units
Converts a console speed in km/h into the pace your watch displays, and back again.
Testing a goal before committing
Shows the finish time a target pace implies, so the goal is checked before the race, not during it.
Following a plan written in other units
Translates a training plan in min/mi into min/km without hand arithmetic.
Checking splits mid-race
Gives the time you should pass each common distance if the pace holds.
Comparing across sports
Puts a cycling speed and a running pace on the same scale via m/s.
Methodology & Editorial Standards
The engine implements the standard published formula for this calculation. Inputs are validated for domain and sign before evaluation, and any undefined case returns an em-dash rather than a spurious value. Pace is a pure ratio and requires no empirical model: the engine normalises distance to kilometres, divides, and converts. The race-distance table applies the entered pace unchanged and is explicitly labelled as arithmetic rather than a prediction, because no fatigue model is applied.
Computation runs in IEEE-754 double precision at full internal precision; rounding to two decimal places occurs strictly at the display layer, so no cumulative drift enters the result. All monetary outputs use accounting presentation — grouped thousands, two decimals, negatives in parentheses — so figures can be transcribed directly into a model or working paper. Division-by-zero and out-of-domain inputs return an em-dash rather than a misleading number.
This engine was reconciled against an independent reference implementation and hand-verified for the worked example above before release. Our full five-stage review process is published on the About Us page.
Disclaimer. This calculator is provided for informational and modelling purposes only and does not constitute financial, tax, legal, medical, or engineering advice. Verify all figures with a qualified professional before acting on them.
Pace Calculator — 20 Expert FAQs
20 analyst-written answers to the questions practitioners actually ask — optimised for voice and answer-engine retrieval.
What is my pace if I run 10 km in 50 minutes?
Exactly 5:00 per kilometre, which is 8:03 per mile or 12.00 km/h. Divide 3,000 seconds by 10 kilometres to get 300 seconds per kilometre, then divide by 60 to read it as minutes and seconds.
How do I convert minutes per kilometre to minutes per mile?
Multiply by 1.609344. A 5:00/km pace is 5:00 × 1.609344 = 8.05 minutes, which is 8 minutes and 0.05 × 60 = 3 seconds, so 8:03 per mile. The mile figure is always larger because a mile is longer than a kilometre.
Why does my watch show a different pace from this calculator?
Three reasons. Your watch reports instantaneous or lap pace rather than the average over the whole session; GPS distance drifts by 1 to 2 per cent under trees, in cities and on winding trails; and watches smooth the figure heavily. This engine gives you the exact average implied by the distance and time you entered.
Is pace the same thing as speed?
They are inverses of each other. Pace is time per unit distance and gets smaller as you get faster; speed is distance per unit time and gets larger. Runners generally think in pace, cyclists and swimmers in speed, which is why this engine prints both.
What does m/s mean and when would I use it?
Metres per second is the physics-standard unit and the one used in track analysis and biomechanics. A 5:00/km pace is 3.33 m/s. It is also the easiest unit for comparing across sports, because it involves no arbitrary distance conversion.
Can I use this for swimming or cycling?
Yes. The arithmetic is identical for any sport where distance and time are measured. Swimmers usually prefer pace per 100 m, which you can get by entering your distance in metres. Cyclists generally read the km/h and mph figures rather than the pace.
If I hold my 5 km pace, what marathon time does that give?
The engine prints the answer, but treat it as arithmetic rather than a forecast. Multiplying 5 km pace by 42.195 assumes zero fatigue over four hours of running, which is physiologically impossible. For a real projection use the Race Predictor Calculator, which applies a fatigue exponent.
Why is my average pace slower than all my kilometre splits?
Almost always because the measured distance is longer than the nominal distance. If your watch recorded 10.15 km for a 10 km race, your average pace is computed over the extra 150 metres. Race courses are measured along the shortest legal line, and nobody runs that line exactly.
How accurate is treadmill pace?
Treadmill belt speed is frequently out by several per cent, and calibration drifts as the belt and motor wear. Treat the console figure as approximate unless the machine has been calibrated recently. The absence of air resistance also makes a given belt speed easier than the same pace outdoors.
What is a good running pace for a beginner?
There is no universal answer, and the honest one is that it depends on age, training history and goal. A more useful test than any benchmark is the talk test: if you can speak in full sentences, you are in the easy range where most training should happen, whatever the number on the watch says.
Should I enter my time in minutes or as h:mm:ss?
Enter minutes. For 1 hour 50 minutes enter 110. The engine converts internally and prints the result back in h:mm:ss format, so a marathon reads as 3:50:01 rather than 230 minutes.
Does elevation change my effective pace?
Substantially. A one per cent gradient costs most runners roughly 3 to 4 seconds per kilometre uphill, and returns rather less than that downhill because braking forces limit the gain. This engine takes no account of gradient; it converts the numbers you give it.
Why is 1 mile exactly 1.609344 kilometres?
Because the international yard was fixed at exactly 0.9144 metres by agreement in 1959, which makes the mile exactly 1,609.344 metres. It is a defined conversion, not a measured one, so the figure never changes.
How do I pace a race I have never run before?
Work backwards from a recent result at a different distance using a fatigue model rather than assuming you can hold your current pace further. Then subtract a little for the unknown. Going out at goal pace when your fitness is a guess is how most first-timers blow up.
What is the difference between average pace and moving pace?
Moving pace excludes time when your watch judged you to be stopped, at traffic lights or aid stations. Average pace includes it. Race results always use elapsed time, so if you train on moving pace you will be slower on race day than you expect.
Can pace be negative or zero?
No. Both time and distance must be greater than zero for pace to be defined, which is why the engine refuses to compute and shows an em-dash rather than returning a spurious number.
Is this pace calculator free to use?
Yes. It is free, requires no account, and has no usage limits. ApexConverter is funded by contextual advertising, never by selling user data.
Is my data sent to a server?
No. The engine runs as Vanilla JavaScript inside your browser under our Zero-Server Client-Side Execution model. Your figures are computed locally and are never transmitted, logged, or stored.
How accurate is this calculator?
It applies the standard closed-form formula in IEEE-754 double precision, rounding only at the display layer. The engine is reconciled against an independent reference implementation before release.
Does it work on mobile?
Yes. The interface is mobile-first with numeric keypad hints and is tested down to a 320-pixel viewport with no horizontal scrolling.