Türkiye vs Uruguay: Vulnerability score
Vulnerability score over time
- Türkiye
- Uruguay
How they compare
Uruguay currently reports 0.3747 against 0.3746 in Türkiye, a difference of 0.0001.
The two have swapped places 2 times across 10 shared years of data; in 2015 it was Uruguay ahead.
Türkiye ranks 126th and Uruguay ranks 125th of 187 countries.
Across the 2 decades both report, Türkiye averaged higher in 1 and Uruguay in 1.
Head to head by decade
| Decade | Türkiye | Uruguay | Difference | Ahead |
|---|---|---|---|---|
| 2010s | 0.3796 | 0.3871 | 0.0075 | Uruguay |
| 2020s | 0.3754 | 0.3737 | 0.0017 | Türkiye |
Averages of every year both report within each decade.
Frequently asked questions
- Which has higher vulnerability score, Türkiye or Uruguay?
- Uruguay, at 0.3747 against 0.3746 in Türkiye as of 2024.
- What is the difference in vulnerability score between Türkiye and Uruguay?
- 0.0001, with Uruguay ahead.
- How many years of comparable data are there for Türkiye and Uruguay?
- 10 years are reported by both, from 2015 to 2024.
- How do Türkiye and Uruguay rank globally for vulnerability score?
- Türkiye ranks 126th and Uruguay ranks 125th of 187 countries.
- Where does this data come from?
- International Monetary Fund, published as Vulnerability score. Statizoid refreshes it automatically from the source and publishes the full history for both places.
Individual pages
About this data
The ND-GAIN index is a global free open-source index, that measures a country’s current vulnerability to climate disruptions and assesses a country’s readiness to leverage private and public sector investment for adaptive actions. The IMF-adapted ND-GAIN index is an adaptation of the original index, adjusted by IMF staff to replace the Doing Business (DB) Index, used as source data in the original ND-GAIN, because the DB database has been discontinued by the World Bank in 2020 and it is no longer allowed in IMF work. The IMF-adapted ND-GAIN is an interim solution offered by IMF staff until the ND-GAIN compilers will review the methodology and replace the DB index.