The Breck Epic, and the Mega Epic

The Breck Epic is a six-day mountain bike stage race held every August in Breckenridge, Colorado. Six stages, each starting and finishing in town, on the trail networks around the Tenmile and Front ranges — roughly 217 miles and 34,805 feet of climbing across the week, most of it above 10,000 feet.

The Mega Epic is what happens when you stop treating those six days as six days. Same six courses, ridden end to end as one continuous effort, with the clock running through the nights and the sleep. It is a format that exists because riders kept asking whether it could be done at all.

What follows is the evidence base this ride was planned against: what the tracker traces of past finishers actually show, and what separates a 31-hour finish from a 57-hour one. The short version is that it is decided by time off the bike, not speed on it.

Event information and registration: breckepic.com
Podcast on the Mega Epic format: listen on Spotify

Past finishers — what the Raceflow traces show

Seven finishers across two tracker views. Solid = moving, dashed gaps = stopped. Your plan on the bottom row.

0h 6h 12h 18h 24h 30h 36h 42h 48h 54h 60h Chase Caughey 30.7h tracker gaps — stops not readable Jeff Kerkove 35h Chris Fisher 49h Yuki Ikeda 49.7h tracker gaps — stops not readable Chris Joice 53h Nora Fierman 53h Jesse Harodetsky 56.5h tracker gaps — stops not readable YOU — planned 57h19
  1. There are two events happening here, and nothing in between. Finishers cluster at 31–35 hours and at 49–57 hours. Not one rider landed in the fourteen-hour void between them. The fast group rides straight through; everyone else sleeps twice. That is a choice made before the gun, not a result that emerges during the race.
  2. The race splits in the first night, not the last day. In the clean traces every rider sits within a couple of miles of the others through hour 15, then fans out. Nobody rode away from anybody — they slept away from each other.
  3. Fierman rode faster than Fisher and finished four hours later. 6.0 mph against 5.2, and it bought her nothing: 17 hours off the bike to his 7. That single comparison is the whole 49–57 hour group.
  4. Caughey's 30.7 is the fastest number on the board — 7.1 mph overall for 217 miles and 34,805 feet. Worth knowing it exists; not worth chasing.
  5. Your projection sits at the back of the sleep-twice cluster, by minutes. 57h19 against Harodetsky's ~56.5. You are inside the pack, not off the back of it — and you are the only one here with a written stop plan.

Riding pace vs. stopped time

217 miles, 34,805 ft. Overall speed is the finish line; riding speed backs the stops out. Stops read off the traces — treat as ±1h, and only where the tracker was continuous.

RiderFinishStoppedRidingRiding speedOverall
Chase Caughey30h42——not readable7.1 mph
Jeff Kerkove35h~2h~33h6.6 mph6.2 mph
Chris Fisher49h~7h~42h5.2 mph4.4 mph
Yuki Ikeda49h42——not readable4.4 mph
Nora Fierman53h~17h~36h6.0 mph4.1 mph
Chris Joice53h~13h~40h5.4 mph4.1 mph
Jesse Harodetsky~56h30——not readable3.8 mph
You — planned57h1912h2843h365.0 mph3.8 mph

Why three rows say "not readable." Caughey, Ikeda and Harodetsky's traces each contain vertical jumps — 40 to 80 miles gained in essentially zero elapsed time, which is physically impossible. Those are InReach dropouts, and the long plateaus sitting next to them are the same gaps seen from the other side. Harodetsky's trace would imply 31 hours stopped and 25 hours riding at 8.7 mph; it simply isn't real data. Their finish times are solid. Their stop patterns are not, and averaging them in would poison the comparison.

What this means for the plan. Your projected riding pace of 5.0 mph sits inside the range of every clean finisher (5.2 / 5.4 / 6.0). You are not slow — you are budgeting 12h28 off the bike, which lands between Fisher's 7h and Joice's 13h. Trim toward Fisher and the same legs finish near 51 hours. That is the entire lever, and it is a kitchen-timer problem, not a fitness one.