Is Your Trek Itinerary Too Fast? How to Read an Ascent Profile Before You Book

You have the PDF open. Fourteen days, a paragraph each, walking hours, a difficulty rating, and somewhere in each entry a number in meters. The photographs are good. The pricing is clear. And when the person interpreting that column for you is also the person selling the trek, you are hearing the answer from someone with a commercial stake in how short it stays.

That column is the part of the document you can compare with published ascent guidance, and the comparing is arithmetic anyone can do. This article is about how. It is not about diagnosing or treating altitude illness, and if you are looking for symptoms or what to do about them, a doctor who works in travel or altitude medicine covers what an itinerary never can. RoamWell sells no treks and recommends no operators, which matters more here than it usually would.

None of it asks you to know anything about altitude physiology, only to subtract one number from another. And if you have already booked, the same work still tells you what to ask before you go.

The 30-second answer

A trek itinerary can be checked before you pay, on paper, using one column of numbers: the elevation you sleep at each night. Published guidance sets figures for how fast that number should rise, and comparing your itinerary against them takes four calculations and about fifteen minutes. What comes out is a list of questions for the operator, not a verdict on the trip.

• The only number that goes in: sleeping elevation, not the day's high point
• Check 1, per night: above 3,000 m, does any night raise it by more than 500 m?
• Check 2, the run: how many nights in a row gain elevation with no night off?
• Check 3, cumulative: how much does one unbroken run add up to, against a reference of an extra night per 1,000 m?
• Check 4, the average: total gain divided by the number of gaining days, against 500 m
• A rest day only counts if the sleeping elevation does not rise, whatever the itinerary calls it
• Night zero matters: where you slept before day one, which on a fly-in trip is often the largest jump of the whole trip
• What it cannot do: tell you anything about yourself. It reads the itinerary, not the traveler

What an ascent profile is, and why it is the one part of an itinerary you can check

Strip a trek itinerary down and most of it turns out to be unfalsifiable. "Moderate" is a word, not a measurement. "Six to seven hours of walking" varies by group and weather. "Stunning views" is not a claim anyone can be wrong about. None of it can be compared between two quotes in any rigorous way.

The sleeping elevations can. Every night of the trip has a number attached, that number is either published or it is not, and once you have the sequence you can compare it with figures that expert bodies publish openly. That sequence is the ascent profile: not the mountain's shape, but yours, plotted as where you sleep each night. Some sources call the same number sleeping altitude, which means exactly what sleeping elevation means here. An elevation profile is a different animal: on most trekking pages that is a distance-against-height chart of a day's walking, which describes the terrain rather than what your body has to sleep at.

Look at what the diagram does with night three. It tops out at 4,600 m during the day and comes back down to 3,900 m to sleep. On the profile, that day is a 50 m gain. The high point is real, it is on the itinerary, and it is not what the published figures measure.

The planning figures the guidance actually gives you

The four figures below come from clinical guidance written for planning, not from anything invented here. The Wilderness Medical Society published its most recent update to its acute altitude illness guidelines in 2024, and grades gradual ascent a strong recommendation on moderate-quality evidence. The CDC Yellow Book restates the same framework for travelers in plainer language.

No more than 500 meters a night, above 3,000 meters

Once your sleeping elevation is above 3,000 m, the WMS 2024 guidance references not increasing it by more than 500 m from one night to the next. Below that line the figure does not engage, which is worth saying explicitly: a 1,400 m jump that ends at 2,600 m is not measured by this rule at all.

A night without gain, every three to four days

The same guidance references a rest day every three to four days, and defines it in a way most itineraries do not: a rest day means no ascent to a higher sleeping elevation. Whether you walk that day is beside the point.

An extra night per 1,000 meters, and where the first night sits

