// Cardio Calculators

10K Pace Calculator

Enter the 10K time you're chasing. Back comes the pace it demands, and where the clock should read at each marker.

Your details

Your result

Pace to hold
5:30/km
Pace per mile
8:51/mi
Speed
10.91km/h
Elapsed at 1 km
5:30
Elapsed at 2.5 km
13:45
Elapsed at 5 km
27:30
Elapsed at 7.5 km
41:15
Elapsed at Finish
55:00
  • The splits are an even pace, which is the arithmetic and not a prediction. Almost nobody runs a race evenly — the point of the table is that you can see, at each marker, how far ahead or behind an even effort you already are.
  • Ten seconds per kilometre is a whole minute and forty seconds over ten of them. Small early drift is the usual reason a goal time is missed, and it is invisible without a checkpoint to compare against.

Estimates are for general guidance only and are not medical advice. For a personalised plan, book a free guided tour at RPM Gym.

What your result means

The headline is what your goal costs per kilometre, not a forecast of what you'll run. Chasing 55 minutes means 5:30 per kilometre, which is 8:51 per mile and 10.91 km/h. Nothing about you went into that. It is 55 divided by 10, and a first-timer and a club runner get the same number.

The rows underneath are where that pace has to have put you. At 5:30/km the clock reads 5:30 at the first kilometre, 13:45 at 2.5 km, 27:30 at halfway, 41:15 at 7.5 km and 55:00 at the line. Those are the figures to check against the course signs while there is still road left to do something with.

Four checkpoints and a finish, not ten. A ten-row table stops getting read somewhere around the fourth kilometre, and a single kilometre on its own is noisy: one slow one usually means a bend, a hill or a water station rather than a problem with the pace. The 2.5 km reading catches a fast start early. The 5 km reading is the last one with half the race still in front of it.

What the table won't tell you is whether being twenty seconds up at 2.5 km is good news. It tells you that you are twenty seconds up. That is the whole service: a gap you can feel becomes a gap you can count, and the decision about it stays yours.

How it is calculated

Constant pace over a fixed 10 km, with elapsed time at four checkpoints

Pace (seconds per km) = goal time (minutes) × 60 ÷ 10 Pace per mile = pace per km × 1.609344 Speed (km/h) = 3600 ÷ pace (seconds per km) Elapsed at a checkpoint = pace (seconds per km) × checkpoint distance (km) Checkpoints: 1 km, 2.5 km, 5 km, 7.5 km, and the finish at 10 km

What it assumes

  • The pace is held from the gun to the line. No fast start, no headwind, no rise, no finishing sprint — the arithmetic carries no term for any of them.
  • The distance is exactly 10 km, measured the way the course was measured. The table is keyed to the official markers rather than to whatever your watch has decided you covered.
  • Every row is rounded to the nearest second. A 47:30 goal comes back as 4:45/km with 11:53 at 2.5 km, which is 11:52.5 rounded up.
  • There is one field and it is the goal. The tool never asks what you have run before, so it has no basis for an opinion on whether the goal is within reach, and it does not offer one.

Units and rounding

  • The goal goes in as decimal minutes rather than minutes and seconds: divide the seconds by 60 and add them on, so 47:30 is 47.5 and 52:15 is 52.25.
  • The field accepts 25 to 150 minutes. That is the range of the arithmetic, not a comment on anybody's running.
  • Pace comes back in minutes and seconds per kilometre and per mile; speed comes back in km/h. The mile row uses the international mile, 1.609344 km exactly.
  • The checkpoint column is elapsed time from the start, not the time taken for that segment. 41:15 at 7.5 km is what the clock shows as you go past, not what the last 2.5 km cost you.

Worked example

A runner going for 55:00 who comes through 2.5 km with the clock on 13:15.

  1. Goal 55 in the field: 5:30 per kilometre, 8:51 per mile, 10.91 km/h.
  2. The checkpoints come back 5:30, 13:45, 27:30, 41:15, 55:00.
  3. The clock says 13:15 at 2.5 km, so the first quarter went 30 seconds quicker than the goal asked for.
  4. Put 53 in the field instead: 5:18 per kilometre, and 13:15 at 2.5 km. That is the pace actually being run.

Thirty seconds up at 2.5 km is 5:18/km, and 5:18 held to the line is 53:00, two minutes inside the goal. The table has no view on whether that is a good race or the first quarter of a bad one. It converts a clock reading into a pace, and the runner spends the remaining 7.5 km deciding what to do with that.

