How to Train for a 200 Mile Race

Think in hours, not miles, because terrain and hiking blow up any mileage number. Most finishers build on a sustainable base of roughly 8 to 10 hours a week and peak somewhere around 14 to 18-plus hours in their biggest weeks, which often lands in the 50 to 80 mile range depending on how much vert and hiking is in there. The honest truth is that consistency over many months beats any single huge week, because you simply cannot train your body to feel like mile 150 of a 200. So the goal is to show up durable and uninjured, not to have logged one heroic 100 mile week. If you can only safely hold 8 hours, peak nearer 12 and lean harder on smart back-to-backs.

Give yourself a real runway: about 6 months of focused training if you already have an ultra base, and more like 8 to 12 months if you are coming up from shorter races or rebuilding. A 200 punishes rushed builds, because the durability you need is made slowly, over months of consistent volume and back-to-back blocks, not crammed into a few big weeks. Inside that window you want a base phase, a build phase where vert and back-to-backs ramp, a peak with your biggest blocks, and a 2 to 3 week taper. Back off roughly every fourth week so your body can absorb the work. If you are getting hurt trying to hit the volume, your timeline is too short, not your toughness too low.

Back-to-backs are the cornerstone of a 200 build. You run a long, harder effort one day, then get up the next morning on tired, sore legs and go long again, usually easier and more hike-heavy. The point is not the single distance, it is teaching your legs, your gut, and your head to keep moving forward when they are already trashed, which is exactly what mile 120 onward feels like. A common pattern is a longer Saturday followed by a Sunday long hike-run focused on forward motion, not speed, and you schedule these big blocks every two to three weeks because they are taxing to recover from. As you peak, stretch one or two of them into three-day blocks. Do them on terrain like your race, with your real fueling and your real pack.

Way less than you would guess, and it is intensely individual. In a published case study of 200-mile finishers, runners averaged only about 4.7 hours of total sleep across a race that took roughly 82 hours, taken in about 5 short bouts, and most did not even lie down for the first 20-plus hours. Plenty of fast runners get by on far less: famous wins have happened on two or three naps of just a few minutes each. The move is to plan your sleep the way you plan your fueling: decide roughly where you will sleep, default to short 5 to 20 minute dirt naps when you feel the drowsiness coming, and keep a longer 45 to 90 minute reboot in your pocket for when the wheels are really coming off. Sleeping a little, early and on purpose, beats death-marching while you hallucinate.

First, expect them. Mild visual hallucinations (rocks that look like animals, faces in the trees, a person who is not there) are extremely common deep in a sleepless night and are usually harmless. The fix is almost always sleep, not pushing through: a 5 to 20 minute dirt nap will often clear them out, and that is faster than grinding to the next aid station hallucinating. Caffeine helps for a window, and so do simple things like eating, fixing your light, and getting a pacer next to you to keep you safe and on-trail. The danger is not the hallucination itself, it is the bad decisions and the falls that come with a fried brain, so when your judgment or balance starts going, that is your signal to lie down, not to be tough about it.

Your crew is your pit stop, your pacers are your copilots, and at 200 miles both are huge. Give every crew member a role and a checklist so a stop is fast and repeatable: one person on food and bottles, one on feet and layers, one tracking what you said you would do at this stop. Aim to keep stops short and purposeful (think 10 minutes, not a half hour of chatting) because those minutes add up to hours over three days. Pacers, allowed on the later sections of most 200s, keep you moving, keep you on the marked course, talk you through the lows, and make sure you do not lie down in a ditch or quit on a bad patch. The best crews also watch you objectively and catch your decline before you do.

Shrink it. Nobody can hold 200 miles in their head, so you run aid station to aid station, or even just to the next ridge, and let the finish take care of itself. Go in expecting the low points instead of being shocked by them, because the dark patches are guaranteed and they pass, especially after you eat, sleep a few minutes, and the sun comes up. Have a tiny reset routine for when it gets bad: eat, drink, fix your feet, sort your layers, decide if you need to sleep, then move to the next station. Train this on purpose by doing some long runs tired and at night so the feeling is familiar, not new. And nail down your real why before the start, because that is what is left when the legs and the fitness have nothing more to give.

The fitness base is similar, but a 200 adds two whole problems a 100 mostly lets you ignore: multi-night sleep deprivation and many more hours of cumulative damage. So the training shifts from peak fitness toward durability and logistics. You add more and longer back-to-back blocks (and some three-day blocks), you actually rehearse night running and a sleep strategy, and you build and brief a crew and pacer system instead of winging it. Coaches often add only modestly more weekly volume than a 100 build, on the order of 10 to 15 percent, because the limiter is rarely raw fitness. It is whether your body, your stomach, and your mind can keep going for two or three days with almost no sleep.