How this instrument works
Running pace, in the training-log sense, is the minutes-per-kilometre figure for one specific logged session — not a goal, not a prediction, just what today's run actually worked out to. It's the same division as any other pace calculation, time divided by distance, but this instrument is framed specifically around recording a completed run in kilometres, the unit most training logs and GPS watches outside the US default to.
Logging pace session by session, rather than just distance or duration alone, is what turns a string of individual runs into a readable fitness trend. An easy 8 km run logged at 56:00 (7:00/km) sitting next to a tempo 8 km run logged at 32:00 (4:00/km) tells a coach or a training app two very different things about that day's effort, even though the distance column reads identically in both rows — the pace column is what actually distinguishes an easy day from a hard one.
This calculator deliberately doesn't ask what kind of run it was — easy, tempo, interval, long — because that classification belongs in the training log alongside the number, not in the arithmetic that produces it. Feed it whatever time and distance a GPS watch or a manually timed loop reported, and read off the pace to write down next to today's date.
- Enter Logged session time (minutes) — the total time from your watch or stopwatch for today's run.
- Enter Logged session distance (km) — the distance covered in that time, in kilometres.
- Read Today's pace (min per km) — the figure to enter into a training log next to today's date.
- Log it alongside a note on run type (easy, tempo, interval, long) — the pace number alone doesn't say which one this was.
Worked example — 30 minutes over 5 km
Enter a logged time of 30 minutes and a logged distance of 5 km. Today's pace = 30 ÷ 5 = 6.00 minutes per km — the figure to write into a training log for this session, whatever kind of run it was.
The same calculation applied to a session logged at 56:00 over 8 km returns an easy-day pace of 7:00 per km, while 32:00 over 8 km returns a tempo pace of 4:00 per km — two entries with an identical distance column but a very different pace column, exactly the contrast a training log is built to show.
Questions
How is this different from the site's plain pace calculator?
The underlying division is identical, but this page is set up for logging a completed training run specifically — inputs are labelled logged session time and logged session distance in kilometres, matching what a GPS running watch typically records. The plain pace calculator uses miles and is framed as a general-purpose tool for any timed activity, not specifically a running-log entry.
Should I log pace for every single run?
Most training plans benefit from it, since pace alongside a note on run type (easy, tempo, interval) is what turns a log of dates and distances into a readable trend of fitness and effort over weeks. A string of distance-only entries can hide a slow drift in pace at the same perceived effort, which is often one of the first signs of overtraining or, in the other direction, of genuine fitness gains.
Why does my logged pace vary so much between easy and tempo runs?
Because it's supposed to — an easy run and a tempo run are deliberately run at different efforts, and the pace column is exactly what should separate them in a log. A 3:00-per-km gap between an easy day around 7:00/km and a tempo day around 4:00/km is a normal and healthy spread for many training plans, not a sign of inconsistency.
Does this calculator adjust for hills or heat when logging pace?
No — it logs the raw pace implied by the time and distance you enter, with no adjustment for terrain, heat, wind, or altitude. Many runners note those conditions alongside the pace entry in their log by hand, since a 5:00-per-km effort on a hilly, hot course represents meaningfully more fitness than the same pace on a flat, cool one.
Can I use this for a treadmill run instead of an outdoor one?
Yes — enter the treadmill's displayed time and distance the same way you would for an outdoor GPS-logged run. Treadmill distance readings can drift slightly out of calibration on some machines, so if your logged pace looks consistently off from your outdoor pace, it's worth spot-checking the treadmill's distance display against a known distance.