Bageshwar district
district of Uttarakhand, India
Bageshwar district is a district of Uttarakhand state in northern India. The town of Bageshwar is the district headquarters. Prior to its establishment as a district in 1997 it was part of Almora district.
Bageshwar district is in Kumaon, and is bounded on the west and northwest by Chamoli District, on the northeast and east by Pithoragarh District, and on the south by Almora District.
As of 2011 it is the third least populous district of Uttarakhand (out of 13), after Rudraprayag and Champawat.
History
The area, that now forms Bageshwar district, was historically known as Danpur, and was ruled by Katyuris during the 7th century AD. After the disintegration of the Katyuri kingdom in the 13th century, the area remained under the rule of Baijnath Katyurs, direct descendants of Katyuri kings. In 1565, king Balo Kalyan Chand annexed Danpur along with Pali, Barahmandal and Mankot to Kumaun.
In 1791, Almora, the seat of the Kumaon, was invaded and annexed by the Gorkhas of Nepal. The Gorkhas ruled the region for 24 years and were later defeated by the East India Company in 1814, and were forced to cede Kumaon to the British as part of the Treaty of Sugauli in 1816. After its annexation by British, Bageshwar was a part of the Danpur pargana in Almora district of United Provinces.
This brief starts where responsible research should: with the source description of “Bageshwar district” as district of Uttarakhand, India. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the places & architecture register because the source frames it as district of Uttarakhand, India. Its deeper value depends on whether names, dates, institutions and citations support that framing.
The strongest evidence will usually combine a dated visual record with documents produced by the authority responsible for the place. The source revision retrieved here is dated Sep 15, 2026. The linked authority identifier is Q1815313. The Library of Congress control number is no2025084384. Authority coordinates are 29.850, 79.770. 3 of 3 selected statements include explicit references; 1 carry qualifiers and 0 use preferred rank. The first chronological checks are 1997, 2011, 1565 and 1791.
A single description cannot reconcile every naming convention, rebuilding phase or administrative transfer associated with a place. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Treat names, boundaries and functions as historically changeable. Maps, plans, inventories and administrative records can clarify what the place meant at different dates.
- Historic place names
- Jurisdictional context
- Routes into maps and plans
Contemporary maps, plans, listed-building records, estate papers and the responsible local or national archive.
Three-step research path
- Establish the record: confirm the title “Bageshwar district”, its source revision and the description used here.
- Expand the search: follow Bageshwar district primary sources, Bageshwar district archive and Bageshwar research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Bageshwar district”?
- What physical evidence or contemporary plan supports the description?
- Which authority defined the place, boundary or structure at the relevant date?
Search terms from this dossier
This entry incorporates text from “Bageshwar district” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.