Data Checks
Each release of the database is checked for records whose fields disagree with each other — for example an expedition's recorded number of summiters not matching the member records marked as summiting. The rules follow the field definitions in the Himalayan Database guide. These are inconsistencies, not necessarily errors: the Himalayan Database is the authority, and some will have explanations. The data is published as it comes, without corrections.
| Check | Records (2026) | Over time (oldest → newest) |
|---|---|---|
|
Member summit count differs from the member records
Expeditions
|
10 | 7 → 9 → 10 → 10 → 9 → 8 → 11 → 9 → 10 |
|
Hired summit count differs from the member records
Expeditions
|
16 | 4 → 8 → 15 → 12 → 12 → 14 → 15 → 15 → 16 |
|
Member death count differs from the member records
Expeditions
|
0 | 0 → 0 → 0 → 0 → 0 → 0 → 0 → 0 → 0 |
|
Hired death count differs from the member records
Expeditions
|
0 | 0 → 0 → 0 → 0 → 0 → 0 → 0 → 0 → 0 |
|
Marked successful, but nobody summited
Expeditions
|
1 | 1 → 1 → 1 → 1 → 1 → 1 → 1 → 1 → 1 |
|
Member record with no matching expedition
Members
|
0 | 0 → 0 → 0 → 0 → 0 → 0 → 0 → 0 → 0 |
|
Reference with no matching expedition
References
|
41 | 5 → 0 → 0 → 0 → 0 → 41 → 41 → 62 → 41 |
|
Member's peak differs from the expedition's
Members
|
0 | 0 → 0 → 0 → 0 → 0 → 0 → 0 → 0 → 0 |
|
Year of birth after the expedition
Members
|
2 | 3 → 4 → 3 → 0 → 0 → 1 → 1 → 2 → 2 |
|
Unusual age
Members
|
2 | 1 → 1 → 1 → 1 → 1 → 1 → 1 → 1 → 2 |
|
Possibly the same person listed twice
Members
|
22 | 15 → 12 → 32 → 20 → 20 → 20 → 20 → 22 → 22 |
Releases, oldest first: 2017, 2018, 2020, 2022, 2023, 2024, 2025, 2026, 2026.