CACrown ArchivesThe cinema collection
Menu
Research dossier · Places & Architecture

Kong, Iran

city in Hormozgan 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 revisionApr 6, 2026
Entity authorityQ2986542
Source-derived summary

Kong (Persian: كنگ) is a city in the Central District of Bandar Lengeh County, Hormozgan province, Iran.

At the time of the 2006 National Census, the city's population was 14,881 in 2,908 households. The following census in 2011 counted 16,496 people in 4,009 households. The 2016 census measured the population of the city as 19,213 people in 4,921 households.

From April 5 through 6, 2026, amidst the 2026 Iran war, strikes hit both Kong and the nearby city of Bandar Lengeh. Combined, the strikes killed 6 people and wounded 17 others.

Editorial summary

“Kong, Iran” enters the record as city in Hormozgan Province, Iran. Crown Archives preserves that source wording while asking what Kong, Iran and city can confirm, complicate or overturn.

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, 2026—that can be checked directly. The selected authority fields contribute no independent date. Its strongest next move is a source search built around Kong, Iran and city.
Editorial analysis

Why this record matters

“Kong, Iran” is worth following because a concise public description often conceals a longer documentary argument. Here, Kong, Iran and city provides the most credible route into that argument.

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 Apr 6, 2026. The linked authority identifier is Q2986542. Authority coordinates are 26.598, 54.937. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 2006, 2011, 2016 and 2026.

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 “Kong, Iran”, its source revision and the description used here.
  2. Expand the search: follow Kong, Iran primary sources, Kong, Iran archive and Kong 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 “Kong, Iran”?
  2. Which earlier names or jurisdictions may reveal additional records?
  3. What physical evidence or contemporary plan supports the description?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from Kong, Iran” 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.