CACrown ArchivesThe cinema collection
Menu
Research dossier · Places & Architecture

Bandan Rural District

rural district in South Khorasan, Iran

Architectural plans, a scale model, maps and brass measuring instruments
Places and architectureInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionSep 15, 2026
Entity authorityQ4854349 ↗
Source-derived summary

Bandan Rural District (Persian: دهستان بندان) is in the Central District of Nehbandan County, South Khorasan province, Iran. It is administered from the Hajat mine.

Demographics

Population

At the time of the 2006 National Census, the rural district's population was 9,494 in 1,880 households. There were 7,693 inhabitants in 1,777 households at the following census of 2011. The 2016 census measured the population of the rural district as 6,736 in 1,625 households. The most populous of its 82 villages was Bandan, with 1,019 people.

Editorial summary

Begin with the source’s own compact description: “Bandan Rural District” is rural district in South Khorasan, Iran. The dossier treats that line as a proposition to test through Bandan, Rural and District, not as a finished interpretation.

Editorial reviewMost useful as a place-based finding aid connecting the present description to earlier jurisdictions, maps and built evidence. The current lead gives the account dated anchors—2006, 2011, 2016—that can be checked directly. The selected authority fields contribute no independent date. For this dossier, Bandan, Rural and District is the immediate research focus.
Editorial analysis

Why this record matters

The phrase “rural district in South Khorasan, Iran” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.

Evidence profile

Place names and jurisdictional language are key evidence: both can reveal earlier catalogue descriptions and overlooked record series. The source revision retrieved here is dated Sep 15, 2026. The linked authority identifier is Q4854349. The first chronological checks are 2006, 2011 and 2016.

Critical limits

Architectural summaries often privilege surviving fabric and can understate demolished phases, contested use or displaced communities. 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.

Best used for
  • Historic place names
  • Jurisdictional context
  • Routes into maps and plans
Verify next

Contemporary maps, plans, listed-building records, estate papers and the responsible local or national archive.

Three-step research path

  1. Establish the record: confirm the title “Bandan Rural District”, its source revision and the description used here.
  2. Expand the search: follow Bandan Rural District primary sources, Bandan Rural District archive and Bandan research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “Bandan Rural District”?
  2. Which earlier names or jurisdictions may reveal additional records?
  3. Which authority defined the place, boundary or structure at the relevant date?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from “Bandan Rural 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.