The CDC Yellow Book, summarizing the same WMS recommendations for travelers, carries two further conditions. One is an additional acclimatization night for every 1,000 m of sleeping-elevation gain, which catches profiles that never break 500 m in a night but climb steadily for a week. The other applies at the very start: coming from below 1,200 m, avoid a first night above 2,750 m.

Figure	What it says	Engages when	Source
500 m per night (1,650 ft)	Sleeping elevation should not rise more than this from one night to the next	Sleeping above 3,000 m (9,800 ft)	WMS 2024
Rest day every 3 to 4 days	One night with no increase in sleeping elevation	Sleeping above 3,000 m	WMS 2024
Extra night per 1,000 m (3,300 ft)	An additional acclimatization night for each 1,000 m of sleeping-elevation gain	Above 3,000 m	WMS 2024, via CDC
First night below 2,750 m (9,000 ft)	Avoid going straight to a sleeping elevation above this from below 1,200 m (4,000 ft)	Start of the trip	WMS 2024, via CDC

Everything in this article is in meters, because that is how itineraries and the published guidance both state it. The feet values above are CDC's own.

Two cautions go with those figures. They are recommendations published by expert bodies for general planning, not thresholds of safety, and CDC says so directly: they can still be too fast for some travelers and too slow for others. They are also written for people coming up from low elevation: CDC's own table notes that the ascent figures assume a starting elevation below 1,200 m. Plenty of readers live above that already, in Quito or Bogotá or Addis Ababa or Denver, and if you do, the arithmetic still describes the itinerary accurately but the thresholds were not written with you in mind. Which way that cuts for any individual is not something an itinerary check can answer.

Where the sources disagree, and why that matters

If the four figures above looked settled, it is worth seeing them next to each other.

Body	Per-night figure	Rest-day wording	Notes
WMS (2024 update)	500 m	Every 3 to 4 days	Also frames it as a trip average
CDC Yellow Book	500 m	Extra night per 1,000 m gained	Restates WMS, and states the first-night condition
UIAA Medical Commission	300 to 500 m	Every 3 to 4 days, plus per 1,000 m	Lower bound is 300 m, not 500 m
NaTHNaC (UK)	500 m, averaged across the trip	Every 3 to 4 days	Defines the altitude bands

The UIAA's range is the one that should change how you read all of this. One gives a 500 m ceiling and another a 300 to 500 m range, which means a night at 480 m of gain sits comfortably inside one figure and above the bottom of the other. WMS and CDC also express the rest-day idea differently, and on a real itinerary those two wordings catch different nights.

The practical consequence is that this check produces three outcomes, not two. A night can be within the figure, above it, or too close to call. A rule can also simply not apply, which is not the same as passing it. Treating "we checked and it was fine" and "that rule never engaged" as the same result is how a check ends up saying more than it knows.

This article uses WMS 2024 as its primary framework, with CDC as the plain-language restatement, because that is the graded clinical guideline the others cite and because it supplies both the per-night figure and the trip average the method needs.

The check, step by step

Four calculations, done on one table you build yourself. Call it the ascent profile check, since it needs a name.

The thresholds it tests against are not ours. They are the published figures in the table above, and they belong to the Wilderness Medical Society and the CDC. The procedure is ours. Those bodies say how fast sleeping elevation should rise. Neither of them publishes a way to take the itinerary sitting in your inbox and work out whether yours does, and that is the gap the steps below fill. They explain the logic first and give the arithmetic after it, because the arithmetic is the easy part.

Build the table, and get night zero right

Open the itinerary and copy out four things per day: the night number, the place you sleep, the sleeping elevation, and the day's stated high point if there is one. Throw away the rest. Walking hours, distances, meal plans and difficulty ratings are not inputs to anything here.

One row matters more than the others and is the one most people fill in wrong. Night zero is where you slept the night before the itinerary's first night. Not the trailhead. Not the airport you landed at. Wherever you actually slept on the night before day one. If you flew from sea level to a city at 3,400 m and started walking the next morning, night zero is 3,400 m and the first night of your trek is not the first altitude event of your trip.

