Calculator

Overnight example

A worked overnight 100-mile aid-station plan

In this worked 100-mile example, a 16:00 per mile moving pace takes 26:40, and four stops totaling 1:20 bring the finish to 28:00. From a 6:00 AM start, that's Day 2, 10:00 AM, two hours inside a 30-hour overall cutoff. The card prints Day 1 or Day 2 on every clock time, so overnight arrivals stay in order.

Last updated November 19, 2026

Example inputs

This fictional 100-mile race uses Pace mode. The expected average moving pace is 16:00 per mile. Four stations at miles 20, 40, 60, and 80 have stops of 10, 20, 20, and 30 minutes. The race starts at 6:00 AM and has a 30-hour overall cutoff.

Distance100 mi
Moving pace16:00/mi
Stops1:20
Cutoff30:00

One hundred miles at 16:00 per mile is 1,600 minutes, or 26:40 of moving time. Adding 1:20 of planned stops produces a 28:00 elapsed finish: Day 2 at 10:00 AM.

The overnight checkpoint schedule

CheckpointDistanceArrivalStopDeparture
CheckpointRiverDistance20 miArrivalDay 1, 11:20 AMStop10 minDepartureDay 1, 11:30 AM
CheckpointRidge CrewDistance40 miArrivalDay 1, 4:50 PMStop20 minDepartureDay 1, 5:10 PM
CheckpointNight CampDistance60 miArrivalDay 1, 10:30 PMStop20 minDepartureDay 1, 10:50 PM
CheckpointLake Drop BagDistance80 miArrivalDay 2, 4:10 AMStop30 minDepartureDay 2, 4:40 AM
CheckpointFinishDistance100 miArrivalDay 2, 10:00 AMStop-Departure-

The Day 2 labels matter. A card that only says 4:10 AM and 10:00 AM can be misread as start morning. The date entered in the calculator lets the printed card keep those overnight events in order.

Overall buffer and intermediate cutoffs

The 30-hour overall cutoff occurs at Day 2, noon. A 28-hour projection therefore shows a two-hour buffer.

overall cutoff buffer = 30:00 - 28:00 = 2:00

That buffer does not prove every intermediate cutoff is safe. A race may require departure from Night Camp by 10:45 PM, for example. This plan arrives at 10:30 but departs at 10:50 after the planned stop, so it would miss that fictional departure cutoff even though the overall finish remains under 30 hours.

Use the official cutoff definition.

If the runner guide says "must leave," compare the rule with departure. If it says "must arrive" or defines another process, follow that exact language.

Make night tasks explicit

Overnight stops often contain more work than daytime refills. The example gives Lake Drop Bag thirty minutes because it may include layers, lighting, food, and a deliberate reset. That is a planning assumption, not a recommended duration.

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

  • Lighting: decide where the primary light comes on and where spare power is accessed.
  • Layers: pack the clothing change in the order it will be used.
  • Drop bag: label the required items and separate them from optional extras.
  • Crew cue: give crew the planned departure time and the short task list.
  • Day label: print Day 2 beside every after-midnight checkpoint.

Rehearse the sequence and revise the stop budget using the stop-time guide.

Compare clean and delayed scenarios

A baseline becomes more useful when it is compared with one plausible delay. If Lake Drop Bag takes 50 minutes instead of 30, total stopped time becomes 1:40 and projected finish becomes 28:20. The overall buffer falls from 2:00 to 1:40.

If the moving pace also slows, change the pace in a second copy of the plan. Do not silently assume the original 16:00 pace will recover every delay. The calculator is deliberately simple, so scenario comparison requires changing one visible input and reading the new card.

Baseline28:00 finish

16:00/mi moving pace and 1:20 stopped.

Long final stop28:20 finish

Same moving pace and 1:40 stopped.

Build your own overnight card

  1. Enter the official total distance and local start date.
  2. Choose Goal mode when the finish target is fixed, or Pace mode when you are testing an expected moving pace.
  3. Add stations in course order with cumulative distances and rehearsed stop budgets.
  4. Enter the overall cutoff and compare every official intermediate rule with the correct arrival or departure column.
  5. Print the card, verify Day 2 labels, and recheck the current runner guide during race week.

Use the aid-station calculator to build the schedule. For the full input workflow, read how to build an ultramarathon aid-station plan.

100-mile aid-station plan FAQ

Can you miss a checkpoint cutoff while on pace for the finish?

Yes. This example finishes two hours inside its 30-hour cutoff, yet it reaches Night Camp at Day 1, 10:30 PM and leaves at Day 1, 10:50 PM after a 20-minute stop. A leave-by cutoff of Day 1, 10:45 PM there would be missed.

How much does one long overnight stop change the finish?

At the same moving pace, each extra stopped minute adds a minute to the finish. Stretching the mile-80 drop-bag stop from 30 to 50 minutes moves the finish from Day 2, 10:00 AM to Day 2, 10:20 AM and cuts the overall buffer from 2:00 to 1:40.

Why does the pace card say Day 2?

The planner adds a day label to every clock time, counted from the start date you enter. In this example the mile-80 arrival prints as Day 2, 4:10 AM, so a crew member can't mistake it for 4:10 AM on race morning.

Does the planner slow your pace for night running?

No. One average moving pace covers the whole race. For a slower night, enter a slower pace and print a second card to compare its finish and buffer.