Night Running for Ultras

Why the night is its own skill

Watch the drop list at any mountain 100 and most of the names go up overnight. It is rarely because those runners ran out of fitness. As coach Jason Koop puts it, watching runners pull out at Leadville: he'd bet his bottom dollar that VO2 max and running economy have little to do with the choice to stop — what undoes people is the fear of the unknown, the disorientation of moving through the dark for the first time when you're already 20 hours deep and a little delirious¹.

The data backs up that the night is genuinely the hard part. In one study of a single-stage ultra, runners slowed by about 36% after sunset compared with their first-twelve-hours daytime pace, and the single slowest stretch of the whole race landed in the dead middle of the night². Sleep-deprivation symptoms are close to universal: in a study of 1,154 mountain-ultra finishers, 80% reported at least one symptom they attributed to sleep loss³.

So the skill you're building is not aerobic — it's the ability to keep moving, keep your footing, and keep making good decisions while tired and in the dark. The rest of this guide is about exactly that.

Lighting the trail

Your headlamp is the single piece of gear that most changes how fast and how safely you move at night. For trail, 200-300 lumens is a solid baseline. The product designer Timothy Gorbold frames the sweet spot as roughly 300 lumens with the ability to bump up to 500 or 800 for the technical bits — enough to light your surroundings while still casting the shadows you need to read the ground and place your feet with confidence⁴.

That word "shadows" matters more than the raw lumen number, and it points to the most useful trick in night running. A headlamp sits at eye level, so its beam runs almost parallel to your line of sight and throws almost no shadow — rocks and roots flatten out and you lose all sense of their height. A light mounted lower (on a waist belt) or carried in the hand hits the trail at an angle, and those angled shadows bring the terrain back into relief. Many runners pair the two: a waist light on its brightest setting to carve up the ground right in front of their feet, with the headlamp dimmer to see further down the trail⁵.

Plan around the tradeoff between brightness and battery, because it is unforgiving. More light helps you move faster, especially on technical terrain — but as lumens go up, battery life drops, fast⁴. And take Koop's warning to heart: most runners have no idea how long their light actually lasts on full power, and the runtime in the manual is optimistic¹. Find out in training, on the real setting you'll race.

Some lamps let you choose a beam pattern, and the two have distinct jobs: a focused spot beam throws light far down the trail for descents and rough ground, while a wide flood beam lights up the area around you for climbing and faster, easier running⁶.

Two more rules, both non-negotiable. First, carry a backup light. A headlamp can fail, run dry, or take a tumble off your head into the brush, and no one wants to descend a steep scree slope in the dark with no light⁴. Koop's standard is blunt: two headlamps, plus backup batteries for each¹. Second, plan a battery swap. Even a premium lamp kept on a medium-low setting only stretches through an 8-to-11-hour night — so if you're carrying a spare battery, a swap around 3 a.m. buys you a brighter last hour of darkness right when you need the lift⁴.

One thing not to count on: the moon. A bright moon on open, non-technical terrain is a genuine bonus and can let you drop to a lower setting and save battery — but treat that as luck, not a plan. Build your lighting for a moonless, overcast night, and anything the moon gives you is gravy.

The 2-4 a.m. low (the "witching hour")

There is a specific window, roughly 2-4 a.m., that Koop calls the "witching hour" — the time when you'd normally be in your deepest sleep, and the point on race night when you'll have to fight hardest just to stay awake⁷. This is your circadian rhythm, the internal clock that governs alertness, and it does not care that you signed up for a 100-miler. Expect to feel genuinely awful somewhere in that window. It is normal, and it passes.

You can see the low in the data. In the 1,154-finisher study, fully 80% of all in-race naps happened between midnight and 5 a.m., versus only 15% during daylight — the body forces the issue right at the circadian nadir³. And in the pacing study, after pace cratered through the night, it recovered to the runners' overall average at sunrise². That dawn lift is real and it is physiological, not just a mood swing — which is why "just get to sunrise" is legitimate race-night strategy, not a platitude. Koop deliberately times any nap so that waking lines up as close to first light as possible, using sunrise as a circadian reset⁷.

Here's the part that should change how you ride it out: at night your legs are mostly fine — it's your head that goes. Koop cites the research split: sleep loss costs an endurance runner only about 2-4%, but the hit to cognitive and skill-based tasks is much larger⁷. So in the witching hour you are not weak; you are impaired in judgment, alertness, and coordination. That reframing matters, because it tells you what to protect — your footing and your decisions — and it tells you the feeling is temporary. Keep moving toward the sunrise.

Caffeine and naps

Caffeine is the most reliable tool you have for the overnight, and the key is to save it for when you actually need it. Koop's protocol: hold off on all caffeine for roughly the first 24 hours of the race, then start deploying it after midnight when the sleep monster shows up, running up to about 100 mg per hour for three to four hours, and then easing off after sunrise so your natural circadian wake-up can take over⁷⁸. Holding it back early is what keeps it potent later — and if it doesn't wreck your sleep, cutting caffeine in the days before the race sharpens the lift you get when you reintroduce it⁷.

