Combined Run Walk Pace: Why It Is Not a Simple Average

If you use a run/walk strategy, your overall pace is not always the simple average of your run pace and walk pace. Combined run walk pace depends on total time divided by total distance.

The simple mistake

A common assumption is that if you run at 12:00 per mile and walk at 18:00 per mile, the average pace should be 15:00 per mile. That sounds reasonable, but it only works if the running and walking portions cover the same amount of distance.

In a time-based run/walk interval, such as 5:00 run / 5:00 walk, the faster running segment covers more distance than the walking segment. That gives the running pace more influence on the combined average pace.

A 5:00 run / 5:00 walk example

Here is the default example from the run walk calculator:

• Run interval: 5:00
• Walk interval: 5:00
• Run pace: 12:00 per mile
• Walk pace: 18:00 per mile

The combined pace is the total cycle time divided by the total cycle distance:

10 minutes ÷ 0.6944 miles = 14.4 minutes per mile, or 14:24 per mile.

Why the running segment has more weight

Pace is based on time per distance. During the same 5 minutes, running at 12:00 per mile covers more ground than walking at 18:00 per mile. Because more of the distance happens during the faster segment, the final average pace is pulled closer to the run pace than a simple number average suggests.

This is why a run/walk pace calculator needs to calculate distance covered during each part of the cycle instead of only averaging the pace numbers.

What changes with distance-based intervals?

Distance-based run/walk intervals work a little differently. If you set the calculator to run 0.50 miles and walk 0.50 miles, then each part covers the same distance. In that specific case, the combined pace is closer to the simple average of the two pace numbers.

But if the distance split is uneven, such as running 0.50 miles and walking 0.25 miles, the longer segment has more influence. The overall pace still comes from total time divided by total distance.

Why this matters for finish time

A small pace difference can become a large finish-time difference over longer distances. For the 5:00 / 5:00 example above, 14:24 per mile equals exactly 24 hours for 100 miles before stop time or terrain adjustment. If you mistakenly planned from 15:00 per mile, the projection would be 25 hours instead.

That is a one-hour difference from a misunderstanding of the combined pace math.

Use the calculator for real scenarios

The easiest way to compare run/walk pacing options is to test them directly. Change the run interval, walk interval, run pace, walk pace, stop time, terrain adjustment, or display units and compare the results.

The calculator supports both miles and kilometers, time-based intervals, distance-based intervals, and common race distances from 1K through 100 miles.

This is planning, not a promise

These calculations are estimates. Real results can change because of weather, hills, trails, fatigue, fueling, training, and race-day choices. The goal is not to guarantee a finish time. The goal is to understand how your run/walk plan affects the projection.