Running pace calculator

How running pace is calculated

Pace is time divided by distance: how many minutes it takes to cover one kilometre or one mile. The calculator rearranges that single relationship three ways, so you can solve for whichever number you do not already have.

The formula, three ways

Pace equals time divided by distance. Time equals pace multiplied by distance. Distance equals time divided by pace. Enter any two and the third follows directly. There is no approximation involved, it is pure arithmetic.

Worked example

Run 5 kilometres in 25 minutes and your pace is 25 divided by 5, which is 5:00 per kilometre. Flip it around: at a 5:00 per kilometre pace, 10 kilometres takes 10 times 5:00, which is 50:00. The same logic works in miles, just swap the distance unit and the pace changes with it. Solving for distance uses the third form of the same equation: run for 40 minutes at a 5:00 per kilometre pace and you cover 40 divided by 5, which is 8 kilometres.

Pace, speed and grade-adjusted pace: which to use

Runners talk in pace, minutes per kilometre or mile, rather than speed, kilometres or miles per hour, because pace maps directly onto splits and finish times. The two describe the same thing: speed in km/h is 60 divided by pace in minutes per kilometre, so a 5:00 per kilometre pace is 12.0 km/h.

Grade-adjusted pace

On a hilly route, GPS pace understates the effort of the climbs and overstates the effort of the descents. Grade-adjusted pace, used by some watches and platforms, converts uphill and downhill effort into the flat-ground pace it is equivalent to. This calculator works on a flat, even pace, so treat a hilly run's calculated splits as a guide rather than a target to hit metre for metre.

GPS versus track-measured pace

A GPS watch can drift off true distance, especially under tree cover, between tall buildings or through tunnels. A pace worked out from a certified race course or a measured track lap is more reliable than one from a watch reading alone.

Cadence and stride length

Two runners can hold the same pace very differently: a higher cadence with a shorter stride, or a lower cadence with a longer one. Neither is automatically more efficient, but a stride that is long for your cadence often shows up as overstriding, landing with the foot well ahead of the hips on each step. The stride length calculator breaks a given pace down into cadence and stride length if you want to look at that side of it separately.

Track pace versus road pace

A pace held comfortably on a 400 metre track does not always transfer directly to the road. A track offers a perfectly flat, consistent surface with no traffic or camber to navigate, so many runners find their honest track pace is a touch faster than the same effort feels on an uneven road surface. Road camber, forcing one foot slightly lower than the other on a sloped shoulder, and frequent turns, kerbs and traffic stops all add small amounts of extra effort a track never asks for. Treat a track time trial as a slightly optimistic input for road pacing, and a road time trial as the more directly transferable number for race day.

Training paces at a glance

How common training and race paces compare in both units, alongside the speed they represent. The 5:00 per kilometre row is highlighted as a widely used benchmark pace for steady recreational training, and a reasonable middle point to check your own numbers against.

Even splits, negative splits and why pacing strategy matters

How you distribute effort across a race matters almost as much as your fitness on the day. Research on pacing consistently favours an even or slightly negative split, running the second half no slower, and ideally a little faster, than the first, over starting fast and fading.

Why fast starts backfire

Starting faster than goal pace burns through glycogen and anaerobic reserves early, and the fade that follows in the second half almost always costs more time than the early speed gained. This shows up most clearly over the marathon, where a positive split of several minutes is common among runners who go out too hard.

Building your own split plan

Use this calculator to work out your target overall pace, then hold it evenly, or shade the first few kilometres 2 to 3 seconds per kilometre slower than goal pace to bank a controlled negative split without the early-race risk.

Pacing by race distance

The right split strategy changes with the distance. A 5K rewards a genuinely even effort from gun to line, since the race is short enough that a slow start is difficult to make up and a fast start is punished immediately by rising lactate. A 10K has slightly more room for a controlled build, holding back marginally through the first two kilometres before settling into goal pace. Over a half marathon, many experienced runners deliberately run the first 5K a few seconds per kilometre slower than target pace, banking energy for a stronger second half. The marathon rewards patience more than any other common distance: the first 10 kilometres should feel almost too easy, because whatever pace mistake is made early compounds heavily once glycogen stores run low past 30 kilometres.

Pace and heart rate: reading effort two ways

Pace tells you what speed you are holding. Heart rate tells you how hard your body is working to hold it. On a good day, in cool weather, on fresh legs, the two line up closely with your usual training paces.

Why the same pace can feel different

Heat, humidity, poor sleep and fatigue carried over from a previous session all push heart rate higher at a given pace. On those days, running to a fixed pace target can push you into a harder training zone than intended, while running to a heart rate target keeps the physiological effort consistent even as the pace naturally drops.

Combining the two

Use pace for racing, when the clock is what matters and conditions on the day are whatever they are. Use heart rate, worked out from the max heart rate calculator and heart rate zone calculator, for easy and steady training runs, where a consistent physiological effort matters more than hitting an exact split.

Cardiac drift over long runs

