Loading...
Race Prep

The 20 Days Between Leadville and Wasatch

Ike Lacey August 7, 2026 9 min read

The Grand Slam's Hardest Seam: Leadville to Wasatch

Leadville finishes at mile 100.2 on August 22. Wasatch starts at mile 0 on September 11. Between those two finish lines sits 20 days, two recovery arcs that will not complete in time, and one question that belongs in a planning session now, not at mile 60 of Wasatch: am I ready enough to start?

The word "recovery" is doing the wrong work here. Full recovery from a 100-miler takes four to eight weeks. Nobody who finishes Leadville on August 22 will be fully recovered on September 11. The runners who navigate this seam cleanly are not the ones who recovered fastest. They are the ones who stopped trying to recover and started managing damage instead.

This is that 20-day window. What it contains, what the body is doing in it, and the week-by-week questions that tell you whether you are on track for the Wasatch start line.


The goal is not full recovery

Full recovery and "ready enough to start Wasatch" are two different goals with two different timelines. If you are treating them as the same thing, the 20-day window will always feel impossible.

Here is the distinction that matters:

Goal Timeline What it means for this window
Full recovery from Leadville 4 to 8 weeks RBC counts normalized, CK back to baseline, connective tissue fully repaired
Ready enough to start Wasatch 20 days Structural damage managed, mobility intact, gut and sleep functional, legs that can cover Wasatch's first 20 miles

The Wasatch Front 100 starts at Kaysville, approximately 4,200 feet. The course climbs to roughly 9,900 feet at its peak and accumulates around 24,000 feet of total gain over 100 miles. The first 20 miles are moderate trail with manageable climbing. The hardest sections come late in the race, not in the first four hours.

That matters for how you set the goal. A runner who reaches the Wasatch start line with working legs, functional gut, and reasonable sleep does not need to have fully recovered from Leadville. They need to have managed the damage well enough to get through the gentle opening before the real demands arrive. Leadville starts at 10,152 feet and crosses Hope Pass at 12,600 feet. Wasatch opens at less than half of that altitude. The two races are not the same physiological ask, even when the distance says they are.


What is happening in your body right now

The post-100 recovery timeline is documented in detail in Why You Still Feel Flat Weeks After a 100-Miler. The short version: red blood cell damage from footstrike is significant after a 100-miler, and CK elevation from muscle breakdown typically takes three to four weeks to normalize. That is the standard post-100 picture.

The altitude-compounded version looks like this:

Days after Leadville What the body is doing What it means for Wasatch prep
Days 1 to 3 CK at or near peak, RBC damage high, sleep still disrupted from race effort True rest only. No testing. Appetite may still be suppressed.
Days 4 to 7 CK beginning to trend down, appetite returning, body starting structural repair Eat when appetite returns. Walk. Flat terrain. Nothing strenuous.
Days 8 to 14 Feeling "almost fine." This is the deceptive phase. The feeling returns before the structure is repaired. Connective tissue lags muscular recovery by several days.
Days 15 to 20 Final decision window. The body's functional signal is now visible. One honest test of the legs. Travel logistics. Loading carbohydrates.

One note specific to the Leadville position in the Slam: sleep at altitude is measurably different from sea-level sleep. Slow-wave sleep is reduced above 8,000 feet, which means the nights during and immediately after Leadville are doing less recovery work than the same hours at lower elevation would. This compounds the standard post-100 recovery timeline for everyone finishing the race there.

The runners who come out of Days 1 to 7 feeling "almost fine" at Day 8 should read that signal carefully. The feeling is real. The structure has not caught up yet.


Stay at altitude or come down

This is the geography decision that lives inside the 20-day window for every runner who finishes Leadville and is heading to Wasatch. Nobody has written about it specifically, but it has a real answer.

The case for staying in Colorado. Staying at altitude, whether in Leadville, Boulder, or Denver, keeps the body in an EPO-stimulating environment. Altitude exposure is genuinely good for endurance athletes. The problem is timing: meaningful hematological adaptation takes two to three weeks. The 20-day Leadville-to-Wasatch window produces minimal new red blood cell benefit for Wasatch. The EPO argument for staying at altitude is real in the abstract, but too short here to matter much in practice.

What altitude does do during this specific window is compress sleep quality. If you are sleeping at 10,000 feet, you are recovering slower than you would at lower elevation. The days when recovery speed matters most are Days 1 through 7, and those happen wherever you are.

The case for coming down. Dropping below 5,000 feet accelerates cellular repair and improves sleep architecture during the critical first week. The cost is re-acclimatization before Wasatch. The Wasatch start is at Kaysville, 4,200 feet. Arriving at the start area 48 to 72 hours before the race, which is the minimum useful acclimatization window as covered in Racing Ultras at Altitude, gives the body enough time to begin adjusting before the opening miles.

Here is what makes this decision easier: the Wasatch course's gradual first 20 miles provide a natural acclimatization arc within the race itself. The early climbing is real, but it is not Hope Pass. A runner arriving from low elevation with 48 hours of re-exposure has more going for them than a runner who stayed at 10,000 feet but slept poorly for 20 days.