Night	Place	Sleeping elevation	Change from last night	Above 3,000 m?	Gaining night?	Outcome
0	where you slept before day 1		not applicable			baseline
1
2
3

Only sleeping elevation goes into the calculation

For this calculation, the published ascent-rate figures use sleeping elevation rather than the day's high point. Every figure in the previous section is written that way.

So a day that climbs to 4,600 m and descends to sleep at 3,900 m enters your table as a 50 m gain. This is not a trick the itinerary is playing on you, and the high point is not being quietly reclassified as something smaller. Going high during the day and sleeping lower is a recognized acclimatization tactic, and the UIAA says it may help, with a caution about not overexerting yourself in the process. That is the whole of the claim. It does not offset a compressed sleeping-elevation profile elsewhere in the itinerary.

It does mean two things. You cannot run this check off a route's advertised maximum altitude, which is the number brochures lead with. And when a rule does not evaluate a day, the honest label is "not evaluated by this check," which is a statement about the rule, not a statement about the day.

Night-to-night change

For each night, subtract last night's sleeping elevation from tonight's. Write the result beside the row, with its sign. Then apply the figure only where it engages: the 500 m reference is for nights that end above 3,000 m.

If you want to confirm a single night's arithmetic without building the whole table first, RoamWell's free single-night checker runs exactly this calculation against the same published figure.

Mark a change of roughly 500 m as review instead of resolving it, because the sources word the boundary differently. Run the first-night condition separately too: if night zero was below 1,200 m and night one is above 2,750 m, that is its own flag regardless of what the rest of the profile does.

Consecutive gaining nights

Count the longest unbroken run of nights that each raise your sleeping elevation while you are above 3,000 m. Any night with no gain, flat or descending, ends the run. Compare the longest run with the three-to-four-day reference. A run of five or six is worth a question. A run of four sits at the edge of the range, and should be read as the edge, not a failure.

What a rest day has to be to count

This is where itineraries most reliably read better than they are. A rest day here means a night with no increase in sleeping elevation, and nothing else qualifies, whatever it is called.

A day billed as an acclimatization day that walks you to a viewpoint 600 m higher and brings you back to the same camp is a rest night by this definition, because the sleeping elevation did not change. A gentle half day that shifts you 300 m up the valley to sleep is not one, even if the itinerary prints the words in bold. Look at the elevation column, not the label. The case for fewer moves and longer stays is usually made in terms of how a trip feels. Here it has a number attached.

Cumulative gain, and the trip average

Once you have marked the genuine rest nights, add the cumulative check. Across each run of consecutive gaining nights above 3,000 m, add up the gain. Compare the total with the extra-night-per-1,000 m reference. A run that gains 1,300 m without a single non-ascent night is worth a question even if no individual night broke 500 m, and this is the pattern the per-night figure on its own will never catch.

Last, the trip average, which is WMS's own formulation of the same idea: total sleeping-elevation gain divided by the number of days on which you gained. One number for the whole trip. It is most useful for comparing two quotes for the same route, and least useful on its own, because an average can look reasonable while hiding a badly distributed week.

Check	Arithmetic	Compare with
Per night	tonight minus last night, for nights ending above 3,000 m	500 m
Longest run	count consecutive nights that gain, above 3,000 m	3 to 4
Cumulative	add the gains within one run	1,000 m
Trip average	total gain divided by number of gaining days	500 m

Summit days and other days the check does not evaluate

Summit days and similar single-day pushes rise steeply and return lower to sleep. Record them in the table and record that the per-night figure does not measure them, because it is written in sleeping elevation. Do not quietly drop them from the page, and do not mark them as within. "Not applicable" is the accurate entry, and it is a different statement from "fine."

Worked example: a common profile that still produces flags

