PCT Planning · Pace

Zero days and neros: how many rest days should you budget on the PCT?

Rest on a thru-hike isn't one thing, it's three, and they cost very different numbers of days. Working out how many zeros to budget is the question people ask — but the quieter choice, between a nero and a quick stop at each resupply, moves your finish date further than your entire zero budget does.

Both belong in a plan, because both are the difference between the date you put on a permit application and the date you actually walk out.

The three kinds of town stop

The vocabulary first, because it gets used casually and the distinctions matter:

• Zero. A day on which you hike no miles at all. A bed, a laundromat, and no walking.
• Nero. "Near zero." You walk a few miles — into a stop in the afternoon, or out of one in the evening — and the rest of the day is a shower, a resupply and a restaurant.
• Quick stop. In and out. Collect a box, buy four days of food, eat something hot, and walk on the same day. Most of the day is still walking.

On a 20 mile-a-day plan those look roughly like this:

What hikers actually do

Halfway Anywhere's annual survey has asked thousands of PCT hikers this for years, and the answer is stable: the mean and median number of zero days sits between 15 and 20. The average hike runs about 149 days, of which roughly 132 involve walking, at about 20.6 miles on the days they move. Hikers reach a resupply stop around every 98 miles, or every four to five days, for an average of about 27 stops across the trail.

The swing hiding in your resupply stops

Here is the part worth doing the arithmetic on. Take the survey's 27 stops and price them three ways:

That's a 13.5-day spread, decided one town at a time, usually in the moment, usually without anyone writing it down. It is larger than the gap between the low and high end of the zero-day range, and nothing about it feels like a decision when you're making it — it feels like getting a burger.

Why a nero is usually the better buy than a zero

Compare what you get. A zero buys you a full day off your feet, a bed, laundry, and every errand done. A nero buys you the bed, the laundry, the errands, the restaurant meal and the full night's sleep — and about five miles of trail.

The rest is nearly identical because the recovery happens overnight either way. What differs is that one of them moved you down the trail and one didn't. This is why experienced hikers often pair two neros — walk in late one day, walk out late the next — rather than taking a zero in between. You get two soft evenings and a full day in town, and you still made ten miles.

The honest exception is genuine recovery. If something hurts, a nero is not rest, it's a shorter day of walking on an injury. Tendons and feet need whole days with no load, and no amount of arithmetic beats not being injured in Oregon.

Zeros don't land evenly

Budgeting one zero a week and spreading them across the map is tidy and wrong. They cluster, for reasons that are mostly structural:

1. Kennedy Meadows. The end of the desert and the gateway to the Sierra, where bear canisters, ice axes and cold-weather kit get sorted out. A lot of hikers take their first real zero here, and it is often two.
2. The Sierra exits. Getting to Bishop or Independence means a pass and a long ride, so the trip out is most of a day in each direction. A zero in the middle costs three days of trail time in total, which is why people stack their errands.
3. Weather and fire. Snow that hasn't melted, a river running too high in the afternoon, a closure that reroutes you. These are unscheduled and they are the reason a plan with zero slack in it fails.
4. The body, around week three and again around month three. The first is trail legs arriving late; the second is accumulated fatigue. Both are common and neither respects your spreadsheet.

So how many should you plan?

A useful way to hold it: budget a rate, not a number. Roughly one rest day per week of walking lands you in the 15–20 range the survey reports, without pretending you know which weeks.

Two things worth saying plainly about that.

The first is that most hikers take more than they planned. If your plan has eight zeros in it and the trail-wide average is 15 to 20, your plan is not lean — it is optimistic, and the difference will show up as a finish date that slides all summer.

The second is that a rest day you never take is free. Budget the days, arrive at the finish early, and nobody minds. Budget none and you spend the hike doing arithmetic you did not want to do.

What this does to the rest of your plan

Rest days aren't a separate ledger. Every one of them pushes everything after it:

• Your permit end date. The application asks when you expect to finish. A finish date calculated with no rest days in it is out by two to five weeks, which is not a rounding error.
• Every mail-drop send-by date. Boxes are posted against arrival dates. Add a zero in week four and every box after it should have gone out later — which matters most for the ones someone at home is posting after you've left.
• Your food carries. A zero doesn't change the miles between stops, so it doesn't change how many days of food a carry needs — but a nero does shift which day you arrive, and that is the date printed on the box.