Some rows on the official table are hard to tell apart even when you know they exist. The Pakistan Online Visa System (NADRA) List of Peaks for Gilgit-Baltistan, snapshot dated 2026-08-26, includes a row written simply as Urdok – I, listed at 7,300 metres. Two other rows share that exact figure: Urdok Kangri –I and Pasu – E. A fourth, Urdok Kangri –II, stands 58 metres higher at 7,358 metres. Fifty-four elevation-listed entries rank above the 7,300-metre group and forty-seven below it.
Are Urdok – I and Urdok Kangri –I two names for one mountain? The official list doesn’t say. It records them as separate rows, and so do we. We won’t speculate, because nothing in the list or our live page settles the question. Instead, this page uses the puzzle as a starting point for a broader skill: reading an official data table carefully, understanding what it does and doesn’t tell you, and using it properly when you plan. The record gives no district, coordinates, route, grade or ascent history for Urdok – I, and neither do we. Reading the official list carefully is half the battle when names collide.
The row as listed
- Exact wording: Urdok – I
- Height: 7,300 m
- Tied rows: Urdok Kangri –I; Pasu – E
- Higher related name: Urdok Kangri –II, 7,358 m
- Ranked higher: 54 entries
- Ranked lower: 47 entries
- District, coordinates, route: none
The 7,300-metre cluster
| Official entry | Listed height | Relation to Urdok – I |
|---|---|---|
| Urdok Kangri –II | 7,358 m | 58 m higher |
| Baltoro Kangri-I | 7,312 m | 12 m higher |
| Urdok – I | 7,300 m | — |
| Urdok Kangri –I | 7,300 m | tied; separate row, longer name |
| Pasu – E | 7,300 m | tied; unrelated name |
| Pasu Peak | 7,295 m | 5 m lower |
| K-6 | 7,282 m | 18 m lower |
What a permit list is for
The NADRA list exists to support the permit system: it names the peaks for which mountaineering permission is handled and records a height for each. It is an administrative tool, not an atlas, a guidebook or a history. Reading it with that purpose in mind prevents most misunderstandings. If something isn’t needed for permits, don’t expect to find it there.
What each column tells you
Our live page draws on two things from each row: the name and the height. The name is the identifier that matters on forms. The height is a recorded value in metres, useful for comparison and for confirming you’ve picked the right row. Neither tells you where the mountain is, how to climb it or how hard it is.
Treat names as exact strings
On an administrative list, “Urdok – I” and “Urdok Kangri –I” are different strings, and that is enough to treat them as different rows. Spacing, dashes and numerals may look inconsistent, as they do here, but copy them exactly. Don’t tidy them up or “correct” them on your forms; doing so may create a mismatch with the official record.
Ties are ordinary
Many heights on the list are round numbers, and several rows share a figure. A tie means only that the recorded values match. It doesn’t imply the peaks are near one another, related, or the same mountain. Pasu – E sharing 7,300 m with two Urdok rows is a coincidence of recorded values, nothing more.
Rankings are relative
When our page says fifty-four entries are higher, it counts rows with a stated height in this snapshot. Rankings shift when the list changes, and ties affect how positions are counted. Use rankings to get a sense of scale, not as a fixed title.
Snapshots and dates
Every fact here is tied to the 2026-08-26 snapshot. Official lists can be revised: names corrected, heights updated, rows added or removed. Before applying, check the current version, and note the date of the version you used in your own records.
Absence is information too
The list’s silence on districts, routes and grades is not an error; it simply isn’t the list’s job. When a source doesn’t state something, the honest response is “not stated”, not a guess. Websites that fill those gaps without citing a source deserve caution.
When you still can’t tell
If you’re unsure which row matches your plans, especially between Urdok – I and Urdok Kangri –I, ask the permit authority or your licensed operator to confirm in writing which row your expedition targets. That written confirmation is worth more than any amount of online research.
Reading comparisons fairly
Tables on our pages compare heights to the nearest metre, just as the list records them. A difference of a few metres between rows is a difference in recorded values, nothing more. It doesn’t tell you which mountain is harder, more dramatic or more popular. Resist the temptation to rank peaks by interest using height alone; the official list has no opinion on that, and neither should your planning notes.
Spotting errors without assuming them
Official lists can contain inconsistencies, such as unusual spacing, differing dash styles or names that look duplicated. Notice them, but don’t assume they’re mistakes. They may reflect naming conventions you don’t know about. If an inconsistency affects your application, raise it with the authority rather than deciding for yourself.
Keeping your own working copy
When researching, many people keep a personal spreadsheet of peaks they’re interested in. If you do, copy names and heights exactly, add a column for the snapshot date, and another for the source. Never edit official values in your copy; add notes in separate columns instead. That way, your working file remains a faithful reflection of the source, with your thoughts clearly separated.
Cross-checking with other sources
Other publications may list different heights or names for peaks in the region. That’s normal; measurement methods vary. For permits, the official list is the reference. For general interest, compare sources and note where they disagree, but don’t merge them into a single figure of your own making.
Teaching others to read the list
If you’re organising a group, share these habits with everyone involved. A short briefing on exact names, snapshot dates and the meaning of ties prevents confusion later, when several people are filling in forms and messages. The more people who read the list carefully, the fewer errors slip through.
Why care about this at all
It may seem pedantic to fuss over dashes and snapshot dates. But expeditions involve many documents, many people and real money. Small errors in names cause delays at exactly the moments when time is most precious. Reading the official list carefully is a small effort that protects a large investment.
A worked example
Suppose a friend sends you a message saying they plan to apply for “Urdok 1”. Which row do they mean? Three possibilities exist on paper: Urdok – I, Urdok Kangri –I, or something else entirely. The right response is to ask them to check the exact wording and height on the official list and confirm with their operator. Shorthand names in conversation are fine; on forms, only the exact string will do.
Recording your sources
Whenever you note a height or name in your plans, add where it came from and the date. “Urdok – I, 7,300 m, NADRA list snapshot 2026-08-26” is a complete reference. “Urdok, about 7,300” is not. Complete references make it easy to check later whether anything has changed.
Version control for planners
If the official list is updated while you are planning, keep the old copy alongside the new one rather than overwriting it. Compare the Urdok – I row line by line: name string, height, neighbours. Note any change, however small, and tell everyone on your team which version is now current. Archived copies also help settle disputes if a form is questioned later, because you can show exactly what the record said on the day you applied. Label each saved file with its retrieval date in the filename so nobody mixes them up.
Choosing the row on your application
Use the exact string “Urdok – I” with 7,300 m if this is your intended row, and keep the confirmation of that choice with your documents. The permit application guide explains the process; trekking and mountaineering regulations cover registration and licensed guides.
Getting to the region
Gateway options are set out in getting to Gilgit-Baltistan and on the Skardu airport access page. Because the list names no district, your operator will confirm the actual approach.
Season and kit
The best time to visit guide and packing guide provide the general picture; your guide will tailor them to your objective.
Safety
Keep a printed note of your camping regulations and photography restrictions alongside your row reference. Emergency numbers belong in that same file: Gilgit-Baltistan Tourist Police, 1422 or 05811-930055, plus your operator’s contact.
Working with an operator
Ask your operator which row they’re planning for and how they confirmed it. Further vetting questions sit in the hiring guide; licensing basics are covered under registering as a tour guide.
Frequently asked questions
What height is listed for Urdok – I?
The NADRA snapshot dated 2026-08-26 records 7,300 metres.
Is Urdok – I the same as Urdok Kangri –I?
The list records them as separate rows, both at 7,300 m. It doesn’t say whether they refer to the same summit, and we don’t assume so.
Which other row shares 7,300 m?
Pasu – E.
How high is Urdok Kangri –II?
7,358 metres, 58 metres above Urdok – I.
How does Urdok – I rank?
Its position: 54 rows above, 47 rows below.
Does the list give a location?
No district, coordinates or route are stated.
Should I correct odd spacing or dashes in the name?
No. Copy the official wording exactly on forms.
Does a shared height mean peaks are related?
No. A tie only means the recorded values match.
How can I be sure which row to apply for?
Ask the permit authority or your licensed operator to confirm in writing.
Who do I call in an emergency?
Dial 1422, or 05811-930055, to reach the Gilgit-Baltistan Tourist Police.
Source
Data: NADRA’s Gilgit-Baltistan peak list (Pakistan Online Visa System), retrieved as the 2026-08-26 snapshot, together with our live page. No district, route, grade or coordinates are given.