On dose, the performance range is about 3-6 mg per kilogram of body mass — roughly 225-450 mg for a 75 kg runner — and the peer-reviewed consensus from the International Society of Sports Nutrition agrees, noting the minimum effective dose may be as low as 2 mg/kg and that very high doses around 9 mg/kg simply aren't required⁹. More is not better: Koop flags 9 mg/kg and up as likely to impair you, bringing jitters, anxiety, an inability to focus, GI distress, and even heart-rhythm problems⁸. For the overnight specifically, small and steady beats one big slug, and the real danger is the dose quietly accumulating across many hours⁸. Caffeine takes roughly an hour to come on (gum and chews act faster), so dose ahead of the low, not in the middle of it⁹. And it's especially well suited to night running because its strongest documented effect under sleep deprivation is on exactly what fails at 3 a.m. — attention and vigilance⁹.

Naps are a real tactic, but the right kind depends on how long you'll be out there. On a one-night 100, the plan is usually to skip sleep entirely and get as far as you can, timing the finish-line push or any nap to sunrise⁷. What real fields actually do confirms this: 77% of mountain-ultra finishers napped at least once, but 82% of those naps were under 30 minutes, and total race sleep was tiny — on the order of a few minutes for a single night³. In an earlier survey, only about a fifth of ultrarunners had any sleep strategy at all, and when they did sleep it was overwhelmingly micronaps of 10-30 minutes¹⁰. So for most one-night 100s, a brief "dirt nap" of 5-20 minutes is a safety tool, something you reach for when you're microsleeping or weaving on the trail, not a scheduled event.

If your race runs into a second night, the calculus changes and a real nap earns its place. Koop's second-night nap is 40-60 minutes, because by then you're trying to recover cognitive function more than physical — and a too-short nap won't get you there⁷. Take it as a trail nap, not in an aid station: a space blanket or bivy on the ground, deliberately uncomfortable, because the warm chair and the drop bag are a trap that swallows races. When you wake, splash cold water on your face, take a caffeine dose, and get moving — nothing wakes you up like making progress down the trail⁷.

Pacing and safety in the dark

Slow down on purpose. The night is empirically the slow part of a 100 — that 36% post-sunset drop again — so planning to back off in the dark is correct racecraft, not a failure of will². Pushing your daytime pace through technical terrain you can barely see is how good runs end early.

Falls and disorientation spike at night, and the numbers are sobering: among 1,154 finishers, 15% reported a fall, 34% reported hallucinations, and 54% reported decreased alertness during the race³. The mechanism is the lighting problem compounded by fatigue — the dark strips away the shadow cues your gait relies on to judge the ground, while tiredness blunts your balance and coordination, so your foot lands on terrain you misread. The fix is conservative footing, a brighter setting on technical descents, and accepting that you will move slower.

Above all, remember where the real danger lives. Because your aerobic engine barely dims overnight while your judgment takes a much bigger hit⁷, the things that end races in the dark are bad decisions and falls, not a loss of power. One small wrong decision made on no sleep tends to cascade into a big mistake¹¹. So in the small hours, distrust your own problem-solving: don't make consequential choices you can defer, follow your plan, and watch your feet. If pacers are allowed for the night leg, use one — the conversation keeps your brain off the exhaustion and gives you a second set of eyes and a second judgment to lean on.

Rehearsing it in training

If your race goes through a full night, do at least one sunset-to-sunrise run before it. This is Koop's most emphatic point, and the instruction is refreshingly simple: run until the sun comes up again. There's nothing to run hard or fast — the entire goal is just to go through the night at an easy, conversational effort¹. One overnight run is what converts the dark from a terrifying unknown into something you've already done, and that alone removes most of the race-night anxiety.

Rehearse with your actual race kit and fueling, because the overnight run is the perfect time to stress-test gear in adverse conditions¹. Run your real headlamp, your real backup, and your real batteries, and learn their true burn time rather than trusting the manual. Eat and drink on your real race plan, including your caffeine timing. And if you can do it in cold or wet conditions you might hit on race night, even better. The other thing you're rehearsing is the circadian low itself — so that race night isn't the first time you've felt the 2-4 a.m. crater and proven to yourself that it lifts by dawn.

Treat the overnight run as the heavy stress it is. Do no more than one a month, place it early in a training block when you're not carrying much cumulative fatigue, count it as two days of running, and protect at least two recovery days afterward¹. In a plan, that means putting it on a down or recovery week within your race-specific build — never stacked on top of peak volume. Whether to do one at all comes down to a few things: do it if your race has a full night, your training is on track, and you reliably sleep eight-plus hours a night; skip it if the race has no real night, your training is behind, or you habitually sleep less than eight hours¹.

One last piece, with an honest caveat. Many runners "sleep-bank" before a 100 — Koop suggests sleeping more than usual for the few nights prior, aiming for around ten hours a night across the three nights before the race⁷. Going in well-rested is low-risk and almost certainly helps how you feel and how clearly you think in the small hours. Be straight with yourself about the limits, though: the largest study to look at it found that runners who extended their sleep beforehand did not actually finish faster than those who didn't³. So bank sleep because being rested can't hurt and likely helps your head — not because it's a proven way to run a faster time.