This is not a prescription. If your life is in Colorado, staying there is reasonable. If you can get lower for Days 1 through 14 and return to the Wasatch start area around Day 18 or 19, the recovery math tilts in your favor. Your situation makes the call.


A framework for the 20 days

This is not a training plan. It is a set of questions by week, each with a signal that says you are on track and one worth pausing on.

Period Primary focus What to do On track Worth pausing on
Week 1: Days 1 to 7 Structural damage window. True rest. Sleep. Eat aggressively when appetite returns, specifically protein. Walk flat ground. No running. No testing the legs. Appetite returning by Day 4 to 5. Sleep quality trending up. Soreness localizing rather than spreading. Still systemically inflamed at Day 7. Feet or ankles with unresolved swelling. Sleep not improving by Day 6.
Week 2: Days 8 to 14 Reintroduce vertical. Test the structure; do not stress it. 45 to 90 minute hikes with 1,000 to 2,000 feet of gain. Power hike pace, not running. By Day 12 to 13, a short flat run (30 to 40 minutes) if hiking has gone cleanly. Hiking feels like hiking, not surviving. HR normalizing relative to effort. No new pain patterns. Legs cramping on descents. HR still elevated 15 to 20 beats above normal for equivalent effort at Day 12.
Days 15 to 20 Confirm or reconsider. Travel. Final call. One hike with vertical to confirm the legs still work. No heroics. Begin loading carbohydrates. Shift focus to Wasatch's opening 20 miles. Can cover 15 to 20 miles of hiking with 3,000 to 4,000 feet of gain and feel tired but structurally intact after. Persistent limp. Tendon pain. Inability to move at moderate pace on a descent.

The table is a framework, not a protocol. A runner who reaches Day 8 feeling better than expected can move earlier than the table suggests. A runner still inflamed at Day 7 needs to adjust, not push. Your body has better information than any table does.


How to know if you are ready enough to start

The test is not whether you feel good. Slam runners will find a reason to feel good at Day 18. The test is functional.

Ask these five questions in the week before Wasatch:

  • Can you complete a 2-hour hike with at least 2,000 feet of gain and feel tired but structurally intact at the end?
  • Can you run four flat miles at an honest easy effort and have your heart rate return to baseline within five minutes of stopping?
  • Has sleep been consistently useful for at least three nights in a row?
  • Can you descend a steep trail without favoring one leg, modifying your stride, or managing pain?
  • Is your gut handling normal food reliably?

Five yes answers means you are ready enough to start Wasatch.

Four yes answers with a borderline fifth is likely ready enough, and the judgment call is yours.

Three or fewer yes answers is worth a serious conversation with yourself about what the Slam means to you and what a Wasatch DNS versus a Wasatch DNF at mile 40 with structural injury means for the season beyond September 11.

The DNF calculus is different here than in a standalone 100. Finishing the Slam means finishing Wasatch. A DNS at Wasatch after finishing Leadville is a hard thing. It is also not the worst outcome available. Starting and DNFing with an injury that takes the fall season with it is the one you want to avoid.

No guilt in either direction. This section is about having the information to make the choice, not about which choice is right. Only you have the data on what your body does when it is operating at 70 percent.


What people who have done this more than once actually do

The Grand Slam community is small enough that accounts from repeat finishers are findable. Around 300 runners have ever completed the Slam. The ones who have written about this window show a pattern that diverges from what sounds right.

Ian Sharman, one of the most documented Slam runners in the record, has described hiking 15 to 20 miles with significant vertical in the week before Wasatch, rather than running. The rationale is direct: hiking maintains the neuromuscular patterns for altitude climbing and descending without adding eccentric load from running downhill. The legs stay engaged without taking additional damage.

The composite picture from finisher accounts looks like this. Almost nobody runs in Week 1. Almost everybody reintroduces hiking in Week 2. Almost everybody does one short run in the final few days to confirm the legs still work. And almost nobody runs long in Week 2.

The runners who have come undone in this window consistently describe the same thing: trying to get some miles in too early. The feeling at Day 8 or 9 is often genuinely good. The structure that feeling is built on is not as ready as it feels. A 10-mile run at Day 9 can cost a runner a week of additional recovery time they did not have to give.

Food priority appears consistently across accounts. Caloric surplus in Week 1, specifically with protein for structural repair. The appetite suppression that often follows a 100-miler is a signal about what the gut can handle in that moment, not a goal to sustain. Eat when it comes back. Eat more than feels necessary.

The Slam community is worth finding and spending time with in this window. The runners who have been through this seam before are out there, and they are not hard to reach.


Your Leadville data is already in the plan

When Leadville flows into NavRun, the training plan sees it. Not as an entry to fill in, but as a signal: a 100-mile effort at altitude with the specific load profile your body just completed. The plan adjusts around it. Your history at altitude, your recovery patterns from previous long efforts, your current load in the context of the whole season, all of it is already there.

If your runs are not flowing in yet, connecting Strava or Apple Health at navrun.app takes a few minutes. Once the data is in, the plan knows where you are.

The 20-day window is a narrow one. The runners who use it well are the ones who let their own data show them how the recovery is actually going, not how they want it to be going. That is the only information that matters between Leadville and Wasatch.

Try NavRun

Training plans built around your recent running. Free for runners.

Get Started Free
Share