Pace turns a finish time into a comparable rate
Running pace is the time required to cover one unit of distance. It is commonly written as minutes and seconds per kilometre or per mile. Because it normalizes a run to one unit, pace makes efforts over different distances easier to compare.
Speed describes the inverse relationship: distance covered per unit of time. A faster runner has a smaller minutes-per-kilometre number and a larger kilometres-per-hour number.
This calculator begins with a measured distance and elapsed time. It reports average pace, not the second-by-second changes that occurred during the activity.
The pace formula
Convert the full duration to seconds, then divide by distance:
pace = total time ÷ distance
A 5 km run completed in 25 minutes contains 1,500 seconds. Dividing by 5 gives 300 seconds per kilometre, formatted as 5:00/km.
The same run is approximately 3.106856 miles. Dividing 1,500 seconds by that distance gives about 482.8 seconds, formatted as 8:03 per mile after rounding.
Keeping seconds during the calculation avoids mistakes caused by treating clock notation as a decimal. A pace of 5:30 means five minutes thirty seconds, which is 5.5 decimal minutes—not 5.30 minutes.
Pace and speed
Speed divides distance by time:
speed = distance ÷ time
For pace in seconds per kilometre, speed in kilometres per hour is 3,600 divided by the pace. A 300-second kilometre gives 3,600 ÷ 300 = 12 km/h.
A pace of 6:00/km equals 10 km/h. A pace of 4:00/km equals 15 km/h. The relationship is not linear in the displayed pace: reducing 6:00 to 5:00 is a larger speed increase than reducing 5:00 to 4:00 in absolute kilometres per hour.
Treadmills often display speed, while training plans often use pace. Conversion helps match the plan to the machine, but treadmill calibration and outdoor conditions can make the effort differ.
Kilometres and miles
The international mile is exactly 1.609344 kilometres. Therefore:
seconds per mile = seconds per kilometre × 1.609344
seconds per kilometre = seconds per mile ÷ 1.609344
A 5:00/km pace is 300 × 1.609344 = 482.8032 seconds per mile, about 8:03/mile. An 8:00/mile pace is 480 ÷ 1.609344 = 298.258 seconds per kilometre, about 4:58/km.
Do not multiply the displayed minutes and seconds separately. Convert the full pace to seconds, apply the distance factor, then convert back to clock notation.
Standard road-race distances
A 5K is 5 kilometres. A 10K is 10 kilometres. The half marathon is 21.0975 kilometres, and the marathon is 42.195 kilometres under World Athletics rules.
Multiplying average pace by one of these distances gives the time required if that pace remained constant. For example, 5:00/km produces 25:00 for 5K, 50:00 for 10K, 1:45:29 for a half marathon, and 3:30:59 for a marathon after rounding.
Those are equivalent times, not predictions. The physiological and practical difficulty rises with duration. Few runners can extend a short-race pace unchanged to a much longer race.
Average pace versus split pace
Average pace uses total time divided by total distance. Split pace applies the same calculation to a segment, commonly each kilometre or mile.
Two runs can have the same average but very different execution. One may be steady; another may begin fast, slow sharply, and finish fast. Splits reveal that pattern.
GPS watches may show “current,” “lap,” and “average” pace. Current pace is calculated over a short window and moves quickly. Lap pace averages the current split. Average pace covers the activity so far. The latter two are usually more stable because position errors form a smaller share of the measured distance.
Elapsed time and moving time
Elapsed time runs from start to finish, including stops. Moving time attempts to exclude periods when the device decides the runner was stationary. Race clocks use elapsed time, apart from the distinction between official gun time and an individual chip time.
Auto-pause thresholds differ between devices and settings. Traffic lights, aid stations, slow climbs, and GPS drift can be included by one device and excluded by another. Comparing moving pace across platforms can therefore compare algorithms as much as running.
Use elapsed time for an outcome that includes all interruptions. Use moving time when the question is specifically about pace while moving, and record that choice.
GPS distance limitations
A GPS watch estimates a path from a series of positions. Buildings, trees, terrain, atmospheric conditions, sampling frequency, and smoothing affect the result. Small errors in each point can shorten corners or add side-to-side noise.
An officially certified road course is measured according to governing procedures and includes a short-course prevention factor. A runner’s device can show more or less than the advertised distance without proving that the course is wrong.
Pace based on recorded GPS distance inherits that distance error. On a track, known lap distance and manual splits may offer a better check, though runners rarely follow a mathematically perfect line.
Equivalent-time examples
A runner completes 10 km in 52:30. Total time is 3,150 seconds, so pace is 315 seconds or 5:15/km. Per-mile pace is about 8:27. Average speed is approximately 11.43 km/h.
At exactly that pace, a half marathon takes about 1:50:46. That does not account for fatigue; it only scales the rate across 21.0975 km.
Another runner covers 3 miles in 24 minutes. Pace is 8:00/mile. The equivalent kilometre pace is about 4:58/km, and speed is 7.5 mph or approximately 12.07 km/h.
If a 400 m track lap takes 90 seconds, the equivalent pace is 225 seconds per kilometre, or 3:45/km. Ten laps at the same split cover 4 km in 15 minutes.
Why longer-distance prediction needs a model
Performance does not scale linearly because sustainable intensity declines with duration. A 20-minute effort relies on a different balance of aerobic capacity, threshold, economy, fueling, and fatigue resistance than a three-hour effort.
Prediction formulas often use a recent race and apply an exponent so time grows slightly faster than distance. Even those models assume comparable training, course, weather, health, and effort. They describe a population pattern rather than a promise to an individual.
The constant-pace values on this page deliberately avoid claiming prediction. They answer “how long would this pace take?” rather than “how fast will I race?”
Terrain, weather, and elevation
Uphills usually slow pace at the same effort, while downhills may increase speed until steepness or muscle damage offsets the benefit. Trail surfaces, turns, crowding, and altitude can add further cost.
Heat and humidity increase thermoregulatory strain. Wind changes air resistance and can affect exposed courses. Cold, rain, and poor footing can also change performance. Comparing raw pace without context can make a well-managed difficult run look worse than an easier one.
Effort measures such as heart rate and perceived exertion add context but have their own delays and uncertainties. Training decisions should consider the combination rather than one number.
Pacing a race
Even pacing aims to keep splits close. Negative splitting means the second portion is faster than the first. Positive splitting means the runner slows.
The best strategy depends on course shape, conditions, competition, and the athlete. Starting much faster than sustainable pace can create early time gains that are more than lost later. A target average should be translated into realistic segment splits and adjusted for hills rather than enforced blindly every kilometre.
Aid stations and turns can produce brief slow splits without indicating poor pacing. The total and larger segments matter more than a single noisy reading.
Rounding pace
The calculator keeps fractional seconds internally and rounds displayed clock values to the nearest second. When projecting over a long distance, rounding the pace first can accumulate error.
For example, an underlying pace of 4:30.49/km displays as 4:30 if rounded down, but across a marathon the hidden fraction adds more than twenty seconds. The tool calculates equivalent times from the unrounded pace before formatting them.
Race timing and device displays may truncate, round, or show tenths differently. Keep the raw total time and distance when precision matters.
Health and training limits
Pace is a performance measurement, not a medical assessment. It does not reveal whether an effort is safe or appropriate. Training history, injury, illness, environment, medication, pregnancy, age, and underlying conditions can change risk.
Sudden pain, chest pressure, faintness, or unusual shortness of breath requires stopping and appropriate medical attention. A calculated target should never override symptoms or professional advice.
Limits of the calculator
The result assumes the entered distance and time refer to the same activity and are accurate. It computes an average and cannot describe pacing variation, stops, elevation, wind, surface, measurement uncertainty, or sustainable effort.
Equivalent race times assume constant pace and should not be treated as forecasts. The calculator does not prescribe training zones, race strategy, or health decisions.
Use it to convert recorded performance, compare unit systems, set a mathematical split, or check a treadmill display. Use recent training evidence, course context, and qualified coaching or medical guidance for decisions beyond arithmetic.