Should I Nap During a 100-Miler? The Data Decides¶
It's around mile 65. Somewhere between 2 and 3 AM. The second aid station of the night is behind you and the next one is a long way out. Your crew vehicle is parked ahead with a sleeping bag folded in the back, and you are standing in the dark asking the question you have probably asked yourself a hundred times in training but never out loud: should I stop?
The night-running post covered gear, light management, and what to do when the trail starts misbehaving visually. This post is the question underneath that one. It is not about surviving the dark. It is about whether the math favors stopping in it.
Here is what the research actually shows at the 100-mile distance, a decision rule tied to a single number you already have, and what to do before the start line that matters more than any in-race decision.
What the data actually shows at 100 miles¶
A Springer Nature study of 1,154 mountain ultramarathon finishers found that 83 percent of 100-mile finishers did not nap during the race. Not "most." Eighty-three percent.
The common assumption is that experienced or faster runners nap strategically, as if sleep management is an advanced technique that separates the field. The data shows the opposite. The runners who napped tended to be slower finishers, those who crossed the 28-to-30-hour range, not those who built in planned rest breaks to go faster. Napping was correlated with needing more time, not with gaining an edge. That is worth stating plainly, without any judgment attached to it: slower finish times mean more time in the dark, more circadian pressure, and more reason to stop. It is biology meeting circumstance, not a failure of preparation.
A separate Sage Journals study of 200-mile-plus finishers describes a completely different picture. At 200 miles, sleep is logistics. You plan it, schedule it, budget for it the way you budget aid station time. The two bodies of research are not interchangeable. A runner training for Leadville or Wasatch should not be making decisions based on what 200-mile finishers do, because the pressures, timelines, and decision contexts are different enough that the guidance does not transfer. This post is only about the 100-mile distance.
A 2025 ScienceDirect study on power naps during a 100-miler added the piece that makes the sub-30-minute rule meaningful: brief naps, under 30 minutes, provided measurable cognitive and alertness benefits. Longer attempts produced meaningfully worse outcomes, because waking from a full or partial sleep cycle mid-race leaves the brain in a grogginess state that costs more time than the nap saved. The mechanism is sleep inertia, and it is the reason duration matters as much as the decision to stop at all.
The finish-time threshold: which camp are you in?¶
The sleep question is not the same question for a runner finishing at 22 hours as it is for a runner finishing at 30. The difference is how many times you will move through the pre-dawn circadian low, typically falling between 3 and 5 AM, when cognitive performance and physical output drop together regardless of how much you have or haven't slept.
Here is the framework:
| Projected Finish Time | Circadian Lows Encountered | Default Plan |
|---|---|---|
| Under 24 hours | One (3-5 AM, night one) | Skip the nap |
| 24-28 hours | One, extended duration | Probably skip; use one if critically impaired |
| 28+ hours | Two (night one and night two) | Plan a 15-minute nap around mile 70-80 |
Under 24 hours. A sub-24 runner will hit the circadian low once, during the first night. Many will be through the worst of it before the second trough deepens. The time cost of a nap, plus the grogginess recovery afterward, is unlikely to be net-positive for this group. Keep moving.
24 to 28 hours. This is the genuinely ambiguous zone. Most runners in this bracket will pass through the 3-5 AM window once, feel the pressure, and emerge on the other side while still functional. The data shows the majority of them do not nap and finish. An unplanned stop is not wrong if a runner feels dangerously impaired at mile 75, but a planned nap is probably not necessary. Run the race, assess when you get there.
28 hours and beyond. The math starts to shift. A runner on a 28-to-32-hour pace will cross the pre-dawn window twice, operating on more than 30 hours without sleep before the finish. The research on this population shows that a brief, structured nap is net-positive for the final 10 to 15 miles. Net-positive means: the time cost of a 15-minute nap, plus 5 to 10 minutes of grogginess recovery, is less than the time cost of spending those same miles reduced to a shuffle. Knowing this in advance is the difference between a plan and a crisis decision at mile 72 in the dark.
One more piece of context from the data: the roughly 17 percent of 100-mile finishers who do nap correlate primarily with longer finish times, not with any particular race length or course profile. If your projected finish time is under 28 hours, you are statistically unlikely to need one and unlikely to benefit from planning one.
The intervention that actually moves the needle, and it's before the race¶
This is the part that competing guides skip, and the part that the research points to most clearly as the highest-leverage sleep intervention available to a 100-mile runner.
Sleep extension in the two weeks before a race: adding 30 to 60 minutes of sleep per night, consistently, meaningfully reduces how quickly cognitive performance degrades during the race. The runner who arrives at the start line carrying a sleep surplus is operating from a different floor than a runner carrying a deficit. The circadian low still hits. The second night still arrives. But the degradation starts from a better position.
Why does this outrank in-race nap strategy? A nap at mile 70 recovers roughly 15 to 20 minutes of alertness, at the cost of the stop time and the grogginess recovery. Two weeks of sleep extension can shift the baseline from which everything declines. It is not glamorous, and it is not complicated. Go to bed 30 to 60 minutes earlier than usual, for 10 to 14 days. That is the entire protocol.
The timing is favorable. Taper weeks typically drop training volume, which means evenings are less committed and earlier bedtimes are easier to sustain. The two weeks before the race are, logistically, the easiest two weeks to extend sleep.
What extension does not accomplish: it does not eliminate circadian lows. It does not mean you will sail through the second night. You will still feel the 3 AM trough. You feel it from a better position. That is the whole benefit, and it is a meaningful one.
If you do stop: the sub-30-minute rule¶
For runners in the 28-plus-hour bracket who plan a nap, the most important number is not where to stop or when. It is how long.
Sleep inertia is the grogginess state that follows waking from a full or partial sleep cycle. In normal life, you move through it and are fine in a few minutes. At mile 75 of a 100-miler, at 4 AM, with 25 miles still to go, sleep inertia lasting 15 to 30 minutes means 15 to 30 minutes of moving worse than you were before you stopped. A nap long enough to enter deep sleep is, in this context, counterproductive. The ScienceDirect study confirmed this directly: longer naps produced meaningfully worse alertness outcomes than shorter ones in the race setting.
The sweet spot, based on the research, is 10 to 20 minutes. Long enough to provide real alertness restoration, short enough to avoid crossing into deep sleep. A few specific things make this work in practice:
- Set an alarm. Do not trust yourself to wake up. You will not.
- Tell your crew. Set two independent wake-up points, the alarm and a crew member, not one. Single points of failure at mile 75 at 4 AM are not a plan.
- Lie down. Horizontal, eyes closed. The location matters less than actually getting off your feet. A sleeping bag in the crew vehicle, a chair leaned back in the aid station med tent, a foam pad in the grass. Whatever is available and horizontal.
- Walk for 3 to 5 minutes after waking. Do not try to assess how you feel the moment you stand up. The alertness benefit from the nap arrives on a delay, usually 5 to 10 minutes after waking. Move first, evaluate second.
For caffeine timing around a planned nap, that guidance is in the night-running post. Caffeine strategy and nap strategy interact, and that post covers both. The short version: there is a timing approach that makes a brief nap more effective, but it belongs in the post that already covers the full caffeine picture.
The night before and race morning¶
Most runners, having read everything else correctly, pull an accidental near-all-nighter on race eve from nerves. This is worth addressing directly, because it is extremely common and it has a clear answer.
One bad night at the end of a 14-night sleep surplus does not erase the surplus. Race-eve poor sleep is nearly universal among 100-mile runners. It is also not the catastrophe it feels like at 1 AM when you are staring at the ceiling. The body recovers meaningful rest from horizontal stillness even without full sleep. The two-week extension was the work. Race eve is not the moment to optimize anything.
What actually helps: going horizontal at a reasonable hour, even without the expectation of sleep. Not checking gear at 1 AM. Not running mental race simulations until 3 AM. Down early, phone away, lights off. Some sleep will come. If it does not, the two weeks before were the protection against exactly this.
Race morning: eat, hydrate, start. The window before a typical 6 AM gun is not the place to manufacture rest. The extension work is done or it is not. Either way, the runner is at the start line, and the question is finished.
Your number¶
Look at your projected finish time. That is the whole decision.
Under 28 hours: the data says keep moving. Eighty-three percent of 100-mile finishers did not nap, and most of them were in this range. Plan to push through the circadian low, brief as it is at the one-night mark, and save the time a stop would cost.
Over 28 hours: a single 15-minute stop somewhere in the mile 70-to-80 range is likely net-positive. Not because you failed to prepare, but because two circadian lows and 30-plus hours without sleep create conditions where brief structured rest returns more than it costs. Plan it now, tell your crew, set two alarms.
The pre-race piece: if your race is more than two weeks out, there is still time to run the sleep extension. Go to bed 30 to 60 minutes earlier tonight. Repeat for 10 to 14 days. That is the intervention with the highest return available to you, and it costs nothing except the evening hours you would have spent on something else.
If you have runs flowing into NavRun, generating a race plan is one click once the data is synced. Race-day strategy, including pacing and nutrition structure for your projected finish time, is on the paid side at navrun.app. For those who haven't connected yet, Strava or Apple Health on the iPhone app are both paths in.
You now have a number. The decision at mile 65 just got easier.