CACrown ArchivesThe cinema collection
Menu
Research dossier · Places & Architecture

Aysak

city in South Khorasan Province, 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 authorityQ83762
Source-derived summary

Aysak (Persian: آيسك) is a city in, and the capital of, Aysak District in Sarayan County, South Khorasan province, Iran. It also serves as the administrative center for Aysak Rural District. The village of Aysak was converted to a city in 1999.

Demographics

Population

At the time of the 2006 National Census, the city's population was 5,023 in 1,399 households. The following census in 2011 counted 4,756 people in 1,488 households. The 2016 census measured the population of the city as 5,143 people in 1,639 households.

Editorial summary

Begin with the source’s own compact description: “Aysak” is city in South Khorasan Province, Iran. The dossier treats that line as a proposition to test through Aysak, city and South, 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—1999, 2006, 2011, 2016—that can be checked directly. The selected authority fields contribute no independent date. For this dossier, Aysak, city and South is the immediate research focus.
Editorial analysis

Why this record matters

The phrase “city in South Khorasan Province, 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

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 Q83762. Authority coordinates are 33.888, 58.383. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1999, 2006, 2011 and 2016.

Critical limits

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.

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 “Aysak”, its source revision and the description used here.
  2. Expand the search: follow Aysak primary sources, Aysak archive and Aysak 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 “Aysak”?
  2. Which authority defined the place, boundary or structure at the relevant date?
  3. What physical evidence or contemporary plan supports the description?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from Aysak” 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.