Pace Calculator
Enter a distance and time to get your pace per mile/km, speed, and predicted finish times for other common race distances at the same pace.
Pace
8:04/mile
5:01/km
Speed
7.4 mph
12.0 km/h
Covering 3.1 miles in 25:00 works out to a pace of 8:04/mile (5:01/km) — a speed of 7.4 mph (12.0 km/h).
Predicted Finish Times at This Pace
| Race | Distance | Predicted Time |
|---|---|---|
| 1 Mile | 1 mi | 8:04 |
| 5K | 3.11 mi | 25:03 |
| 10K | 6.21 mi | 50:07 |
| 10 Miles | 10 mi | 1:20:39 |
| Half Marathon | 13.11 mi | 1:45:43 |
| Marathon | 26.22 mi | 3:31:27 |
What is a Pace Calculator?
A pace calculator converts a distance and time into pace — the rate of movement, usually expressed as minutes per mile or minutes per kilometer for running and walking. Pace is simply the inverse of speed: instead of "how far in one hour," it answers "how long per unit of distance," which is the more natural way runners think about and set training and race goals.
Beyond a single pace figure, this calculator projects what that same pace would produce over other common race distances — useful for setting a realistic goal time for an upcoming race based on a recent training run or previous race result.
How Is Pace Calculated?
Pace is simply time divided by distance, and speed is its inverse — distance divided by time. This calculator computes both directions at once so you can think in whichever unit is more natural: pace for planning splits during a run, speed for comparing against a treadmill display or bike computer.
Speed (mph) = Distance (miles) ÷ Total Time (hours)
The finish-time table above runs the same formula in reverse: it takes your calculated pace and multiplies it by other common race distances to project a finish time — exactly what calculator.net's "finish time calculator" mode does, folded into one tool here.
Aerobic vs. Anaerobic Pace
Pace and heart rate are positively correlated — the faster your pace, the higher your heart rate climbs, up to a point. Training at your aerobic threshold pace (roughly 70–80% of max heart rate) burns a mix of fat and carbohydrate and can be sustained for a few hours, making it the backbone of most endurance training. Push past your anaerobic threshold (roughly 80–90% of max heart rate) and the body shifts to relying primarily on stored glycogen rather than oxygen — a pace that feels sustainable for minutes, not hours.
A common way to estimate your own anaerobic (lactate) threshold is a 30-minute time trial at maximum sustainable effort, averaging your heart rate over the final 20 minutes — that average approximates your lactate threshold heart rate (LTHR). Subtracting roughly 30 beats per minute from that figure gives a rough estimate of your aerobic threshold heart rate.
Why the Finish-Time Table Isn't Perfectly Accurate
The table above assumes you can hold your exact current pace across every listed distance, which is realistic for similar distances but increasingly optimistic the further apart the distances are. Race pace naturally slows as distance increases — the pace that feels comfortable for a 5K is rarely sustainable for a full marathon, since longer efforts draw more heavily on fat metabolism and pacing discipline rather than raw aerobic power.
Runners commonly use a "negative split" strategy — running the second half of a race slightly faster than the first — both as a pacing safety margin (avoiding an early pace that isn't sustainable) and because it tends to produce better finishing times than starting too fast and fading late.
Example — Your Current Inputs
Covering 3.1 miles in 25:00 works out to a pace of 8:04/mile (5:01/km) — a speed of 7.4 mph (12.0 km/h).
Additional Example — Marathon World Record Pace
The men's marathon world record (as of the mid-2020s) is a little over 2 hours, averaging roughly 4:37 per mile (2:52 per km) — a pace of about 13 mph sustained for over 26 miles. For comparison, a 4-hour marathon finisher — a common goal time for recreational runners — averages about 9:09 per mile, nearly twice as slow but still a demanding pace to hold for the full distance.
This wide gap illustrates why finish-time predictions get less reliable the further the target distance is from the pace you actually trained or raced at — extrapolating a fast 5K pace directly onto marathon distance almost always overestimates what's realistically sustainable.
About These Parameters
- Distance
- The distance covered, in miles or kilometers. Standard race distances — 5K, 10K, half marathon (13.11 mi), and marathon (26.22 mi) — are used to build the finish-time projection table.
- Time
- The total time taken (or targeted) to cover the distance above, in hours, minutes, and seconds. This is the only other input needed — pace and speed are both fully determined by distance and time together.
Frequently Asked Questions
What's a good running pace for a beginner?
There's no universal "good" pace — it depends entirely on fitness level, age, and goals. Many beginner runners comfortably train in the 10–14 minute-per-mile range. What matters far more than any specific number is training at a pace where you can hold a conversation (roughly your aerobic threshold), which builds endurance safely and reduces injury risk compared to consistently training too hard.
How accurate are the predicted finish times for other distances?
They're a reasonable estimate for distances close to the one you entered, but become less reliable the further apart the distances are — pace naturally slows as distance increases. Treat the marathon prediction from a 5K time as optimistic; dedicated race-prediction formulas (like Riegel's formula) apply a fatigue factor for longer distances, which this simple linear projection does not.
What's the difference between pace and speed?
They measure the same thing from opposite directions. Speed answers "how far in a fixed amount of time" (miles or km per hour) — useful for cycling and treadmills. Pace answers "how long per unit of distance" (minutes per mile or km) — the more natural framing for runners planning splits during a race, since race distances are fixed and you're solving for time.
Should I run at the same pace the whole race?
Most coaches recommend even or slightly negative splits (running the second half marginally faster than the first) over starting fast and fading. Starting too aggressively burns through glycogen stores and accumulates fatigue-inducing byproducts faster than your body can clear them, which is why races that start too fast so often end in a painful slowdown over the final stretch.