CACrown ArchivesThe cinema collection
Menu
Research dossier · Places & Architecture

Robat-e Sang

city in Razavi 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 revisionMar 30, 2026
Entity authorityQ4364033
Source-derived summary

Robat-e Sang (Persian: رباطسنگ) is a city in, and the capital of, Jolgeh Rokh District in Torbat-e Heydarieh County, Razavi Khorasan province, Iran. It also serves as the administrative center for Miyan Rokh Rural District.

Demographics

Population

At the time of the 2006 National Census, the city's population was 1,344 in 384 households. The following census in 2011 counted 1,721 people in 462 households. The 2016 census measured the population of the city as 1,551 people in 457 households.

Editorial summary

Begin with the source’s own compact description: “Robat-e Sang” is city in Razavi Khorasan Province, Iran. The dossier treats that line as a proposition to test through Robat-e, Sang and city, not as a finished interpretation.

Editorial reviewA valuable geographic starting point for tracing changing names, boundaries, uses and administrative responsibility. 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, Robat-e, Sang and city is the immediate research focus.
Editorial analysis

Why this record matters

The phrase “city in Razavi 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

Maps, plans, fabric surveys and administrative records can establish how the site’s name, extent and function changed over time. The source revision retrieved here is dated Mar 30, 2026. The linked authority identifier is Q4364033. Authority coordinates are 35.546, 59.194. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 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 “Robat-e Sang”, its source revision and the description used here.
  2. Expand the search: follow Robat-e Sang primary sources, Robat-e Sang archive and Robat-e 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 “Robat-e Sang”?
  2. What physical evidence or contemporary plan supports the description?
  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 Robat-e Sang” 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.