Run-Walk Interval Calculator

{{ summaryTitle }}: {{ summaryValue }} · {{ summaryLine }} {{ badge.label }} {{ badge.value }}

Interval visual unavailable

Distance preset:

Route distance:

Interval preset:

Run interval: {{ formatDuration(runIntervalTotalSeconds) }}

min

sec

Walk interval: {{ formatDuration(walkIntervalTotalSeconds) }}

min

sec

Pace basis:

Run pace:

min

sec

Walk pace:

min

sec

Course marker spacing:

First segment:

Continuous comparison pace:

0:00 follows the current run pace and keeps this refinement neutral.

Comparison minutes:

min

Comparison seconds:

sec

Stop buffer per marker:

sec

Measure	Value	Planning use	Copy
{{ row.label }}	{{ row.value }}	{{ row.note }}

Event	Distance	Elapsed	Phase	Next action	Copy
{{ row.event }}	{{ row.distance }}	{{ row.elapsed }}	{{ row.phase }}	{{ row.next }}

Ratio	Finish	Average pace	Run share	Vs selected	Copy
{{ row.label }}	{{ row.finish }}	{{ row.pace }}	{{ row.runShare }}	{{ row.delta }}

Planned walk breaks change a run from one continuous effort into a repeatable rhythm. Runners use that rhythm when building fitness, returning after time away, managing a long event, or keeping effort controlled on a demanding route. The useful question is not simply how much time is spent walking. It is how the chosen run pace, walk pace, interval lengths, and route distance combine into a finish plan that can still be followed when tired.

A time ratio and a distance ratio are not the same. Four minutes of running followed by one minute of walking gives running 80% of the cycle time, but running usually covers more than 80% of the cycle distance because the run pace is faster. The finish can also arrive partway through a segment, so multiplying an average cycle by a whole number of repeats can overstate the final time.

Four parts of a practical plan deserve separate attention:

Run and walk durations determine how often the effort changes and how many cues must be followed.
Segment paces determine the distance covered during each timed block.
Course markers connect the time pattern to real locations such as kilometre boards or aid stations.
Planned stop time separates moving pace from elapsed pace when a pause adds time without adding distance.

Shorter cycles create frequent recovery opportunities, but they also create more watch alerts and more chances to miss a cue. Longer run blocks are simpler to follow, yet they may stop serving as controlled intervals if fatigue forces an unplanned walk before the scheduled break. Training is the best place to test both the physical effort and the cue load.

A finish estimate assumes the entered paces remain available across the route. Hills, heat, crowding, GPS error, fueling, fatigue, injury, and unexpected stops can all change the outcome. People who are inactive, returning after illness or injury, or increasing intensity should build gradually and seek appropriate medical or coaching guidance when symptoms or health conditions make running uncertain.

How to Use This Tool:

Set the route and the repeat pattern first, then add only the pacing and stop assumptions you can defend from training or course information.

Choose a Distance preset or enter the Route distance in kilometres or miles.
Select an Interval preset or set the run and walk minutes and seconds. The run interval must be above zero; a zero walk interval represents continuous running.
Choose the Pace basis and enter a separate run pace and walk pace. Use expected segment paces rather than the overall pace you hope to see at the finish.
Set Course marker spacing. Open Advanced only when the plan begins with walking, uses a separate comparison pace, or includes a stop buffer at intermediate markers.
Check Plan summary for the headline estimate, then use Route cue ledger to verify the segment sequence and marker timing. Ratio comparison is useful for alternatives, while Pace timeline shows how moving and elapsed time separate across the route.

Interpreting Results:

Finish time and Average pace include the clipped final segment and any stop buffer applied before the finish. Moving time and Moving pace leave those marker stops out. Compare like with like when checking the plan against a race cutoff or a previous run.

The route ledger is the exact schedule for the selected intervals. A ratio comparison uses a cycle-average projection for the alternatives, so it can differ slightly from the exact selected plan when the route ends in the middle of a run or walk block.

Treat a high cycle count as a practical warning. Even a mathematically sound plan may be difficult to follow if it produces constant alerts. Confirm the paces in training, check that the course markers use the expected unit, and leave extra time when terrain or aid-station congestion is likely.

Technical Details:

Each timed segment becomes distance by dividing its duration by its pace. The schedule advances one segment at a time until it reaches the route distance; the last segment is shortened when only part of it is needed. All distance arithmetic is performed in kilometres, using 1 mile = 1.609344 kilometres.

Formula Core:

The governing equations connect segment time, pace, distance, stop time, and average pace.

\begin{array}{rcl} d_{j} & = & \frac{t_{j}}{p_{j}} \\ T_{elapsed} & = & \sum_{j = 1}^{k} t_{j} + N_{stops} t_{stop} \\ p_{average} & = & \frac{T_{elapsed}}{D} \end{array}

For segment j, t is seconds used, p is seconds per kilometre, and d is kilometres covered. D is route distance. Intermediate stop count is the number of complete marker spacings strictly before the finish, so a marker exactly at the finish does not add another stop.

A 4-minute run at 6:00 per kilometre covers about 0.667 km. A 1-minute walk at 10:30 per kilometre covers about 0.095 km. One full cycle therefore covers about 0.762 km in 5 minutes; a route that ends before the next full block uses only the time needed for the remaining distance.

Rule Core:

The planning label is assigned in order. Once a rule matches, later rules are not considered.

Run-walk planning label rules
Label	Exact rule	Practical reading
High cue load	Cycle count > 120	Test whether that many alerts remain usable.
Walk-heavy	Run time share < 50%	More moving time is spent walking than running.
Light walk breaks	Run time share > 88% and walk time > 0	The pattern is close to continuous running.
Endurance pattern	Distance ≥ 21 km and walk time > 0	Walk breaks repeat across a long route.
Balanced plan	No earlier rule matches	No special cue-load or time-share rule applies.

The route may be entered from above zero through 500 in the selected unit. Run and walk pace values must be positive, the run interval must be positive, marker spacing must be positive and no more than twice the route distance, and stop buffer accepts 0 through 600 seconds per intermediate marker. Calculations retain full precision; displayed durations and paces are rounded for reading.

Accuracy Notes:

The schedule is deterministic, but race and training inputs are estimates. It does not model hills, surface changes, weather, fatigue, GPS drift, fueling, crowding, or a pace that changes from one cycle to the next.

Use segment paces observed in training rather than a target average pace.
Match marker spacing to the course information you will actually follow.
Recheck the plan after adding realistic water, crossing, or aid-station stops.
Increase running volume and intensity gradually, especially after inactivity.

References:

Physical Activity Guidelines for Americans, 2nd edition, U.S. Department of Health and Human Services, 2018.
NIST Guide to the SI, Appendix B.8, National Institute of Standards and Technology.
Marathon, World Athletics.
Half Marathon, World Athletics.