How to Calculate Running Pace (Time, Distance and the Splits in Between)
Updated: 2026-11-02
Pace is the unit that connects the number on your watch to the number on the finish banner. It is just time divided by distance — minutes per kilometre or per mile — and it works in both directions: a goal time and distance give you the pace to run, and a distance and a pace give you the time you will finish in. This guide shows the exact formula, walks through a 5K example, explains the split table the calculator builds, and covers what a negative split actually means.
The short answer
Pace = total time ÷ distance. Run 5 km in 30 minutes and your pace is 30 ÷ 5 = 6:00 per km. A goal time of 1:30:00 over a half marathon (21.1 km) gives about 4:17 per km, the pace you need to hold for the finish time.
The calculator works both ways: enter a distance and a time to get a pace, or enter a distance and a pace to get a finish time. It supports kilometres and miles, has presets for 5K, 10K, half and full marathons, and builds a split table for every kilometre or mile of the run.
- Pace = total time ÷ distance
- 5K in 30:00 = 6:00 per km
- Half marathon in 1:30:00 ≈ 4:17 per km
- The same math reversed: distance × pace = time
Pace: minutes per kilometre or per mile
Running pace is a unit of speed expressed as time per distance — minutes (and seconds) per kilometre, or per mile if you prefer imperial. A faster runner has a smaller number. A 4:00/km pace beats a 5:30/km pace; a 7:30/mile beats an 8:00/mile.
A 1 km is about 0.621 miles, so the two units are related but not equal. The calculator keeps them separate: pick kilometres or miles and every number, including the splits, is computed in that unit. Mixing them is the most common source of 'why is my pace slower than expected' confusion.
Pace and speed are the same idea from opposite directions: speed is distance per time (km/h), pace is time per distance. A 10 km/h run is a 6:00/km pace, and a 8 km/h run is a 7:30/km pace. Runners think in pace because it tells you how long a given distance will take; speed tells you how far a given time will carry you. The calculator speaks the runner's language and does not force you to convert to km/h.
The two directions the calculator runs
Most people want to know the pace to hit a goal time, so the primary direction is distance plus time to pace: pick the race distance, type the time you are aiming for, and read off the pace to hold. The reverse direction — distance plus pace to a finish time — is how you plan a training run: 'I want to run a 5:00/km pace for 10 km, what time will I finish?'
Step by step: goal time to pace
Choose kilometres or miles, and the distance — or tap the 5K, 10K, half or full marathon preset.
Type the time you want to finish in, as hours:minutes:seconds or minutes:seconds.
Read the pace: that is the per-km or per-mile pace to hold for the goal.
Check the split table to see the cumulative time at each distance mark.
Step by step: pace to finish time
Choose the unit and the distance you plan to run.
Type the pace you want to hold, as minutes:seconds per unit.
Read the finish time: that is distance times pace.
Use the splits to plan when you should be at each mark.
A worked example: 5K in 30 minutes
Goal: 5 km in 30:00. Pace = 30:00 ÷ 5 = 6:00 per km. The split table shows 6:00 at 1 km, 12:00 at 2 km, 18:00 at 3 km, 24:00 at 4 km and 30:00 at 5 km — each mark exactly six minutes apart.
The same run in miles is 5 km ≈ 3.11 miles, so 30:00 ÷ 3.11 ≈ 9:37 per mile. Notice the mile pace is a different number for the same run — that is why keeping the unit consistent matters.
What the split table is for
The split table lists the cumulative time at each kilometre or mile of the distance. It turns a single pace into a plan: at each mark you know exactly where you should be, so on race day you can check the clock and know whether you are on, ahead of or behind pace.
It is the same arithmetic as the pace, applied to every whole unit of the distance. A 10K at 5:00/km shows 5:00, 10:00, 15:00, 20:00, 25:00, 30:00, 35:00, 40:00, 45:00 and 50:00 across the ten kilometres.
Splits turn a single pace into checkpoints you can act on. Instead of only seeing the clock at the start and the finish, you get a moving map of where you should be at kilometre four, kilometre eight, and the halfway mark. If you are ahead of the split at 5K, you have room to hold it; if you are behind, you know how much to make up and by where. That is the practical reason runners keep a table of them instead of just one pace number.
Negative splits and even pacing
A negative split means the second half of a run is faster than the first. It is a pacing strategy, not a different calculation: the calculator assumes one constant pace, so it cannot model a fast finish or a slow start — it assumes the whole run at a single even pace.
If you want to run a negative split you plan two paces yourself, using the same math for each half. The flat-course, constant-effort model is a good first estimate; real races vary with hills, heat and fatigue, so treat the number as a target to chase, not a guarantee.
Treadmill pace and why the same number moves
On a treadmill the belt does the pushing, so a pace that feels identical outdoors usually reads a touch faster on the machine. The same time and distance give the same arithmetic pace, but your body works less against wind, ground and hills, so the number is a slightly different thing to chase. If you are planning a road or trail race, treat a treadmill pace as a reference and leave a small margin for the conditions you will actually run in.
The calculator is deliberately condition-free: it adds no hills, no wind and no fatigue, and it has no idea whether you are on a treadmill or a road. That is what makes it a clean, repeatable yardstick. Use it to set the number, then use your own experience to adjust it for the course you are actually on.
When to plan with pace math instead of guessing
If you are setting a race goal, a training target or a time cutoff, working out the required pace beats an estimate. The whole thing is local arithmetic — no account, no app, works offline — so you can re-run it for any distance, any unit and any target time in seconds, which is exactly when the guesswork gets expensive.
Everything runs in this page: the division, the unit conversion and the split table are plain JavaScript reading your inputs directly. There is no leaderboard and no network, so a clean pace plan is yours to keep and re-run for any distance.
- Use it for goal times, training targets and time cutoffs.
- Keep the unit (km or mi) consistent across the whole run.
- Treat the splits as marks to check on race day, not a rigid script.
- Reload to reset; the numbers are never stored or sent.
Frequently asked questions
How do I calculate my running pace?
Divide your total time by your distance. A 30:00 5K is 30 ÷ 5 = 6:00 per km. The calculator does this in both directions — distance plus time gives the pace, and distance plus pace gives the finish time — in kilometres or miles.
How do I find my pace from a goal race time?
Enter the race distance and the time you want to finish in. The result is the per-km or per-mile pace to hold for the goal, and the split table shows the cumulative time at each distance mark so you can check in on the way.
What is a negative split?
Running the second half of a run faster than the first. It is a pacing strategy, not a different formula. The calculator assumes one even pace across the whole run, so to plan a negative split you set two paces yourself using the same time ÷ distance math for each half.
Why is my mile pace a different number than my kilometre pace?
Because they are different units for the same run. One kilometre is about 0.621 miles, so the per-mile time is larger. The calculator keeps kilometres and miles separate — pick one and every number, including the splits, is in that unit.
What is a good 5K pace?
That depends on your fitness and goal. The calculator does not grade you; it just converts between time and pace. A 5K in 30:00 is a 6:00/km pace, a 25:00 5K is 5:00/km, and a 35:00 5K is 7:00/km. Use it to translate the time you want into the pace you need.
Does the calculator account for hills or fatigue?
No. It is a flat-course, constant-effort model: pace = total time ÷ distance, one even pace for the whole run. Real races vary with terrain, heat and tiredness, so treat the number as a target to chase and adjust it with your own experience.
What distances does it support?
Kilometres and miles, with presets for 5K, 10K, half marathon and full marathon, plus any custom distance. The cumulative split table is built for whichever distance you choose.
Are my numbers stored or uploaded?
No. The division, unit conversion and split table are plain JavaScript running in this page, reading your inputs directly. It works with the network disconnected, and there is no leaderboard — the numbers never leave your device.