Training and where the estimates come from

The stage times on the schedule are not guesses from a calculator. Most of this course was ridden in the six weeks before the start, in pieces, and the planned durations are those measured efforts with an allowance added for riding them tired, in the dark, and back to back.

Ride data pulled from Strava on 12 August 2026. Moving time and stopped time are Strava's own split.

Course recon rides

DateRideMilesGain (ft)MovingmphStopped
2026-08-09Full stage simulation40.36,1826:226.31:08
2026-07-15Aqueduct 2 · stage 423.63,6253:167.20:22
2026-07-12Stage 3 Guyot partial · stage 319.42,7533:345.41:54
2026-07-12Segment 2 co trail · stage 242.25,8075:567.11:18
2026-07-11Breck epic stage 1 Penn creek · stage 138.15,5024:497.90:42
2026-07-03Firecracker course pre ride26.23,5533:108.20:08
2026-07-16Morning Ride (Guyot area)24.63,1693:187.40:14

Across these: 214 miles, 30,591 ft of climbing, 30:29 moving, averaging 7.0 mph.

How that becomes a 58-hour plan

Recon pace averaged 7.0 mph moving, on fresh legs, in daylight, one stage at a time. The plan does not use that number. It uses something slower, because the thing being estimated is not how fast a stage can be ridden — it is how fast the sixth one gets ridden after fifty hours.

Two adjustments carry most of the difference. Stages ridden at night, on the Colorado Trail and Aqueduct, are planned slower than they were ridden in July. And the stopped time is planned explicitly rather than absorbed: the schedule allocates it in named blocks, because the finisher traces show time off the bike is what separates a 31-hour finish from a 57-hour one.

Stages 5 and 6 are the softest numbers on the schedule. They were not ridden end to end in recon, so their durations are scaled estimates rather than measured ones — and they are also the last two stages, on the worst legs.