You have a pace in mind, and now you want to know what time that gives you at the finish line. The maths is short. To calculate your finish time from running pace, multiply the pace for one kilometre or mile by the number of kilometres or miles in the race, then convert the result into hours, minutes and seconds.
The multiplication is rarely where people go wrong. The trouble starts with unit handling, the odd distance of a half marathon, and the gap between a pace you can hold for 5K and one you can hold for 42 kilometres. This guide covers all three.
The Finish Time Formula: Pace Multiplied by Distance
Finish time equals pace multiplied by distance. If your pace is 6:00 per kilometre and the race is 10 km, your finish time is 60 minutes. The only rule is that the units must match: minutes per kilometre goes with kilometres, and minutes per mile goes with miles.
Pace is simply time per unit of distance. When you multiply it by the number of units, the distance cancels and time is left. That is why the formula works for any race, from a 3 km fun run to an ultra.
Written out, it looks like this:
Finish time = pace per unit × number of units
The formula assumes you hold the same pace the whole way. That assumption matters more than the arithmetic, and I come back to it further down.
How to Convert Pace Into Seconds Before You Multiply
Convert the pace into seconds first, multiply, then convert the total back into hours, minutes and seconds. This avoids the most common error in pace maths, which is treating 5:30 as 5.30 minutes. A pace of 5:30 means 5 minutes and 30 seconds, which is 5.5 minutes or 330 seconds.
Here is the full method with a 10K at 5:42 per kilometre:
- Convert the pace: 5 × 60 + 42 = 342 seconds per km.
- Multiply by the distance: 342 × 10 = 3,420 seconds.
- Divide by 60 to get minutes: 3,420 ÷ 60 = 57 minutes.
Your 10K finish time is 57:00.
When the total passes an hour, divide by 3,600 for the hours, then convert the remainder into minutes and seconds. A half marathon at 5:30 per km works like this:
- Pace in seconds: 5 × 60 + 30 = 330.
- Multiply by 21.0975 km: 330 × 21.0975 = 6,962 seconds.
- Hours: 6,962 ÷ 3,600 = 1 hour, with 3,362 seconds left.
- Minutes: 3,362 ÷ 60 = 56 minutes, with 2 seconds left.
The finish time is 1:56:02.
I always work in seconds for this reason. Decimal minutes invite mistakes, and seconds keep every step as whole-number multiplication.
Standard Race Distances to Use in the Calculation
Use the exact race distances: 5 km, 10 km, 21.0975 km for the half marathon and 42.195 km for the marathon. In miles, those are 3.107, 6.214, 13.109 and 26.219. Rounded distances like 21 km or 42 km make the projected time look faster than it will be.
The error is bigger than it looks. At 5:00 per km, the marathon is 42.195 km, and the extra 0.195 km is worth about 58 seconds. Calling it 42 km would make your projected finish time almost a minute too optimistic before a single step of fatigue is considered.
| Race | Kilometres | Miles |
|---|---|---|
| 5K | 5 | 3.107 |
| 10K | 10 | 6.214 |
| Half marathon | 21.0975 | 13.109 |
| Marathon | 42.195 | 26.219 |
Most races also add a small amount of real-world distance, which I cover in the section on watch accuracy.
How to Calculate Finish Time From Pace Per Mile
The method is identical with miles. Convert the mile pace into seconds, multiply by the number of miles, and convert the total back. A marathon at 9:30 per mile takes 570 seconds per mile, and 570 × 26.219 gives about 14,945 seconds, which is 4:09:05.
A 10K at 8:45 per mile follows the same steps. The pace is 525 seconds per mile, the distance is 6.214 miles, and 525 × 6.214 is about 3,262 seconds. That is a finish time of 54:22.
If your watch shows miles but the race is in kilometres, convert the pace instead of the distance:
- Mile pace to kilometre pace: divide the mile pace in seconds by 1.609. A 9:00 mile (540 seconds) is about 5:36 per km.
- Kilometre pace to mile pace: multiply the kilometre pace in seconds by 1.609. A 5:00 km (300 seconds) is about 8:03 per mile.
Convert once, at the pace stage, and then use only one unit for the rest of the calculation.
Finish Time Table for Common Paces Per Kilometre
The table below shows projected finish times for six paces across the four standard distances. Find your pace in the left column and read across to the race you are entering. If you think in miles, convert your pace to kilometres first using the method above.
| Pace per km | 5K | 10K | Half marathon | Marathon |
|---|---|---|---|---|
| 4:30 | 22:30 | 45:00 | 1:34:56 | 3:09:53 |
| 5:00 | 25:00 | 50:00 | 1:45:29 | 3:30:59 |
| 5:30 | 27:30 | 55:00 | 1:56:02 | 3:52:04 |
| 6:00 | 30:00 | 1:00:00 | 2:06:35 | 4:13:10 |
| 6:30 | 32:30 | 1:05:00 | 2:17:08 | 4:34:16 |
| 7:00 | 35:00 | 1:10:00 | 2:27:41 | 4:55:22 |
Every number here assumes a perfectly even pace on a flat course. Treat the table as a map of what a pace would produce, not a prediction of what you will run.
How to Work Out Finish Time From Treadmill Speed
Treadmills show speed in km/h or mph, so convert the speed into a pace first. Divide 60 by the speed in km/h to get minutes per kilometre. At 10 km/h, 60 ÷ 10 = 6, so the pace is 6:00 per km. At 12 km/h, the pace is 5:00 per km.
You can also skip the pace step. Time equals distance divided by speed, so 10 km at 10 km/h takes exactly one hour, and 5 km at 12 km/h takes 25 minutes.
Speeds that do not divide evenly need one extra conversion. At 11 km/h, 60 ÷ 11 is 5.4545 minutes. The decimal part, 0.4545, multiplied by 60 gives about 27 seconds, so the pace is roughly 5:27 per km.
One practical note. Treadmills can drift out of calibration, and many runners find that a given speed feels easier indoors than the same pace outside. If you are using a treadmill session to project a race time, treat the result with some caution.
Why a Finish Time From Running Pace Is a Best-Case Estimate
A finish time from running pace assumes you hold exactly that pace from the first step to the last. Over short distances that is close to true. Over a half marathon or marathon it almost never is, so the calculated time works better as a ceiling than as a forecast.
Several things pull the real number away from the maths:
- Fatigue. Pace tends to drift slower as the distance grows, and the effect increases the longer the race is.
- Course and weather. Hills, wind, heat and crowded early kilometres all cost time that a flat-course formula ignores.
- Aid stations. Slowing to drink adds seconds that no pace calculation includes.
- Watch distance. GPS watches usually record slightly more than the official distance because you run wider lines than the measured course, especially around corners.
The last point deserves a closer look. Say your watch reads 5.1 km when you cross the line of a 5K. The watch divides your time by 5.1, so the pace it shows looks faster than the pace the race will record, which divides by 5. If you multiply that watch pace by the official 5 km, you get a time that is a little too fast.
For anything past 10K, I choose the pace from a recent race or a hard training effort at a similar distance, not from a 5K personal best. A runner who holds 5:00 per km for 25 minutes is not usually a 3:30:59 marathoner. The honest gap between those two numbers is the point of this section.
How to Use Splits to Check Your Finish Time During a Race
Splits turn the finish time into a series of checkpoints. Multiply your target pace by each checkpoint distance, and you know exactly what the clock should read at that point. If you are on pace, the clock matches. If you are behind, you can see by how much.
For a 10K at 5:30 per km, the checkpoints look like this:
- 5 km: 330 × 5 = 1,650 seconds, which is 27:30.
- 8 km: 330 × 8 = 2,640 seconds, which is 44:00.
- 10 km: 330 × 10 = 3,300 seconds, which is 55:00.
Some runners write the checkpoints on a wristband or note them on their phone before the start. It takes two minutes of preparation and removes any need for mental arithmetic mid-race.
Two details are worth knowing about official results. Large races often publish both gun time and chip time. Gun time starts when the race begins, while chip time starts when you cross the start mat. If you start near the back of a big field, the difference can be a minute or more. Your pace-based finish time lines up with chip time, because chip time measures the distance you actually ran.
Splits also help when you plan to run the second half slightly faster than the first. That approach is called a negative split. Calculate the target for each half separately, then add the two halves to confirm the total matches your goal.
Calculate Finish Time From Pace With a Running Pace Calculator
A running pace calculator performs the same multiplication instantly and handles the unit conversions for you. You enter a pace and a distance, and it returns the finish time. The running pace calculator is useful when you want to compare several paces quickly or check a number you worked out by hand.
I still suggest doing the first few calculations manually. Knowing that 5:30 per km over 10 km is 55:00 gives you a sanity check, and you can spot a typo in a calculator input much faster.
Custom distances are where a calculator saves the most effort. Local races are often 8K, 12K or 15K, and no standard table covers them. The formula does not change: a 15K at 5:20 per km is 320 × 15 = 4,800 seconds, or 1:20:00. A pace calculator for race finish time just removes the conversion step from the end.
Common Mistakes When You Calculate Finish Time From Pace
Most errors in a finish time from pace calculation come from a small set of habits. Knowing them in advance makes the result easier to trust.
- Reading 5:30 as 5.30. Minutes and seconds are not decimals. Convert to seconds before you multiply.
- Using rounded distances. Rounding the half marathon to 21 km or the marathon to 42 km hides about 30 to 60 seconds, depending on your pace.
- Mixing units. A pace per mile multiplied by kilometres produces nonsense. Match the pace unit to the distance unit.
- Using a 5K pace for a marathon. Short-race pace is not a pace you can hold for hours, so the result will look better than reality.
- Trusting watch pace on a twisty course. Extra distance on the watch makes the pace appear faster than the official figure.
If a calculated time looks too good, one of these five is almost always the reason.
How to Pick a Target Pace by Working Backwards From a Goal Time
To find the pace a goal requires, divide the goal time in seconds by the distance. This is the same formula rearranged: pace = finish time ÷ distance. It answers the question many runners start with, which is what pace they need to hold to hit a certain time.
Take a sub-2:00 half marathon. The goal is 7,200 seconds, and 7,200 ÷ 21.0975 is about 341 seconds per km, or 5:41 per km. A sub-4:00 marathon is 14,400 seconds, and 14,400 ÷ 42.195 gives the same 5:41 per km. In miles, a four-hour marathon needs 14,400 ÷ 26.219, or about 549 seconds, which is roughly 9:09 per mile.
Once you have the required pace, compare it with what you have actually run. If the pace is faster than anything you have held for that distance, the goal needs more training before race day, or the target needs adjusting. If it sits a little slower than your recent race pace, the goal is realistic.
Quick Method to Estimate Finish Time From Running Pace
The fastest reliable way to estimate your finish time from running pace takes three steps. Convert your pace into seconds, multiply by the exact race distance, and convert the total back into hours, minutes and seconds.
For example, a pace of 6:15 per km over a 5K gives 375 seconds per km, then 375 × 5 = 1,875 seconds, which is a finish time of 31:15.
Then ask whether the pace is one you can genuinely hold for the whole race. For short races the answer is often yes. For longer ones, treat the figure as an upper limit and expect the real time to land a little above it. That combination of accurate arithmetic and honest judgement is what turns a pace into a useful race plan.
