Marathon Pace KM
Menu

Run-walk pace calculator and marathon pacing guide

A five-hour marathon averages about 7:07/km. If part of those five hours is spent walking or standing still, the running sections need to be faster. How much faster depends on the intervals, the walking pace and the time stopped.

Enter your target, run/walk intervals, walking pace and stop allowance below.

Run-walk pace calculator: choose your target and intervals

Full marathon distance: 42.195 km. The running pace is the pace during run intervals; the finish target includes both movement and stops. This model begins with a run interval and pauses the interval timer while standing still.

Finish target: 5:00:00.

Required running-interval pace

6:46.2 / km

10:53.6 / mile

Time running
4:26:00
Time walking
0:29:00
Distance running
39.295 km
Distance walking
2.900 km
Total moving time
4:55:00
Standing still
0:05:00

29 complete cycles plus a partial final interval, starting with a run. Stops pause the interval timer.

This is the running-interval pace needed by the arithmetic. It is faster than the overall race average when slower walking or stops are included.

Read the interval and partial-final-cycle method. The five-hour goal page keeps the same calculator beside its goal-specific split tables.

What running pace do I need for a five-hour run-walk marathon?

Take a 5:00:00 target, alternating 9 minutes running and 1 minute walking. Assume walking at 10:00/km and allow 5 minutes standing still across the race. Start with a run interval and pause the interval timer while stopped.

  1. Moving time: 300 − 5 = 295 minutes.
  2. Complete cycles: 29 cycles of 10 minutes take 290 minutes.
  3. Final interval: 5 minutes remain. All five are running, because each run interval lasts nine minutes.
  4. Walking: 29 minutes at 10:00/km covers 2.900 km.
  5. Running: 266 minutes remain to cover 42.195 − 2.900 = 39.295 km.

266 minutes ÷ 39.295 km = 6:46.2/km while running.

The overall race average remains 7:06.6/km. The required running pace is about twenty seconds per kilometre faster than that average. It is a calculated requirement, not evidence that this pace or interval pattern is sustainable for you.

Open the run-walk calculator

The calculator sits on the five-hour goal page. Change the finish time in its splits calculator above the run-walk section to explore another target.

How do walk breaks and stopped time change the pace?

All examples below assume 42.195 km and a 10:00/km walking pace. Intervals are measured in minutes, begin with a run and continue until the moving-time budget ends. Standing still pauses the interval timer.

Original arithmetic examples; these are not recommended targets or ratios
Finish targetRun : walkStoppedTime walkingRequired run pace
5:00:009 : 10 min30 min6:53.3/km
5:00:009 : 15 min29 min6:46.2/km
5:00:004 : 15 min59 min6:30.1/km
4:30:009 : 13 min26 min6:05.2/km
4:00:009 : 10 min24 min5:25.7/km

More walking can reduce the duration of each running bout, while also requiring a faster running pace for the same finish target. If that faster pace feels forced in ordinary training, the combination of target and intervals needs changing. The calculator cannot decide which part to change.

Notice that five stopped minutes do not simply add five seconds to every kilometre. They shorten moving time, change the last interval and alter the distance left for running. That is why the calculator counts the final partial interval explicitly.

Calculate average pace without averaging two pace numbers

For a complete cycle, add the distances covered while running and walking, then divide the cycle time by that total distance. Do not take a simple average of the two pace numbers.

For example, four minutes at 6:00/km covers 0.6667 km. One minute at 10:00/km covers 0.1000 km. The five-minute cycle covers about 0.7667 km, so its average is about 6:31.3/km. The simple average of 6:00 and 10:00 would be 8:00/km, which ignores how long you spend at each pace.

For a finish-target calculation, use seconds consistently:

Moving time = target time − stopped time
Walking distance = walking seconds ÷ walking pace in seconds/km
Running pace = running seconds ÷ (42.195 − walking distance)

Count complete cycles first, then assign any remaining time to the running part and, if necessary, the walking part of one last cycle. A runner who finishes partway through a run interval does not owe the clock a final walk.

The model assumes immediate transitions and constant paces. Crowds, hills, taking a drink and fatigue can change real execution. Check the full method and assumptions before turning its output into a plan.

Rehearse the parts the equation cannot measure

Choose an appropriate existing training run to try the intended pattern. Measure walking pace while actually moving as you would on race day, including carrying your kit. An optimistic walking estimate makes the required running pace look easier than it really is.

Record the interval lengths, elapsed time, actual walking pace, time stopped, effort and what happens during transitions. If you use a watch interval alert, establish what it does when you pause the activity. Match that behaviour to the calculator's assumption that stops pause the interval cycle.

Practise moving to the side before slowing, checking behind and avoiding abrupt stops in a crowded group. At aid stations, decide whether taking a drink belongs in the walking interval or in stopped time. Count it once. Walking to collect water and adding the same minute as standing still would double-count the delay.

Use the fueling schedules to plan intake by elapsed time. A run-walk strategy changes where a reminder may fall on the course, but it does not remove the need for a practised fuel plan.

Use pace bands as an elapsed-time reference

The five-hour pace band shows an even-average reference: 35:33 at 5 km and 2:30:00 at halfway. It does not print a run-walk interval timetable. A checkpoint reached just after a walk can differ slightly from one reached near the end of a run.

Judge progress across several official markers rather than speeding up after every walk to force the next watch kilometre. Compare elapsed time, which includes stops. The splits guide explains the difference between segment and cumulative times; the GPS guide covers distance discrepancies.

Check the organiser's cutoffs and whether they use gun time, chip time or fixed station closure times. A finish-time calculation does not establish that every intermediate cutoff will be met.

What does research say about run-walk marathons?

Hottenrott and colleagues compared run-walk and continuous-running strategies in a small study of non-elite marathoners. The run-walk approach produced similar finish times with less reported muscle discomfort, but did not reduce the measured cardiovascular stress.

That finding supports considering planned walking as a race strategy. It does not prove that a particular ratio will make you faster, prevent injury or make an underprepared marathon safe. The pace table above is a mathematical comparison, not an extrapolation of the trial's results.

Davin's account of walking late at Sydney describes a different situation: walking after the original race plan had broken down. It is useful context, but not a personal trial of a planned run-walk strategy.

Run-walk marathon questions

Which run-walk ratio is best?

There is no universal ratio established by this calculator. Start with a pattern you can rehearse comfortably, then check whether its required running pace and the event's cutoffs are realistic.

Can I use run-walk for a sub-four marathon?

The four-hour 9:1 example requires about 5:25.7/km during the running intervals at the stated walking pace. That demonstrates the arithmetic, not whether it is an appropriate strategy for a particular runner.

Should I turn auto-pause off?

You need a reliable elapsed clock for race checkpoints. Check how your watch displays elapsed versus moving time and how pausing affects interval alerts before race day.

Source and calculation notes