Both examples below are illustrative. The camp elevations are real and published, the schedules around them are constructed, and neither is any current commercial itinerary. The first example uses the Machame route camp elevations published by Climb Kilimanjaro Guide. The second uses the Everest Base Camp figures in Ammonite Adventure's altitude chart, with the descent stop from Adventure Great Himalaya. Both were checked on 29 September 2026. Night zero is a chosen pre-trek town in each case, not a waypoint from those sources. Figures are rounded, and published camp elevations vary between sources by a few tens of meters, which is exactly why the tolerance rule exists.

This one is a seven-night pattern of a kind sold widely. Note the night-zero row: both examples start at 1,400 m, which is above the 1,200 m the first-night condition is written for, so that condition never engages in either of them. On a trip that begins with a flight from sea level it would.

Night	Place	Sleeping elevation	Change	Outcome
0	town, before the trek	1,400 m	baseline	not applicable
1	first camp	2,835 m	+1,435 m	Not applicable (below 3,000 m)
2	second camp	3,850 m	+1,015 m	Exceeds referenced figure
3	third camp	3,900 m	+50 m	Within (day high point 4,600 m, not evaluated)
4	fourth camp	3,960 m	+60 m	Within
5	high camp	4,680 m	+720 m	Exceeds referenced figure
6	descent camp	3,100 m	-1,580 m	Not applicable (descent)

Run the four checks. Two nights exceed the per-night figure, by 515 m and 220 m. The longest run of gaining nights above 3,000 m is four, nights two through five, which sits at the edge of the three-to-four reference. Cumulative gain across that run is 1,015 + 50 + 60 + 720 = 1,845 m, against a reference of an extra night per 1,000 m. Total positive gain across the trip is 3,280 m over five gaining days, so the trip average is 656 m per day.

The reading worth taking from this is not the two big jumps, which anyone would spot. It is that there is no night anywhere in the ascent without a gain. Nights three and four are small enough to feel like rest, and they are not rest by the definition the guidance uses, which means the profile has no rest night at all before the high camp.

Two flags on a pattern this common is an ordinary outcome, not an alarming one, and that is the whole reason a flag produces a question instead of a verdict.

Worked example: a compressed profile

A nine-night pattern that starts with a flight into a mountain airstrip.

Night	Place	Sleeping elevation	Change	Outcome
0	city, before the trek	1,400 m	baseline	not applicable
1	valley village	2,610 m	+1,210 m	Not applicable (below 3,000 m)
2	main town	3,440 m	+830 m	Exceeds referenced figure
3	main town	3,440 m	0 m	Rest night (no gain)
4	monastery village	3,860 m	+420 m	Within
5	upper valley	4,410 m	+550 m	Review (within 50 m of the line)
6	high village	4,940 m	+530 m	Review (within 50 m of the line)
7	highest camp	5,160 m	+220 m	Within (day high point 5,360 m, not evaluated)
8	descent village	4,240 m	-920 m	Not applicable (descent)

One night exceeds the per-night figure and two sit too close to the line to call. The longest run of gaining nights above 3,000 m is four, nights four through seven, cumulative gain 420 + 550 + 530 + 220 = 1,720 m. Total positive gain is 3,760 m over six gaining days, a trip average of 627 m per day.

Now compare the two. On the metrics most people reach for, this second itinerary looks like the better-built one: its biggest single jump is 830 m against 1,015 m, and its trip average is 627 against 656. It also has something the first one lacks entirely, a genuine rest night.

The elevation column says something the comparison misses. That rest night sits at 3,440 m, and there is not another one above it. The last four gaining nights climb 1,720 m without a single night of no gain, and they do it between 3,440 m and 5,160 m, which is the entire upper half of the profile. Generous low down, compressed at the top.

Neither example is being ranked here, and neither is being called a good or a bad trip. The point is narrower and more useful: the two profiles raise questions in different places, and in both cases the informative finding is about rest nights, not the biggest number in the column. A reader comparing only the largest daily jump would have learned the wrong thing about both of them.

