Finish Time
Calculator

How finish time is calculated

A finish time is just your pace multiplied by the race distance. Hold 5:30 per kilometer for a 10K and you'll finish in 5:30 × 10 = 55:00. The calculator above does this instantly for any pace and distance, with one-tap presets for the 5K, 10K, half marathon (21.0975 km) and marathon (42.195 km). It assumes you run an even pace from start to finish — the ideal most race plans are built around.

Finish times at common paces

What a few steady paces produce across the classic distances (even splits):

Pace	5K	10K	Half	Marathon
5:00 /km	25:00	50:00	1:45:29	3:30:59
5:30 /km	27:30	55:00	1:56:02	3:52:04
6:00 /km	30:00	1:00:00	2:06:35	4:13:10
6:30 /km	32:30	1:05:00	2:17:08	4:34:16

Why your real time may differ

Pure pace-times-distance math is perfect for planning, but real races rarely hold a flat pace to the finish. Fatigue, fuelling, heat, hills and crowded starts all nudge your pace slower as the distance grows — the effect is small in a 5K and significant in a marathon. So treat the calculator's number as your even-effort target, then expect a little fade unless you're well trained and well paced.

Predicting across distances: the Riegel formula

If you want to predict your time at a new distance from a recent race, flat pace isn't enough — you need something that builds in the natural slowdown. The most popular tool for this is the Riegel formula:

T2 = T1 × (D2 ÷ D1)^1.06

Here T1 is your known time over distance D1, and T2 is the predicted time over the new distance D2. The exponent 1.06 captures the fact that you can't hold your 5K pace for a marathon. For instance, a 25:00 5K predicts a marathon a good deal slower than five times 25:00, because the formula accounts for the fade over 42 km. It's an estimate, not a promise — training specificity matters enormously for long races — but it's a far better cross-distance predictor than flat pace.

Turning a finish time into a pacing plan

Once you've set a target finish time, work backward to your per-kilometer or per-mile splits and commit them to memory or your watch. Even-split running — hitting roughly the same time at each marker — is the most reliable way to reach a goal, because it stops you from spending energy you'll need later. Many runners aim for slightly negative splits, running the back half a touch faster, which tends to produce both better times and a stronger finish.

Race-day factors to plan for

A finish-time target is only as good as the conditions you run it in. Heat and humidity can slow you noticeably, so adjust expectations on a hot day. Elevation and hills change effort even when pace looks steady. Crowded starts can cost time in the first kilometer — don't panic and overcompensate. And fuelling and hydration become decisive past about 90 minutes of effort. Build a little buffer into your target for anything you can't control.

Pacing strategy by race distance

The right way to use a target time changes with the distance. In a 5K, the margin for error is small — go out a few seconds too fast per kilometer and you'll feel it by the third. In a 10K, settle into goal pace quickly and hold it; the middle kilometers are where focus slips. The half marathon rewards patience: bank nothing early, run the first few kilometers slightly conservative, and you'll have something left for the last 5K. The marathon is the most punishing of all for poor pacing — the difference between an even run and a fast start is often the difference between a strong finish and "hitting the wall."

How to set a realistic goal time

The best goal times come from recent evidence, not hope. Take a race or hard effort you've done lately, find your pace, and use a cross-distance predictor like the Riegel formula to estimate the new distance. Then sanity-check it against your training: have you actually run workouts at the required pace? A goal that's a small stretch beyond your current fitness is motivating; one that's wildly optimistic just sets up a blow-up. Adjust for the course and conditions, too — a hilly or hot race deserves a softer target.

Why marathons fade: the wall

Long races slow down for a physiological reason, not just fatigue. Your body stores only a limited amount of carbohydrate (glycogen), and around the 30 km mark of a marathon many runners begin to run low — the infamous "wall." Pace drops sharply, and no amount of willpower fully compensates. This is why marathon pacing and fuelling go hand in hand: an even, slightly conservative pace plus regular carbohydrate intake delays the wall, while a fast start burns through glycogen early and brings it on sooner. It's also why the Riegel exponent exists — the slowdown over distance is real and predictable.

How to run negative splits

Negative splitting — running the second half of a race faster than the first — sounds simple but takes discipline. The method is to deliberately start a touch slower than your goal average pace, hold steady through the middle, and gradually lift the effort over the closing stretch. In a marathon that might mean running the first few kilometers 5–10 seconds per kilometer slower than target; in a 5K, just easing off the throttle for the opening 60–90 seconds. It feels too conservative early — that's the point. The runners passing you in the first kilometer are often the ones you'll reel back in over the last. Plan your splits from your goal time, then run the first ones with restraint.

Using the whole pace toolkit

This calculator answers "how long will it take at this pace?" To answer the reverse — "what pace do I need for a goal time?" — use the 5K pace calculator for 5K goals or the running pace calculator to find your current pace from a recent run. And to switch any pace between units, the pace converter turns min/km into min/mile and back.