Bigfoot 200 2026: The Results, the Storm, and the Sleep Math¶
Aaron Kubala crossed the Bigfoot 200 finish line in 47 hours, 21 minutes, and 11 seconds. Aimee Warnke was the first woman in approximately 61 hours, 18 minutes, and 35 seconds. One hundred eighty-seven runners finished within the 107-hour cutoff, on a course that had already been rerouted by the time most of them were into their second night.
That is the short version.
Results at a glance¶
| Race date | August 14-18, 2026 |
| Location | Near Mount St. Helens, Washington |
| Distance | 200.1 miles |
| Elevation gain | 44,082 feet |
| Cutoff | 107 hours |
| Winner | Aaron Kubala |
| Men's winning time | 47:21:11 |
| First woman | Aimee Warnke |
| Women's winning time | approximately 61:18:35 |
| Finishers | 187 |
| Final finisher day | Tuesday, August 18 |
Rain hit the field within the first hours of the race and low cloud followed. Heavy storms pushed through the first two days and race management rerouted the course between the Blue Lake and Coldwater Lake aid stations. Every runner who finished in 2026 finished on a course that was not the one they had trained on.
The storm on the first two days¶
The race started Friday, August 14. By the time the field reached Saturday, the weather had already forced the reroute. That change matters beyond the weather story. When a 200-mile course moves, the crew access points a runner mapped during training no longer line up with where the actual runner will be. The aid station you planned to sleep at may be the one that no longer exists on the course. Time estimates built on the registered route now have wider error bars.
The 187 finishers absorbed that mid-race change. Finishers came through until Tuesday, August 18, four days and four nights after the start.
Aaron Kubala: 47:21:11¶
Kubala's winning time asks a quiet question: what does it take to cover 200.1 miles with 44,082 feet of gain in 47 hours and 21 minutes, through a field-wide storm reroute, on a night course?
He was already moving through the first full night on Friday before most finishers had found their stride. At 47 hours, there is roughly one sleep window, one real rest, and then continuous forward motion. Sub-14-minute miles for 200 miles over that terrain. The pace number hides how much of that performance came from planning rather than fitness.
Kubala is chasing the Triple Crown of 200s. He ran Tahoe 200 in June 2026 and set the course record there. Bigfoot is the second leg. Moab 240 follows in October.
Aimee Warnke: approximately 61:18:35, first woman¶
Warnke's finish is not a story about pace. It is a story about staying intact across 61 hours of race time and two full nights of running.
She is an Army physical therapist based in San Antonio. Before this race, she was diagnosed with a rare pelvic chondrosarcoma. Three months after that diagnosis, she won her first 100-miler outright. Not the women's division. Outright.
Warnke is also on the Triple Crown of 200s alongside Kubala: Tahoe done, Bigfoot done, Moab 240 in October.
At 61 hours, her race crossed Friday night into Saturday, then Saturday night into Sunday. Both circadian lows required decisions: when to sleep, for how long, and how to move afterward. Pace explains some of the gap between 47 hours and 61 hours. Sleep management explains most of the rest.
What 200 miles decides differently than 100¶
There is an existing post here on sleep strategy for 100-milers that draws one explicit boundary: it covers 100-mile distances only. At 200 miles, the framing changes.
At 100 miles, the sleep question is whether to stop at all. The data shows most 100-mile finishers do not nap. The answer for many is: hold your pace, use caffeine, survive the one circadian low.
At 200 miles, that question is already settled. You are going to sleep. The only variables are when, for how long, and how well you planned it before you started. Research on 200-mile finishers describes sleep not as a choice but as logistics: something you budget the way you budget aid station time or crew handoffs.
Runners who improvise the sleep schedule at mile 120 are making that call while exhausted, 20 or more hours into the race, in a different physiological state than they were at the start line. That is not the right moment for the decision. The right moment is before the race, using the data you already have.
What your training data shows about your sleep cliff¶
Your training history tells you where your personal performance cliff arrives. The cliff is the point where pace drops and cognitive function drops together. It is different for every runner. Most people find it during races by running into it. You can find it earlier.
Three things in your training log point to when the cliff arrives and how steep it is:
Your overnight run data. If you have run a 12-plus-hour effort that crossed into the night, your splits from 3 AM to 5 AM compared to your splits from 9 PM to 11 PM show how hard the first circadian low hits you. Runners who lose 30 percent of pace during that window tend to benefit from a planned stop before it arrives. Runners who hold within 15 percent can usually push through on caffeine.
Your baseline sleep over the last eight weeks. If your average nightly sleep is under seven hours, you are starting the race with a deficit. That deficit compounds faster over 200 miles than over 100 miles, because the exposure time is longer. Runners with chronic short sleep should plan their first stop earlier than a well-rested runner would.
How your body responds to long stops. Look at your training runs: when you sat for 30 minutes at an aid station during a long effort, how long did it take to move freely again? If you stiffen in 20 minutes, your sleep stops should be short and frequent, not one long rest that leaves you trying to restart a body that does not want to move.
A sleep schedule to build before you start¶
This is not a plan you can borrow from someone else's race report. Kubala's 47-hour architecture looks nothing like a 75-hour architecture. Warnke's two-night plan looks nothing like a three-night plan. The structure depends on your projected finish time, your personal sleep cliff, and the aid station locations on the course.
Here is the framework to build yours.
Step one: Find your degradation threshold. From your training data, identify how many hours awake you can cover before splits meaningfully collapse. The common range is 14 to 20 hours, but it varies.
Step two: Map the threshold against aid station locations. Where on the course will you hit that threshold? That location is your first sleep window. Not wherever you happen to feel tired.
Step three: Set a sleep duration before the race. A 60-to-90-minute planned stop at mile 100 costs less than an improvised 3-hour stop at mile 140 because you pushed past your threshold.
Step four: Plan the second window. Most finishers between 55 and 107 hours require two sleep stops. Plan both before the race. Adjust only if conditions clearly warrant it.
| Projected finish time | Nights in the race | Suggested sleep structure |
|---|---|---|
| 47 to 55 hours | 1 to 2 nights | 1 stop, 60 to 90 minutes, planned around hours 30 to 40 |
| 55 to 75 hours | 2 full nights | 2 stops, 60 to 90 minutes each, timed to the second night and the following dawn |
| 75 to 107 hours | 3 or more nights | 2 to 3 stops, 90 to 120 minutes each, with one unscheduled contingency built in |
Timing means arriving at a crew-accessible aid station 30 to 60 minutes before your personal circadian low, not after you have already fallen off the cliff. And each stop needs a fixed exit trigger: a time your crew holds you to, not a feeling you wait for. At mile 140, you will never feel ready to leave. "I leave at 75 minutes regardless" is the plan. Give it to your crew before the start.
The 2026 reroute adds one more variable worth naming: course changes widen the error bars on every time estimate you built in training. A sleep schedule that only works when everything goes to plan is not really a plan. Build in a 10-to-15-percent time buffer for each window and you will not have to recalculate under pressure.
What NavRun shows you¶
If you connect Strava to NavRun, your overnight training efforts are already there. Your activity history shows splits by time of day, so you can see where the slowdown happened and how sharp it was. That is the raw material for building a sleep schedule based on your history, not borrowed from a race report about someone faster or slower than you.
The 100-mile sleep post handles the decision at that distance. This framework is the 200-mile version. The inputs are your training data. The output is a plan you execute at mile 120, when you cannot build plans anymore.
Kubala ran 47 hours on a plan. Warnke ran 61 hours on a plan. One hundred eighty-seven runners finished on some version of a plan. The race begins long before Mount St. Helens.
If you are building toward a 200-miler and want to see your overnight training splits in one place, NavRun connects to Strava and pulls your full activity history.