Part of Trips and itineraries
What the chart plots
The profile reads two numbers from each day of the itinerary: the sleeping altitude and the highest point reached that day. Sleeping altitudes become the line, one point per night. A highest point above the night's stop is drawn as a mark above the line, which is how a day up Kala Patthar and down to Pheriche shows a peak of 5,545 m while the line drops to 4,371 m. Acclimatisation days get a shaded band behind them.
The highest altitude anywhere on the trek, night or day, is labelled on the chart. Days without an overnight, such as a flight home, sit on the axis without a point. The chart appears once at least two nights have an altitude.
Why it matters to the people booking
Altitude sickness is the worry behind most questions a Nepal operator gets about Everest, Manaslu or the Annapurna Circuit. A traveller comparing three Everest Base Camp itineraries wants to see where the nights are and where the rest days fall, and a chart answers that faster than fourteen paragraphs. It also shows the honest shape of a trek: that the highest point is a few hours on one morning, and that the nights climb in steps.
For the office, it's a check on your own itinerary. A chart that jumps from 3,440 m to 4,410 m in one night stands out before a traveller or an agent points it out.
Fast gains in the workspace
Under the chart in the itinerary editor, TripNerve lists nights that break the usual guidance from the Wilderness Medical Society: above 3,000 m, sleep no more than 500 m higher each night, with a rest day every 3–4 days. Each one shows the day, the place and the gain, such as Day 6, Dingboche: +550 m to 4,410 m. It's advice, not a rule. Plenty of good itineraries break it on a day or two, with a rest day after. The list is for your staff and isn't shown to travellers.
- Counted from the last night with an altitude
- Only nights above 3,000 m are checked
- A rest day at the same altitude counts as no gain
Where it appears
On your booking website, the Altitude profile section sits on the trip page with a key for where you sleep, highest point that day and acclimatisation day, and travellers can hover a day for its details. Blog posts can embed the altitude profile block for any trip, so an Everest acclimatisation guide shows the real profile of the trek it sells. The phone app shows the same chart in the itinerary.
When TripNerve's AI drafts a trip, it fills in the altitudes and walking times with the itinerary, so the chart appears straight away. Altitudes found on the web vary by a few dozen metres from source to source; check them against your own guides' notes before you publish, because the chart makes every number visible.
Worked example
The Everest Base Camp Trek in 14 days
A Kathmandu company enters the sleeping altitude and highest point for each day of its 14-day Everest Base Camp Trek. Day 14 is the flight home, with no overnight.
| Day | Overnight | Sleeping | Highest point | Change |
|---|---|---|---|---|
| 2 | Phakding | 2,610 m | 2,860 m (Lukla) | +1,210 m |
| 3 | Namche Bazaar | 3,440 m | +830 m, flagged | |
| 4 | Namche (rest) | 3,440 m | 3,880 m | 0 |
| 5 | Tengboche | 3,860 m | +420 m | |
| 6 | Dingboche | 4,410 m | +550 m, flagged | |
| 7 | Dingboche (rest) | 4,410 m | 5,083 m | 0 |
| 8 | Lobuche | 4,940 m | +530 m, flagged | |
| 9 | Gorak Shep | 5,164 m | 5,364 m (Base Camp) | +224 m |
| 10 | Pheriche | 4,371 m | 5,545 m (Kala Patthar) | −793 m |
The chart labels its peak, 5,545 m on day 10, and describes itself to screen readers as Altitude over 14 days, highest 5,545 m on day 10. Day 2's gain from Kathmandu at 1,400 m isn't flagged because Phakding is below 3,000 m. Three nights are: Namche, Dingboche and Lobuche.
Namche and Dingboche are each followed by a rest day, which is the standard Khumbu pattern, so the company leaves them. Lobuche is the one to think about. It follows a rest day and the gain is 30 m over the guidance, so the company keeps the stage but adds a line to day 8's description about walking slowly and drinking water. A competitor's 12-day itinerary entered the same way shows five flagged nights and one rest day, which is the comparison the sales team wants travellers to make.
Common mistakes
Only filling in the highest point
The line is drawn from sleeping altitudes. Without them the chart has nothing to join and the gain check can't run.
Using feet in one place
Altitudes are entered in metres. A day typed as 17,598 instead of 5,364 puts a spike in the chart travellers will notice.
Not marking rest days
An acclimatisation day that isn't marked looks like an ordinary day at the same altitude. Mark it so the band shows.
Reading the warnings as a verdict
A flagged night isn't wrong in itself. Look at what follows it: a rest day after a 550 m gain is the usual pattern, three flagged nights in a row is not.

