Pace is the fundamental unit of running. Every training plan, race goal, and performance comparison comes back to it. Minutes per mile (or minutes per kilometer) is simple to calculate but surprisingly rich as a planning tool once you understand how to use it.
The basic calculation is straightforward. The nuanced applications, using pace to plan splits, predict race times at new distances, design a negative split strategy, or evaluate training progress, require a bit more structure. All of it is accessible and useful for runners at every level.
The Three Directions of Pace Calculation
Most runners think of pace as a single calculation: divide time by distance to get pace. But there are three equivalent problems, and any two values can be used to solve for the third.
Find your pace: You know the distance and time. A 5K run completed in 28:30 produces a pace of 28:30 / 3.1 miles = 9:11 per mile, or 28:30 / 5 km = 5:42 per kilometer.
Find your finish time: You know the distance and your target pace. Running a half marathon at 9:30 per mile: 13.1 miles * 9:30 per mile = 124 minutes 25 seconds = 2:04:25.
Find how far you can run: You know your time and pace. Running at 8:00 per mile for 45 minutes: 45 / 8 = 5.625 miles.
Photo by RUN 4 FFWPU on Pexels
The free pace and race time calculator by EvvyTools handles all three modes and supports both miles and kilometers. It also accepts preset race distances (5K, 10K, half marathon, marathon) for quick entry. Switching between distance units automatically converts the pace, so you don't have to do the unit conversion in your head.
Split Times: Why They Matter More Than Overall Pace
A split time is the pace or time for a specific segment of a run, typically each mile or kilometer. Splits give you a picture of how your effort was distributed across a race or training run. An overall time doesn't tell you whether you went out too fast, faded badly in the second half, or negative-split perfectly. Splits do.
Running splits from a recent race are among the most diagnostic data available to a recreational runner. If your first half was significantly faster than your second, you paced too aggressively. If your second half was faster, you either paced conservatively (a negative split) or started out exhausted. If your splits are relatively even, you paced steadily.
For a runner targeting a 2:00:00 half marathon, the average pace required is 9:09 per mile. Split-level planning reveals something important: even minor pace inconsistency across 13 miles adds up. Starting at 8:50 for the first three miles because you feel good, then fading to 9:30 for the last five, produces a finish time significantly slower than even pacing would have, because the early over-effort depletes glycogen stores and increases cardiovascular fatigue faster than a steady effort.
The EvvyTools pace calculator generates a full split table for every mile or kilometer at your target pace. Printing or saving that table and using it as a reference during a race is a simple and effective pacing strategy.
Negative Split Strategy
A negative split means running the second half of a race faster than the first. It is the pacing strategy used by most elite runners for longer distances, and it's associated with better performance outcomes for recreational runners as well.
The physiological case for negative splitting is well-established. Starting at a conservative pace preserves glycogen stores longer, avoids early lactic acid buildup, and allows you to increase effort in the second half when many competitors are fading. The psychological benefit is also real: passing people in the second half of a race is significantly more pleasant than being passed.
Photo by Stephen Leonardi on Pexels and other athletics organizations publish training guidelines that consistently recommend pacing discipline as a key factor in performance for middle and long distance events.
Riegel's Race Prediction Formula
One of the most practically useful tools in running math is the race time prediction formula developed by Pete Riegel, published in 1977. It allows you to estimate your expected finish time at one race distance based on a recent performance at a different distance.
The formula is: T2 = T1 * (D2 / D1)^1.06
Where T1 is your known finish time at distance D1, and T2 is the predicted finish time at distance D2. The exponent 1.06 captures the fact that performance degrades as distance increases, i.e., you can't run a marathon at exactly your 5K pace.
An example: you ran a 5K in 25:00. What is your predicted marathon time?
T2 = 25 * (42.2 / 5)^1.06 = 25 * (8.44)^1.06 = 25 * 9.28 = 232 minutes = 3:52:00
This gives you a rough target for race planning purposes. The formula has known limitations: it works best for distances within a few multiples of your reference race, it assumes similar training preparation, and it doesn't account for course conditions, weather, or pacing strategy. For a first marathon attempt based on 5K performance, the prediction may be off by 10 to 20 minutes. But it's a more rigorous starting point than pure intuition.
The EvvyTools pace calculator implements the Riegel formula in its race prediction feature. You enter a known race time and distance, select the target race distance, and get a predicted time and corresponding per-mile pace.
Training Zones and How Pace Connects Them
Pace is the external expression of internal effort, and training plans use pace ranges to target specific physiological zones. Understanding the connection makes training plans more than arbitrary numbers.
Easy runs, which should make up 70% to 80% of most runners' weekly mileage, are run at a pace roughly 60 to 90 seconds per mile slower than goal race pace. The purpose is aerobic base building and recovery. Going too fast on easy runs is a very common mistake that increases injury risk and impairs recovery between harder sessions.
Tempo runs, typically run at a pace you could sustain for about an hour in a race (roughly 20 to 40 seconds per mile slower than 5K pace for most runners), train the lactate threshold. This is the pace at which lactate accumulates faster than it can be cleared, and raising it allows you to run faster before accumulating fatigue.
Photo by RUN 4 FFWPU on Pexels is the maximum rate at which your cardiovascular system can deliver oxygen to your muscles, and it's a primary limiter of distance running performance. Training at paces that stress this system improves it over time.
Understanding where each workout sits on the effort spectrum makes it possible to execute training more precisely. Most runners who are "always tired" and making little progress are running their easy days too hard, not their hard days too hard.
Adjusting Pace for Conditions
Pace targets from training plans assume roughly flat terrain and moderate weather. In practice, conditions vary and your targets should flex accordingly.
Heat and humidity increase physiological effort at a given pace. Above 60 degrees Fahrenheit, most runners slow by roughly 20 to 30 seconds per mile for each 10-degree temperature increase. A 9:00-per-mile easy pace in 50-degree weather might need to become 9:30 to 10:00 at 80 degrees to maintain the same cardiovascular effort. Running pace calculators give you target times, but adjusting for conditions requires knowing what effort level you're actually targeting and accepting that the clock pace will be different.
Hills affect pace in both directions. Running uphill at your usual pace requires significantly more effort, and running downhill is mechanically hard on the quads in a way that doesn't show up in pace but does show up in fatigue. Most coaches recommend training by effort on hilly courses and using flat-terrain target pace as a reference for what equivalent effort feels like on level ground.
Wind is underestimated as a performance variable. Running into a 10 mph headwind adds roughly 30 to 45 seconds per mile to your effective effort. A tailwind provides a benefit, but it's smaller than the headwind penalty because drag is a nonlinear function of speed. On out-and-back courses, the headwind on the way out is rarely offset by the tailwind on the way back. This is one reason that personal records set on loop courses or point-to-point with tailwind conditions are sometimes marked with an asterisk by runners who prefer them to have been set in neutral conditions.
Setting Realistic Race Goals
The most practical use of pace math is setting race goals that are ambitious but achievable. A goal that's too conservative is a missed opportunity. A goal that's too aggressive leads to an ugly second half and a disappointing time.
For runners with a recent race performance, the Riegel prediction provides a starting point. For runners who haven't raced recently, a time trial, running a 5K or 10K at race effort as a training run, provides the reference data. World Athletics publishes age-graded performance tables that let you compare your performance to age-group standards, which can be motivating context for setting longer-term goals.
The EvvyTools pace and race time calculator gives you a single place to run all of these calculations: pace, finish time, distance, race prediction, split generation, and negative split planning. More fitness and health tools are available in the EvvyTools tools directory, and training-related guides are on the EvvyTools blog.
Pace math doesn't make running easier. But it makes training more deliberate, and deliberate training produces better outcomes than running by feel alone.
