Most mountains people dream about come with a shelf of books. Pasu – E comes with one line. The NADRA List of Peaks for Gilgit-Baltistan (snapshot dated 2026-08-26) gives a name, Pasu – E, and a height, 7,300 metres, and nothing else. No district, no coordinates, no route, no ascent record. That gap is the real subject of this page. Instead of padding it with guesses, we walk through how a serious team can build its own evidence file for a thinly documented 7,000-metre row, what to ask, who to ask, and how to tell solid information from hearsay before money and lives are committed.
The entry, exactly as listed
- Name on the list: Pasu – E (with a spaced dash, as printed)
- Height: 7,300 m
- Shares that height with: Urdok Kangri – I and Urdok – I, both also at 7,300 m
- Related name on the list: Pasu Peak at 7,295 m, and Passu/Peak 55 at 7,284 m
- District, coordinates, grade, season, first ascent: not given
The “E” is very likely an abbreviation, and “east” is the obvious reading. But the list doesn’t say so, and a guess written onto a permit application is still a guess. Treat the letter as part of the name until an authority tells you what it means. A one-line catalog entry is enough to start a dossier, not enough to skip one.
Heights around this row
| Row | Height | Difference |
|---|---|---|
| Pumari Chhish – S | 7,314 m | 14 m higher |
| Baltoro Kangri I | 7,312 m | 12 m higher |
| Pasu – E | 7,300 m | — |
| Urdok Kangri – I / Urdok – I | 7,300 m | same |
| Pasu Peak | 7,295 m | 5 m lower |
Fifty-six rows on the snapshot carry a greater figure. Small differences like these are within the range where surveys disagree, so don’t build a marketing claim or a personal goal around a few metres.
Why a dossier matters more here than on famous peaks
On a well-known mountain, mistakes get corrected by the crowd. Someone has photographed the approach, someone has logged the camps, someone has complained in print about a bad river crossing. On a row like this, that safety net doesn’t exist. Every assumption your team makes may go unchallenged until you’re standing in the wrong valley.
A dossier is simply a shared document where every claim about the objective sits next to where it came from and how sure you are. It’s boring work. It is also the cheapest risk reduction available, because it happens at a desk.
Building the file: five layers
Work from the most authoritative source outward, and stop treating a layer as complete until it has a named source.
Layer 1: Official identity
Ask the permitting authority, in writing, to confirm the exact name, height and any reference number they use for this row. Keep the reply. If they use a different spelling or a different height, note both. The procedure is explained in applying for trekking and mountaineering permits, and the governing rules are in trekking and mountaineering regulations.
Layer 2: Location
Ask whoever confirms the identity whether they hold coordinates or a district for it. If a source gives coordinates, record the datum and the source, and check whether the point sits on a plausible summit on more than one map. If two sources put it in different places, the dossier should say “unresolved”, not pick the one you like.
Layer 3: Access
Only once location is settled does it make sense to plan an approach. Ask operators to describe the route stage by stage: road end, walking days, river crossings, likely base camp. General transport into the region is covered in getting to Gilgit-Baltistan.
Layer 4: Mountain history
Search expedition journals and club archives for reports that clearly name this summit. Be strict. A report about “a peak near Pasu” is not a report about Pasu – E. Record each find as confirmed, probable or doubtful.
Layer 5: Current conditions
Glaciers retreat, bridges wash out, and regulations change. Whatever you learn about the approach should carry a date. Information older than a few seasons deserves a second check.
A worked example of a dossier entry
To make the idea concrete, here is how one line in the file might look. The content is a template, not a claim about this mountain.
| Item | Value | Source | Date | Confidence |
|---|---|---|---|---|
| Official name | Pasu – E | NADRA List of Peaks | 2026-08-26 | Confirmed |
| Height | 7,300 m | NADRA List of Peaks | 2026-08-26 | Confirmed |
| Meaning of “E” | (to be filled) | (authority reply) | — | Unverified |
| District | (to be filled) | (authority reply) | — | Unverified |
Every empty cell is a question someone on the team owns. Give each one a name and a deadline. When the cell is filled, the person who filled it writes the source in plain words, not “I heard”. If a later source contradicts an earlier one, keep both rows and mark the item unresolved, rather than overwriting the older answer.
Who keeps the file
One person should hold the master copy, even if several people contribute. On small teams that is often the leader, but it works better when it’s someone with time and patience for detail. Agree a rule for edits: new information goes in with its source, and nothing is deleted without the team knowing. Before each major decision, such as paying a deposit or booking flights, the keeper reads the file aloud, or circulates it, so everyone sees what is still unverified.
Grading your evidence
A simple three-level label keeps the team honest:
- Confirmed: written statement from the authority, or two independent reliable sources that agree.
- Probable: one reliable source, not contradicted.
- Unverified: word of mouth, forum posts, assumptions from the name.
Planning decisions that carry real risk, such as which valley to enter or where to put base camp, should rest on confirmed or probable items only. Unverified material can guide questions, not decisions.
Questions to put to operators
When you interview companies using the hiring a tour operator checklist, a thinly documented objective calls for a few extra questions:
- Have you, or anyone you work with, been to the base of this specific row? How do you know it was this one?
- What source do you use for its location?
- What happens to the contract if the authority disagrees with the planned approach?
- Who on your side handles liaison and paperwork, and how will changes reach us?
An operator who answers “we’re not sure, but here’s how we’d find out” is often more trustworthy than one who has a confident answer for everything. Check any guide’s standing against registering as a tour guide.
People and loads
Porter terms, load limits and wages should follow the porter and mule hiring regulations. On an uncertain approach, agree in advance how extra days are paid if the route turns out longer than expected. That conversation is far easier in town than on a moraine. For personal kit, see the packing list for Gilgit-Baltistan.
Seasons
The list gives no climbing window for this row. Regional weather patterns are summarised in the best time to visit Gilgit-Baltistan, but valley weather and high-altitude climbing weather are different problems. Get a seasonal recommendation from your operator and ask what it’s based on. Write that answer into the dossier too, with its source.
Safety on a poorly known mountain
Uncertainty is itself a hazard. The less is known about a mountain, the more conservative the plan should be.
- Build extra days into acclimatisation. You can’t borrow someone else’s experience of how the mountain treats bodies.
- Set a strict turnaround rule and agree it before leaving base camp.
- Plan rescue as if it will be slow. Helicopter access, insurance cover and communications should all be confirmed in writing before departure.
- Log what you find. Your own notes may become the first useful record of the approach.
For emergencies in the region, the Tourist Police can be reached on 1422 and 05811-930055. Make sure your insurer and operator know your intended location as precisely as the dossier allows.
Leaving a better record behind
If your team does reach the base, or the summit, consider sharing a sober, factual account with the authority and with a mountaineering journal. State what you’re sure of and what you aren’t. The next team will thank you, and the gap that made this page necessary will shrink a little.
Respect in the valleys
Whatever valley you end up in, you’ll be a guest. Read about the culture of Gilgit-Baltistan, check photography restrictions, and follow camping regulations on waste and water. Ask before photographing people or homes.
Frequently asked questions
What height does the official list give for Pasu – E?
The NADRA List of Peaks snapshot dated 2026-08-26 records it at 7,300 metres.
Does “E” mean east?
That’s the likely reading, but the list doesn’t spell it out. Ask the permitting authority before relying on it.
Is Pasu – E the same mountain as Pasu Peak?
They are separate rows, at 7,300 m and 7,295 m. Don’t assume they describe the same summit.
Which other rows share its height?
Urdok Kangri – I and Urdok – I are both listed at 7,300 metres.
Where exactly is it?
The list gives no coordinates or district. Request location details from the authority and record the source.
Is there a known climbing route?
None is recorded on the list. Treat any route description as unverified until it has a reliable named source.
What is an expedition dossier?
A shared document listing every fact about the objective alongside its source and a confidence level.
How should we choose an operator for a little-known peak?
Ask how they know the location, who they’ve sent there, and how the contract handles changes. Honest uncertainty is a good sign.
Do porter rules change for remote objectives?
The same regulations apply. Agree in advance how extra days will be handled if the approach runs long.
Who do I call in an emergency?
The Tourist Police numbers are 1422 and 05811-930055. Arrange evacuation cover through your operator and insurer before setting out.