Seven patterns worth a question

Once you have run a few of these, the shapes start repeating.

The fly-in start. Night one sits far above night zero because a flight or a long drive did the climbing. The trek's own numbers look modest and the largest elevation event of the trip happened before day one, usually on the same day you got off a long-haul flight.

The staircase. Four, five or six consecutive gaining nights, none individually over 500 m, cumulatively well past 1,000 m. Passes the per-night check cleanly and is exactly what the cumulative check exists for.

The rest day that is not one. A day labeled acclimatization that still raises the sleeping elevation. Caught only by reading the column instead of the label.

The back-loaded push. Unhurried at the bottom, compressed above 4,000 m. The trip average absorbs it and the run check finds it.

The summit-day spike. A large single-day rise treated as routine because it does not change where you sleep. Correctly not evaluated by the per-night figure, and correctly still written down.

The undisclosed profile. No elevations published anywhere. The absence is the finding.

The price-shaped itinerary. Two quotes for the same route, one three days shorter. Run both tables and you can see what the extra three days are actually doing.

What the arithmetic cannot tell you

There are three separate things going on in this check, and keeping them apart is the difference between a useful exercise and a false sense of having settled something.

The first is arithmetic: differences between numbers you were handed. It is reproducible, and you can check anyone's working, including this article's.

The second is published guidance: the figures those differences are compared against. They are recommendations from expert bodies, graded and openly stated, written for planning rather than for individuals. The WMS grades gradual ascent a strong recommendation on moderate-quality evidence, which is a real endorsement and not a guarantee of anything.

The third is everything else, and it is the larger part. How you personally respond to altitude, which varies enormously between people and which nothing in the itinerary predicts. Your health, your history, any medication you take. The weather on the week you go, which is partly a function of when you chose to travel and mostly a function of luck. The group you end up with and the pace it sets. The judgment of the guide on the day. And whether the itinerary on paper is the itinerary that actually happens, which on any multi-day trek it frequently is not.

Physical preparation sits in this third category too. It changes a great deal about how a trek goes, and it changes nothing about how the profile reads: acclimatization and fitness are different processes, and no published ascent figure is adjusted for how fit someone is. If you want to work on it, staying fit while you travel and loaded walking are the two most transferable places to start, and RoamWell's Trek-Ready Training System goes further. None of it moves a number in your table.

A profile with no flags is an itinerary that raises fewer questions. It is not a clearance, and this check is not a medical assessment. The reverse holds too: a flag is not a verdict in the other direction. It marks a place where the itinerary and the published figures disagree, which is a reason to ask a question, not a finding about anyone's health. If you are planning a trip to altitude, take the itinerary to a doctor who works in travel or altitude medicine, along with your own history. What that service is called and how you reach it differs from one country to the next, but it is the conversation where the third category can actually be addressed, and an itinerary check is not a substitute for it.

Turning your findings into questions

Each flag becomes one question, and the questions are worth sending even when you expect a reassuring answer, because the quality of the answer is itself information.

Three things make these work. Ask rather than instruct: you are trying to hear what the operator knows, not win an argument. Quote your own arithmetic, because "your itinerary rises 580 m into night six, to 4,480 m" is a different message from "is this too fast?" And send them early, while an extra night is still a booking change rather than a conversation on the trail.

What you found	What to ask
A night above the 500 m reference	Your itinerary raises sleeping elevation by X into night N, to Y m. Published guidance references no more than 500 m a day above 3,000 m. How does the itinerary account for that, and is there a version with an extra night before that point?
Five or more consecutive gaining nights	There are N consecutive nights of increasing sleeping elevation above 3,000 m with no night of no ascent. Guidance references a rest day every three to four days. Is an acclimatization night available on this route, and where would it fall?
A run gaining more than 1,000 m	This stretch gains X m across consecutive nights with no non-ascent night in between. Guidance references an extra acclimatization night per 1,000 m of gain. Is one available anywhere in that section?
A first night above 2,750 m from low elevation	Night one is at X m, reached in a day from Y m. What happens if someone is unwell on the first morning, and how far is the nearest point you would descend to?
A labeled rest day that gains elevation	Day N is described as an acclimatization day but the sleeping elevation rises by X m. Is there a version of this day that stays at the same elevation?
No elevations published	Could you send the sleeping elevation for each night of the itinerary?

