Calculator

Worked examples

Worked 50K and 50-mile aid-station plans

A 7-hour 50K with 20 minutes of stops needs an 8:00 per km moving pace (12:52 per mile), and a 12-hour 50-miler with 40 minutes of stops needs 13:36 per mile. Planned stops come out of the goal time first, and the rest is divided by distance. Both worked examples list every station's arrival and departure.

Last updated November 19, 2026

How to read the examples

Both examples use Goal mode. Planned stops are subtracted from the target elapsed finish time before required moving pace is calculated. Each checkpoint arrival includes moving time plus stops completed at earlier stations. Departure also includes the stop at the current station.

required moving pace = (goal time - total stops) / distancecheckpoint departure = arrival + current stop

These are arithmetic demonstrations, not recommended race goals. Terrain, elevation, conditions, and runner capability are deliberately outside the model.

All clock times in these examples are Day 1 on the printed card.

Worked 50K plan

The fictional race starts at 6:30 AM. The goal is 7:00 elapsed, with four five-minute stops at cumulative distances of 8, 17, 26, and 39 kilometres.

Distance50 km
Goal7:00
Stops0:20
Moving pace8:00/km

Seven hours minus twenty stopped minutes leaves 6:40, or 400 minutes, for moving. Dividing 400 minutes by 50 kilometres produces an 8:00 per kilometre moving pace.

CheckpointDistanceArrivalStopDeparture
CheckpointPine GateDistance8 kmArrival7:34 AMStop5 minDeparture7:39 AM
CheckpointCreek BendDistance17 kmArrival8:51 AMStop5 minDeparture8:56 AM
CheckpointHigh PointDistance26 kmArrival10:08 AMStop5 minDeparture10:13 AM
CheckpointLake RoadDistance39 kmArrival11:57 AMStop5 minDeparture12:02 PM
CheckpointFinishDistance50 kmArrival1:30 PMStop-Departure-

At Pine Gate, eight kilometres of moving takes 64 minutes, producing a 7:34 AM arrival. The five-minute stop moves departure to 7:39. Every later arrival includes that delay and the stops completed after it.

For what to eat between those stations, see the EnduranceOS 50K nutrition article.

Worked 50-mile plan

The second fictional race starts at 6:00 AM with a 12:00 elapsed goal. Four stops total 40 minutes: two routine ten-minute stops and two major ten-minute stops. The equal numbers are convenient for this demonstration; a real plan should budget from the actual task list.

Distance50 mi
Goal12:00
Stops0:40
Moving pace13:36/mi

Twelve hours minus forty stopped minutes leaves 11:20, or 680 minutes, for moving. Dividing by 50 miles produces a required moving pace of 13:36 per mile.

CheckpointDistanceArrivalStopDeparture
CheckpointNorth ForkDistance10 miArrival8:16 AMStop10 minDeparture8:26 AM
CheckpointRidge CrewDistance22 miArrival11:09 AMStop10 minDeparture11:19 AM
CheckpointLake Drop BagDistance34 miArrival2:02 PMStop10 minDeparture2:12 PM
CheckpointSouth GateDistance43 miArrival4:15 PMStop10 minDeparture4:25 PM
CheckpointFinishDistance50 miArrival6:00 PMStop-Departure-

The card reaches the exact target because Goal mode solved the moving pace after reserving all forty stopped minutes. If actual stops total one hour instead, the same 13:36 moving pace finishes twenty minutes later.

For what to eat between those stations, see the EnduranceOS 50-mile nutrition plan.

What the two plans make visible

Distance alone does not determine the stop budget. The 50K example reserves twenty minutes; the 50-mile example reserves forty. The longer plan therefore asks the runner to hold a faster moving pace than a calculation that ignores stops would show.

In either race, an early delay moves every later row. A ten-minute overrun at the first checkpoint does not disappear unless the runner later moves faster or spends less time stopped. The timing card makes that trade visible without pretending which response is safe or achievable.

Adapt the examples to a real race

  1. Replace the fictional distance and stations with the current official course values.
  2. Build stop budgets from the tasks at each station using the stop-time guide.
  3. Enter the race's local start date and overall cutoff.
  4. Compare departures with any intermediate cutoff that requires runners to leave by a stated time.
  5. Print the result, mark the source date, and recheck it when final instructions arrive.

Open the calculator to build your version. For a plan that crosses midnight, continue with the worked 100-mile example.

50K and 50-mile plan FAQ

What pace do you need for a 6-hour 50K?

Six hours over 50 km averages 7:12 per km (11:35 per mile) with stops included. With this page's 20 minutes of planned stops, the moving pace you need is 6:48 per km (10:57 per mile) over 5:40 of moving time.

What pace do you need for a 12-hour 50-miler?

Overall pace is 14:24 per mile (8:57 per km), stops included. With the 50-mile example's 40 minutes of stops, the moving pace you need is 13:36 per mile (8:27 per km) over 11:20 of moving time.

How much does extra stop time change the pace I need?

On a fixed goal time, every extra 10 minutes of stops makes the required moving pace 12 seconds faster per km on a 50K and 12 seconds faster per mile on a 50-miler. Going from 20 to 30 minutes of stops in the 7-hour 50K moves it from 8:00 to 7:48 per km.

What happens if my stops run long?

At the same moving pace, the finish moves later by the extra stop time. In the 50-mile example, an hour of stops in place of the planned 40 minutes moves the finish from Day 1, 6:00 PM to Day 1, 6:20 PM.