Itinerary
Planning Nepal: Your Body Sets the Schedule
Most countries let you trade money for time. Nepal does not, or at least not where it matters. You can pay for a flight that removes a day of road travel, a better room at the end of it and a guide who makes the whole thing easier — and none of that will let you walk to high altitude faster, because the constraint is not logistics or fitness but the rate at which your own physiology adjusts. That single fact should be the first thing that shapes a Nepal itinerary, and it is usually the last thing people think about.
Updated 2026-08-15
The one thing you cannot buy
The arithmetic makes the point better than any argument. The walking distance from the roadhead or airstrip to Everest Base Camp is not far by the standards of a fit hillwalker — a handful of days at an ordinary pace. Every genuine itinerary allows roughly twice that. The difference is not scenery stops or inefficiency; it is days deliberately spent not gaining height, because the body needs them to adapt, and the routes are designed around that need rather than around the map.
This reframes what a rest day is. On most trips a day without progress is a day lost, and the instinct when time is short is to cut it. On an altitude itinerary the rest day is doing the work that makes the rest of the trek possible, and removing it does not save a day — it removes the mechanism by which the trip functions at all. Travellers who compress an acclimatisation schedule to fit an annual-leave allowance are not being efficient; they are deleting the load-bearing part of the plan.
The corollary is that trek length is not really a choice. You do not decide how long Everest Base Camp takes; the route decides, and your job is to have enough days for it or to choose a different route. Which is a much easier decision to make at home than halfway up.
A week to ten days: stay low, and enjoy it
With about a week of usable days, the right answer is not a compressed high trek — it is a good low one plus the rest of the country. Shorter routes reach genuinely spectacular ground without the altitude that forces a long schedule, and the days you save go into the Kathmandu Valley's heritage or a few days in the lowlands, both of which most trekking-focused visitors skip and later regret skipping.
This is also the itinerary that survives contact with reality best. A short trek with no altitude dependency has no acclimatisation days to lose and no mountain-airstrip flight to be delayed by, so a bad-weather day costs you an afternoon rather than the trip. For a first visit with limited leave, it is a better trip than a rushed version of a famous one.
Two weeks: one classic trek, with the rest days intact
A fortnight is the band in which a classic high route becomes genuinely doable, and the discipline is to spend it on one thing. Choose the trek, take the schedule as written including every acclimatisation day, and accept that this is the trip — not a trek plus the valley plus the lowlands, all shortened to fit.
The temptation at this length is to bolt something onto the end. Resist it in the direction of the buffer instead: a fortnight with a two-day margin is a comfortable trip, and a fortnight scheduled to the last day is one weather delay away from missing an international flight. The most common Nepal planning failure is not choosing the wrong trek; it is choosing the right one and leaving no room around it.
Three weeks or more: the trek plus the country
Past about three weeks the trek stops being the whole trip and Nepal opens up considerably. This is the length at which the natural shape is a high route with its schedule respected, several days in the Kathmandu Valley either side of it, and a genuine stretch in the lowlands — which is the part of the country that most rewards the extra time, because it is the least like the mountains and the one visitors most consistently underestimate.
It is also the length at which the longer or more remote routes become sensible rather than punishing, and at which the restricted-permit regions start to make sense: they cost more, need a guide, and buy real solitude, none of which is worth it on a compressed schedule. Long-stay travel has its own logic here — visa extensions are generous enough that trekkers routinely base themselves in the capital or the lakeside town for weeks between routes, which is a genuine and long-established way to see the country rather than an eccentric one.
Where the buffer goes, and why both ends
The other structural constraint is weather, and it applies specifically to the mountain airstrips: flights to and from the high valleys are delayed or cancelled routinely, and this is normal operation rather than misfortune. The mistake is putting the buffer only at the start, on the reasoning that a delayed departure just shortens the trek. It also strands you at the far end, where a cancelled return flight can hold you in a mountain village for days with an international departure ticking down.
So the rule is slack at both ends, and the second one matters more. Practically: never book an international flight for the day after a mountain flight is due to return you, treat the last two days before departure as unallocated, and if you are on a fixed schedule choose a route that ends at a road rather than an airstrip. The mechanics of why the flights behave this way are on the getting-around guide; the planning consequence is simply that a Nepal itinerary is a fixed physiological pace in the middle with weather margin at both edges.