Choose the Missing Quantity Before Typing Numbers
Pace is elapsed time divided by distance, while speed reverses that relationship to distance divided by time. The form makes the solve direction explicit: leave pace unknown to translate a completed run, leave time unknown to build a purely mathematical duration, or leave distance unknown to see how far a steady entered pace would cover. Supplying all three would hide which value should control, so the contract rejects that ambiguity.
A clock entry must be interpreted as a duration rather than a time of day. Five kilometres in twenty-five minutes means 1,500 elapsed seconds divided across 5,000 metres. The answer is five minutes per kilometre, but that average does not reveal accelerations, stops, hills, GPS drift, traffic, or whether every segment was run continuously.
Normalize the Units Before Dividing
- Convert the course length
Kilometres become metres by an exact factor of 1,000; an international mile is exactly 1,609.344 metres. The calculation retains that full relationship rather than using 1.6 as a shortcut.
- Convert the duration
Hours and minutes are converted to seconds, keeping the raw total unrounded. A displayed clock is formatted only after the relationship has been solved.
- Return the requested pace language
Seconds per kilometre and seconds per mile describe the same performance in different units. Comparing their clock texts without converting the denominator creates a false difference.
Do Not Confuse Pace With Training Intensity
Average pace
Summarizes elapsed duration per unit distance for the entered scenario. It says nothing by itself about physiological effort.
Heart-rate intensity
The heart-rate zone calculator derives planning bands from a chosen maximum and optional resting rate. Terrain and conditions can produce different heart rates at the same pace.
Aerobic field estimate
The VO2 max field estimator applies the Cooper or Rockport protocol. Ordinary training pace cannot be inserted as though it were a completed test.
Audit a Recorded Run Before Comparing It
A precise quotient is only as defensible as the route and clock behind it.
- State whether elapsed time includes stops, pauses, warm-up, or timing-chip offsets, and apply the same convention to every comparison.
- Check whether the distance came from a certified course, track lane, wheel, treadmill calibration, or consumer GPS estimate.
- Compare sessions only with context for elevation, surface, weather, crowding, fatigue, and intended effort; the solver does not adjust for them.
- Stop exercise for chest pressure, faintness, severe breathlessness, or other concerning symptoms and seek appropriate care. The arithmetic is not medical clearance.
Treat a Goal Pace as a Hypothesis to Test Safely
Solving a target time from a desired pace proves only that the numbers are internally consistent. It does not establish that the runner can sustain the effort or account for heat, fueling, recovery, injury, altitude, course profile, or race-day conditions. Build changes gradually and use qualified coaching or clinical guidance when health, rehabilitation, or competitive risk makes generic arithmetic insufficient.
This website is independent and does not certify courses, organize races, sell entries, or forecast performance. Save the solve direction, units, distance source, and timing convention with the result. That record makes a later comparison useful without turning a clean average into a claim about every kilometre or the next event.