Limitations

  • This is arithmetic on one number. There is no fatigue model in it, no read on your training, and no way for the page to know whether 55 minutes is a target or a wish.
  • Even splits are what the division produces, not a recommendation. Actual fields do not run them: across 16,315 finishers of the Oslo 10 km between 2015 and 2018, the second half came in slower than the first by about 3.4% for men and 4.0% for women.
  • Nor is an even split what the fastest races look like. In the men's 10,000 m world records analysed by Tucker and colleagues, the first and last kilometres were quicker than the ones in the middle. Neither finding makes even pacing right or wrong. Both make it a reference line rather than a plan.
  • No adjustment for heat, humidity, wind, gradient or surface. A table generated in a browser has no contact with a July morning in Abu Dhabi.
  • Working out a 10K time from a 5K result is a different job needing a different model, and this page does not attempt it. A goal goes in, a pace comes out, and that is the extent of it.
  • The finish row restates your goal. That is the tool being consistent with what you typed rather than a result — worth saying out loud, because this page used to report the distance baked into its own URL as though it had calculated it.

What to do next

  • Get the four checkpoint times somewhere you will actually look: a wrist, a watch face, a strip of tape on the back of your hand. A table you plan to remember is a table you will remember wrong at 7 km.
  • Read them off the course markers rather than your watch's auto-lap. The two drift apart over 10 km, and the finish clock only agrees with one of them.
  • Move the goal in half-minute steps and watch the per-kilometre figure move with it. Five minutes off a 10K goal is thirty seconds a kilometre, which is a larger request than five minutes sounds.
  • Enter a time you have genuinely run alongside the one you want, and compare the two tables. The distance between them is the honest size of the project.
  • Rehearse the 2.5 km checkpoint in training rather than the whole distance. A quarter of the race is the cheapest way to find out how you start.

Sources

Related calculators
View all calculators →
// Frequently Asked

Questions, answered.

What pace do I need for a 50-minute 10K?

5:00 per kilometre, which is 8:03 per mile and a flat 12 km/h. The checkpoints land on 5:00, 12:30, 25:00, 37:30 and 50:00 — every one of them a whole or half minute, which makes it the one goal time you can carry in your head without writing anything down.

How do I enter 47 minutes and 30 seconds?

As 47.5. The field takes decimal minutes, so 47:30 is 47.5, 52:15 is 52.25 and 58:45 is 58.75. Enter 47.5 and the pace comes back at 4:45/km, with checkpoints at 4:45, 11:53, 23:45, 35:38 and 47:30.

Are the numbers in the table splits or elapsed times?

Elapsed, all of them, counted from the start. 13:45 at 2.5 km is what a race clock reads as you pass the sign. If you want segment times instead, subtract each row from the one below it — at an even pace they all come out identical, which is exactly why the elapsed column is the more useful of the two to carry.

Should I run even splits in a 10K?

This page cannot tell you, and it deliberately does not try. What is on record is that most people do not: that 16,000-runner field in Oslo averaged a slower second half, and the men's 10,000 m world records went quick at both ends and steadier through the middle. Even pacing is the arithmetic the table is built from, so read it as the line you are measuring against rather than the instruction.

My watch beeps a kilometre before the sign does. Which one do I trust?

The sign, when the table is what you are checking against. These elapsed times are keyed to the measured course, so comparing them with a watch that has quietly added a hundred metres will tell you that you are behind when you are not. Watch for pace, markers for position.

Why does the finish row just show my goal time back to me?

Because that is the honest output. You typed the finish; the tool worked out what it demands and completes the column with it. Every row above the last one is new information, and the last one is a checksum. A version of this page once presented the 10 km in its own URL as a calculated result, and that is the kind of row worth being explicit about.

Can I use this for a 10K that isn't a race?

Yes, and it probably earns its keep there. A training run has no official clock, no signs and nobody to pull you along, which is where pace drifts hardest and least visibly. Four checkpoint times on a watch face is the cheapest way to find out how steady your steady 10K really is.

Ten kilometres is a long way to find out the number was optimistic.

Goal paces get set from what a runner wants and tested for the first time on race morning, which is a poor order to do it in. Book a free guided tour at RPM Gym in Al Manhal and bring the times you have actually run.

Book Free Tour