Two questions are worth asking whatever your table says, because no arithmetic reaches them. What are your guides' criteria for turning someone around, and who makes that call, the guide, the group or the client? And what oxygen, pulse oximetry and evacuation arrangements are carried, and what is the descent plan from the highest camp?

The same method in different mountains

The four calculations are not regional. What changes between ranges is which part of the check does most of the work.

In Nepal, treks often begin with a flight to a mountain airstrip, so the profile starts partway up the scale rather than at the bottom and night zero carries unusual weight. In Peru, the city is frequently the event: Cusco sits around 3,400 m, so an arriving traveler is above the engagement threshold before the trek starts, and short trek lengths mean the rest-day rule may never engage. In Tanzania, the start is road-accessible and low, standard route lengths often contain no rest night at all, and the per-night and run checks do nearly all of it.

In Bhutan, long itineraries cross high passes daily, which puts more weight than usual on the distinction between the day's high point and the night's elevation. In Ladakh, flying into Leh at roughly 3,500 m is a first-night event larger than any gain the trek itself will produce, and it happens before the operator's day one. In Colorado and other drive-up ranges, the flight and the drive can do all of the climbing in a day, so the approach is the profile and almost all the information sits in the night-zero row.

Nothing here is a route recommendation or a reason to pick one range over another. It is a note on where to look first.

The table also works on trips nobody describes as a trek, because it runs on sleeping elevations rather than on walking. A ski week that begins with a flight, a pilgrimage, a high driving route, a work posting: any trip with a sequence of overnight elevations can be laid out the same way. RoamWell's guide to Almaty in winter is one of these hiding in plain sight, a trip whose elevations are usually discussed as lift statistics.

If the itinerary does not give you elevations

Work down this list.

If the elevations are simply absent, that is your first question and it is a finding in its own right. An itinerary that will not state its sleeping elevations cannot be compared with any other itinerary on the variable that matters most.

If camps are named but unmeasured, look them up, write down where you got each figure, and mark it as assumed. Carry that distinction all the way through to your questions, so the operator is correcting your numbers rather than confirming them.

If sources disagree, and they will, round to the nearest 50 m and refuse to decide anything on a margin narrower than that. Published camp elevations on popular routes differ by twenty to eighty meters between reputable publishers, and the same publisher's route page and campsite table sometimes contradict each other.

If a day reads "drive to X, trek to Y, overnight at Z," only Z goes in the table. And if an extra acclimatization night is offered as a paid add-on, run the table twice, once with it and once without. The difference between the two is what the upsell actually buys, which is a much better basis for the decision than the price alone.

Fifteen minutes, one column of numbers

Copy out the nights. Fix night zero. Subtract. Count the run. Add the run up. Divide once. Then write to whoever sold you the trip, quoting your own numbers back to them.

What you end up with is not a verdict on the trek, and the check was never going to produce one. It is the difference between buying an itinerary because the photographs were good and buying it because you read the part of it that could be read. If the answers come back specific and unhurried, that tells you something. If they come back vague, that tells you something too, and it is better to learn it now than at 4,900 m.

For most trips this is the first and last time the profile is negotiable. It is worth the quarter of an hour.

---

Related reads:

• Rucking for Beginners: Weight, Progression and What It Actually Does
• How to Stay Fit While Traveling: No Gym Needed
• Slow Travel: What It Means and How to Plan One
• Shoulder Season Travel: Find the Right Time to Go
• How to Beat Jet Lag: The Science-Backed Protocol