Gaziantep, Adıyaman, Kilis vs Türkiye: Average usual weekly hours worked in the main job by NUTS 2 region
Gaziantep, Adıyaman, Kilis
45.6 Hour
in 2025
Türkiye
43.8 Hour
in 2025
Gaziantep, Adıyaman, Kilis rank
4th
Türkiye rank
2nd
Average usual weekly hours worked in the main job by NUTS 2 region over time
- Gaziantep, Adıyaman, Kilis
- Türkiye
How they compare
Gaziantep, Adıyaman, Kilis currently reports 45.6 Hour against 43.8 Hour in Türkiye, a difference of 1.8 Hour.
Across all 20 years both countries report, Gaziantep, Adıyaman, Kilis has been ahead every year.
Gaziantep, Adıyaman, Kilis ranks 4th and Türkiye ranks 2nd of 437 regions.
Gaziantep, Adıyaman, Kilis has averaged higher in every one of the 3 decades both report.
Head to head by decade
| Decade | Gaziantep, Adıyaman, Kilis | Türkiye | Difference | Ahead |
|---|---|---|---|---|
| 2000s | 56.58 Hour | 50.88 Hour | 5.7 Hour | Gaziantep, Adıyaman, Kilis |
| 2010s | 51.79 Hour | 47.41 Hour | 4.38 Hour | Gaziantep, Adıyaman, Kilis |
| 2020s | 46.17 Hour | 44.55 Hour | 1.62 Hour | Gaziantep, Adıyaman, Kilis |
Averages of every year both report within each decade.
Frequently asked questions
- Which has higher average usual weekly hours worked in the main job by nuts 2 region, Gaziantep, Adıyaman, Kilis or Türkiye?
- Gaziantep, Adıyaman, Kilis, at 45.6 Hour against 43.8 Hour in Türkiye as of 2025.
- What is the difference in average usual weekly hours worked in the main job by nuts 2 region between Gaziantep, Adıyaman, Kilis and Türkiye?
- 1.8 Hour, with Gaziantep, Adıyaman, Kilis ahead.
- How many years of comparable data are there for Gaziantep, Adıyaman, Kilis and Türkiye?
- 20 years are reported by both, from 2006 to 2025.
- How do Gaziantep, Adıyaman, Kilis and Türkiye rank globally for average usual weekly hours worked in the main job by nuts 2 region?
- Gaziantep, Adıyaman, Kilis ranks 4th and Türkiye ranks 2nd of 437 regions.
- Where does this data come from?
- Eurostat, published as Average usual weekly hours worked in the main job by NUTS 2 region. Statizoid refreshes it automatically from the source and publishes the full history for both places.