Skip to content
NSNormandin SystemsTHE EVERYDAY TOOLBOXMain site
{ }

Data / YOUR EVERYDAY TOOLBOX

Running Pace Calculator

Calculate running pace, distance, elapsed time, or speed from the values you know.

✓ Free to use✓ No account neededHow to use this tool ↓
YOUR WORKSPACESee an example ↗

Opening your tool…

Runs in your browser. Check important results and keep a copy of your original files.

THE PRACTICAL GUIDE · NORMANDIN SYSTEMS

Get more from Running Pace Calculator

Running Pace Calculator helps you calculate distance, time, or pace from the other two values. Pace is elapsed time per unit distance, while speed is distance per unit time. The tool can also express speed for supported pace inputs. The most reliable way to use the result is to keep the input values, their units, and the calculation assumptions together. That makes it possible to reproduce the example and understand why a later result changes. The result is arithmetic at a stated average pace, not a prediction of individual performance or a training prescription. Terrain, conditions, and stops change actual time. Start with the worked example below, then replace its values with your own. Check whether each field expects a whole number, decimal, percentage, or duration before entering it. Leave the unknown field empty; supplying all three values prevents the tool from knowing which one to calculate. A displayed result is an output of the supplied inputs, so a plausible-looking number still deserves a quick reasonableness check.

Guide updated October 13, 2026

How to use this tool

  1. Enter two of distance, elapsed time, and pace, plus kilometres or miles. Choose any unit or calculation mode before interpreting the values already visible in the form.
  2. Review the input assumptions. Leave the unknown field empty; supplying all three values prevents the tool from knowing which one to calculate.
  3. Read the calculated result and compare it with the worked example or a simple estimate. A decimal-place or unit mistake often produces a large discrepancy.
  4. Record the result together with the original inputs. If comparing scenarios, change one assumption at a time so that its effect remains clear.

SEE IT IN PRACTICE

A worked example

EXAMPLE INPUT
Distance 5 km; time 00:30:00
RESULT / WHAT TO EXPECT
Pace 06:00 per km; equivalent speed 10 km/h

Thirty minutes divided by five kilometres is six minutes per kilometre. Five kilometres in half an hour is ten kilometres per hour.

Elapsed time and moving time

A recorded activity may report moving time that excludes pauses, while an event finish time usually includes the full elapsed interval. Those definitions produce different average paces for the same distance. Keep the timing basis consistent when comparing activities. A projected finish at constant pace assumes that the chosen average can be maintained; it is a scenario calculation, not a performance guarantee.

Supply two known quantities

Distance, elapsed time, and pace are linked, so the tool needs two to calculate the third. Leave the unknown field empty rather than entering three values that may disagree. Select kilometres or miles before interpreting the pace unit. Six minutes per kilometre and six minutes per mile describe different speeds, even though the minute figure is identical. Use an explicit time format to avoid reading decimal minutes as minutes and seconds.

When this tool is useful

  • Check a recorded average pace using explicitly stated inputs.
  • Compare finish times at a constant pace by comparing the same calculation under different assumptions.
  • Convert a pace to speed with a worked example that can be checked independently.

Tips for a better result

  • The result is arithmetic at a stated average pace, not a prediction of individual performance or a training prescription. Terrain, conditions, and stops change actual time.
  • Leave the unknown field empty; supplying all three values prevents the tool from knowing which one to calculate.
  • Keep intermediate precision where possible, then round the final number to suit the context. Rounding should not conceal a meaningful difference between two scenarios.

Frequently asked questions

Why is a smaller pace value faster?

Pace measures the time needed for one kilometre or mile. Covering that distance in fewer minutes is faster. Speed has the opposite direction: more distance per hour means faster movement.

Why can two calculators give different answers?

They may use different assumptions, formulas, unit conventions, rounding, or treatment of boundary cases. Compare the full input definitions before comparing only the final displayed number.

How can I check an unexpected result?

Return to a simple example and verify the inputs individually. Leave the unknown field empty; supplying all three values prevents the tool from knowing which one to calculate. Then change one field at a time and see whether the direction of the change agrees with the relationship being calculated.

What happens to the information I enter?

The utility processes your input in this browser. Some tools retain field values in browser storage or the URL; avoid entering secrets in shareable fields. Page and asset requests still go to the hosting provider. Read the privacy and offline-use notes for details.