Pace Calculator
Find your running pace in minutes per kilometer (or per mile) by dividing total run time by distance covered. Use it after every workout or race to log pace, set training targets, and compare efforts across different distances.
Last updated: May 2026
Compare with similar
About this calculator
The formula is pace = (hours * 3600 + minutes * 60 + seconds) / distance / 60, returning minutes per kilometer when distance is in km. Variables: hours, minutes, seconds together encode the elapsed run time; distance is the run length in your chosen unit. The result is the average pace across the entire effort, not instantaneous speed. Pace is the standard reference metric in running because most race goals are expressed as a target pace (e.g. 4:30/km marathon pace), and training plans prescribe runs as easy pace, threshold pace, or interval pace based on this metric. Edge cases: GPS watches typically overstate distance by 1-3% in tree cover, urban canyons, or with tight turns, which makes the calculated pace appear faster than reality - prefer measured tracks or certified courses for accurate baseline pacing. Treadmill pace and outdoor pace are not directly comparable because a treadmill has no air resistance; set the treadmill incline to 1% to approximate outdoor effort at the same speed. Pace varies meaningfully with terrain (flat road vs trail), wind, temperature, and altitude - a 4:30/km pace at sea level on flat tarmac may correspond to 4:50/km on a hilly trail at 2,000 m altitude for the same physiological effort. Average pace masks variability: a run with a fast first kilometer and slow last kilometer has the same average as a perfectly even-paced run, but the training stimulus and effort cost are very different.
How to use
Example 1 - You finish a 10 km training run in 52 minutes 30 seconds. Compute total seconds: 0*3600 + 52*60 + 30 = 3,150 seconds. Divide by distance and convert: 3,150 / 10 / 60 = 5.25 min/km, or 5:15 per kilometer. Verify by multiplying back: 5.25 min/km * 10 km = 52.5 minutes = 52:30, matching the input. This pace puts you on track for roughly a 1:55 half marathon if you can hold the effort, using a standard 2.1x scaling factor for the longer distance. Example 2 - You run 5 miles in 38 minutes 45 seconds. Convert distance to km (5 * 1.609 = 8.045 km) and total time to seconds (38*60 + 45 = 2,325 s). pace = 2,325 / 8.045 / 60 = 4.815 min/km, which is 4:49/km or 7:45/mile. Verify by converting back: 4:49/km * 8.045 km = 38.75 min = 38:45. The 7:45/mile pace is a solid steady-state aerobic effort for most recreational runners and corresponds to roughly 75-80% of maximum heart rate for someone with a typical training base.
Frequently asked questions
What is the difference between pace and speed in running?
Pace is the inverse of speed: pace is time per unit distance (min/km or min/mile), while speed is distance per unit time (km/h or mph). Runners almost universally use pace because race goals and training prescriptions are expressed in time terms - a 4:30/km marathon means each kilometer should take 4 minutes 30 seconds, which is more actionable than the equivalent 13.33 km/h. To convert between them, divide 60 by your pace in minutes (e.g. 60 / 4.5 = 13.33 km/h). Cyclists and treadmill displays often default to speed because vehicles are traditionally measured in distance-per-time, but a runner watching a 13.3 km/h treadmill is mentally converting back to pace anyway. Use whichever your training partners and race materials use, but understand that the two metrics are reciprocals - if your speed is constant, your pace is constant in the inverse sense.
How does GPS watch accuracy affect my calculated pace?
Consumer GPS watches typically have a distance error of 1-3% in open conditions and can reach 5-10% error in dense urban areas, deep forests, or tight indoor tracks. A 1% distance overestimation makes your displayed pace 1% faster than reality - so a watch showing 4:30/km may correspond to a true 4:33/km. This matters most for race-pace runs and threshold workouts where small pace differences map to large physiological differences. For accurate baseline pacing, run a known-distance route (a certified road course or a marked track) and calibrate your watch's reported pace against the true average. Multi-band GPS watches (released widely since 2022) cut error to under 1% in most conditions and are worth the upgrade for runners doing pace-based training, though basic single-band watches remain fine for casual logging.
Can I compare my treadmill pace to my outdoor pace directly?
No - a treadmill belt moves under you, eliminating air resistance and the propulsion cost of overcoming wind, so treadmill running at a given pace is roughly 2-5% easier than outdoor running at the same pace on flat ground. Setting the treadmill incline to 1% closes most of this gap and produces an effort approximately equal to outdoor flat running, which is why coaches commonly prescribe 1% as the default training incline. Treadmills also lack lateral motion, slight surface unevenness, and visual flow cues that subtly affect outdoor pacing perception. For race preparation specifically, do at least 60-70% of your runs outdoors so your body adapts to the actual mechanics you will use on race day. If you must train indoors during winter, accept that your treadmill pace may not transfer one-to-one to a goal race pace until you've done several outdoor runs to recalibrate.
What are common mistakes when calculating and using running pace?
The most common mistake is using GPS-measured distance as ground truth without recognizing the typical 1-3% error - especially on out-and-back routes through buildings or trees where the error can compound. Another frequent error is comparing pace across different terrains or conditions as if they were equivalent: a 5:00/km pace on a hilly trail at altitude is physiologically harder than the same pace on a flat sea-level road, but the watch shows the same number. Runners also commonly average paces across different segments naively (e.g. 4:00/km for 1 km then 6:00/km for 1 km is not 5:00/km average pace - it is total_time / total_distance, which gives the same answer here but produces wrong results when segment distances differ). Failing to convert between min/km and min/mile correctly (multiply min/km by 1.609 to get min/mile) is a frequent error in mixed-unit training plans. Finally, chasing pace at the expense of effort - running too fast on easy days because the watch shows a target number - is the most common pace-driven training mistake, leading to incomplete recovery and elevated injury risk.
When should I NOT use a pace calculator?
Skip pace tracking entirely on recovery runs and easy long runs, where effort (perceived exertion, heart rate, conversational ability) is the right metric and pace becomes a distraction that pushes you to run harder than the training stimulus calls for. The calculator is the wrong tool for trail running over significant elevation - pace becomes meaningless when 200 m of vertical gain in a kilometer can double the effective effort; use vertical gain per hour or heart rate instead. For ultra-distance events (50 km+), average pace across the whole event is too coarse to plan with - use segment paces between aid stations and plan for significant pace decay in the final third. Pace is also misleading for interval training where you care about the work pace and recovery pace separately, not the blended average. Finally, do not use pace for swimming or rowing comparisons - those sports use different conventions (per 100 m or split per 500 m) that don't translate from running pace directly.