Samarkand
city in southeastern Uzbekistan

Samarkand is a major city located in southeastern Uzbekistan. Among the oldest continuously inhabited cities in Central Asia, it has a population of 882,000 inhabitants as of 2026, making it the second-largest city in Uzbekistan after Tashkent. It is the capital of the Samarkand Region and a district-level city, that includes the urban-type settlements of Kimyogarlar, Farkhod and Khishrav. Earlier it also served as the initial capital of the Uzbek Soviet Socialist Republic from 1925 until 1930.
There is evidence of human activity in the area of the city dating from the late Paleolithic. Though the exact date of founding of Samarkand remains uncertain, it has been proposed that it was established between the 8th and 7th centuries BC. Historically, Samarkand has long been one of the principal urban centers of Iranic civilization in Central Asia and played a major role in the cultural and commercial networks of the Silk Road. By the time of the Persian Achaemenid Empire, it was the capital of the satrapy of Sogdiana. The city was conquered by Alexander the Great in 329 BC; at that time it was known as Markanda. Islam got introduced to the region in the 8th century AD following the Umayyad campaigns. It was one of the principal cities in the Samanid Empire, under which New Persian gradually replaced Sogdian as the dominant language of the region.
Begin with the source’s own compact description: “Samarkand” is city in southeastern Uzbekistan. The dossier treats that line as a proposition to test through Samarkand, city and southeastern, not as a finished interpretation.
Why this record matters
The phrase “city in southeastern Uzbekistan” 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.
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 21, 2026. The linked authority identifier is Q5753. VIAF identifies the subject as 152380790. The Library of Congress control number is n80113871. Authority coordinates are 39.655, 66.976. 3 of 5 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 2026, 1925 and 1930.
Architectural summaries often privilege surviving fabric and can understate demolished phases, contested use or displaced communities. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. 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 “Samarkand”, its source revision and the description used here.
- Expand the search: follow Samarkand primary sources, Samarkand archive and Samarkand 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 “Samarkand”?
- Which authority defined the place, boundary or structure at the relevant date?
- What physical evidence or contemporary plan supports the description?
Search terms from this dossier
This entry incorporates text from “Samarkand” 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.