Cities in Türkiye: Eurostat data
Browse 4 available profiles for Türkiye, separated into city and greater-city geography and listed alphabetically. These are 4 release-scoped provider records, not an accepted or complete national city directory.
City provider records
Comparison status: qualified. Records use the same Eurostat indicator, reference period, and provider grain. National implementation and boundary vintage have not been reviewed. Source flags remain visible. Numeric ordering is for browsing only, and no ordinal position is published.
| Current source label and code | Population (DE1001V) | Source status code and meaning | Reference period | Comparison status |
|---|---|---|---|---|
| Ankara TR001C | Not reported | Not applicable | Not applicable | qualified |
| Antalya TR003C | Not reported | Not applicable | Not applicable | qualified |
| Diyarbakir TR007C | Not reported | Not applicable | Not applicable | qualified |
| Istanbul TR012C | Not reported | Not applicable | Not applicable | qualified |
About this table's data
- Dataset and metric
- urb_cpop1, DE1001V
- Accepted release
- eurostat_city_statistics.urb_cpop1.2022.a0a3004b398d
- Period
- 2022
- Table geography
- city provider records
- Boundary vintage
- Not established
- Project treatment
- source_literal
- Source dates
- Accessed 2026-09-01; retrieved 2026-09-01T18:15:29Z; Eurostat update 2026-08-31T23:00:00+0200
- Coverage note
- Not every provider profile reports this field. Missing values stay missing, and source status appears with each affected value.
- How to read it
- Label the page as Eurostat city or greater-city population for the stated year.
Only retained direct Eurostat City Statistics values appear. Derived age-65-plus values remain private pending P-012. Maps, coordinates, climate, regional statistics, PPP, density, and capital status are not in public use.
Accessed 1 September 2026 from the exact Eurostat datacodes. The accepted responses were freshly captured on that date; their selected keys, values, source-status codes, provider labels, and indicator labels matched the retained extracts. The superseded legacy extracts' original download times were not recorded. The perception response alone was byte-identical; metadata changes made the other seven responses byte-different.
The 1 September 2026 API review found later 2024 or 2025 candidate observations in the seven non-perception tables. Those candidates have not passed project acceptance and are not shown.