Even at a genuinely steady pace, heart rate tends to climb gradually over a long run, a pattern known as cardiac drift. Rising core temperature, fluid loss and accumulating fatigue all push heart rate upward even though the pace on the watch has not changed. A well paced long run typically shows some drift by the final third, and a large amount of drift, heart rate climbing sharply while pace holds steady, is often an early sign of dehydration or heat stress rather than fitness. Tracking both numbers together on a long effort gives a clearer picture than either one on its own.

What your pace means across common race distances

Once you know your pace, splitting a race into checkpoints is multiplication. The table below shows finish times at a handful of common training paces, so you can see where a given pace lands you across the standard distances without doing the maths mid-run. The calculator above builds the same table live from whatever pace you enter, distance by distance.

A checkpoint plan is only as useful as your ability to check it against the clock on the day. Writing splits on a wristband, or setting quiet watch alerts at each checkpoint distance, turns the table into something usable mid-race rather than a number you only think about afterwards. For a first attempt at a distance, err on the side of writing more checkpoints rather than fewer, every 5 kilometres at minimum, since an early warning that you are drifting off pace is far more useful than a single number at the finish line telling you it already happened.

How to use your pace

A calculated pace is only useful once it turns into a decision: what speed to hold on a treadmill, what split to hit at 5 kilometres, or what effort a coach should prescribe for an interval session.

Setting a treadmill speed

Treadmills display speed, not pace. Convert with speed in km/h equals 60 divided by pace in minutes per kilometre, or read it straight off the stats shown above for whatever pace you enter.

Pacing a goal race

Work backwards from your goal time: enter the distance and target time, solve for pace, and that is the number to hold, checkpoint by checkpoint, on race day. The race time predictor is the natural next step if you are not yet sure what goal time is realistic.

Interval and tempo paces

Training paces are usually set relative to race pace, a few seconds per kilometre either side. Once you know your 5K or 10K pace here, most interval prescriptions become simple arithmetic instead of guesswork.

Comparing pace across watches and apps

Garmin, Strava, a phone app and a track all measure distance slightly differently, so the same run can show a handful of different average paces depending on where you read it. Pick one source as your primary record for a training block, so week-to-week comparisons are measuring a change in fitness rather than a change in measurement method.

Adjusting for heat and altitude

Pace calculated on a cool, low-altitude course does not transfer directly to a hot day or a race at elevation. Heat forces the body to divert blood flow to the skin for cooling, which raises heart rate and perceived effort at a given pace, so a sensible adjustment on a hot day is to accept a slower pace for the same effort rather than chase the number calculated in training. Altitude reduces the oxygen available per breath, which similarly slows the pace a given effort can sustain, more noticeably the higher above sea level and the longer the race. Neither factor changes the arithmetic this calculator does, only what pace is realistic to type into it on the day.

Common mistakes

Confusing pace with speed. A lower pace number is faster, a higher speed number is faster. Mixing the two up when comparing sessions or watches leads to real training errors.

Ignoring watch drift. GPS distance can run long or short under tree cover, downtown or through tunnels, which quietly skews a pace calculated from a watch reading rather than a measured course.

Setting splits from an ambitious pace rather than a proven one. Base race splits on a pace you have actually held for at least part of a recent effort, not a hoped-for personal best.

Forgetting elevation. The same pace on a hilly course costs more effort than on the flat, so a flat-course split plan needs adjusting on a hilly route.

Mixing units mid-plan. Switching between min/km and min/mile partway through a training block, without converting properly, is a common source of workouts that feel wrong for no clear reason.

Treating one pace as fixed for a whole training block. Pace at a given effort improves as fitness improves, so a training pace set two months ago is probably a little easier than it used to be.

Ignoring wind. A steady headwind can cost several seconds per kilometre for the same effort, and it does not average out against the tailwind on the way back, since the tailwind rarely returns as much time as the headwind takes. A pace plan on an exposed, out-and-back course should build in a slower split for the headwind leg rather than assuming the two cancel out.

How coaches use a running pace calculator

For a running coach, pace is the currency of every session: an easy run, a threshold block, an interval set are all built around it. Working out several paces by hand for every client, every few weeks as fitness changes, adds up fast.

A workable routine: recalculate key paces from a recent time trial or race every 4 to 6 weeks, write sessions around those paces rather than a single number that ages quickly, and review splits, not just an average pace, to see where a session actually broke down.

Scraler lets you build and assign running sessions with target paces per client, and track what they actually held against what was planned, rather than relying on a client's own memory of how a session went. See workout programming, or read how hybrid personal training blends structured running work with coached strength sessions.

Pace targets also need revisiting whenever a client's training phase changes, not just on a fixed schedule. A client moving from a base-building block into race-specific work usually needs faster paces recalculated even between routine check-ins, since a base phase is deliberately conservative and a race-specific phase is not. Tracking pace against perceived effort, not only against the clock, also flags a client who is technically hitting a prescribed pace but working far harder than intended to do it, a pattern that a pace number alone will not reveal.