Haiti vs Sudan: Vulnerability score, Capacity
Vulnerability score, Capacity over time
- Haiti
- Sudan
How they compare
Haiti currently reports 0.7311 against 0.721 in Sudan, a difference of 0.0101.
The two have swapped places 1 time across 10 shared years of data; in 2015 it was Sudan ahead.
Haiti ranks 22nd and Sudan ranks 24th of 177 countries.
Across the 2 decades both report, Haiti averaged higher in 1 and Sudan in 1.
Head to head by decade
| Decade | Haiti | Sudan | Difference | Ahead |
|---|---|---|---|---|
| 2010s | 0.7369 | 0.7637 | 0.0267 | Sudan |
| 2020s | 0.7316 | 0.7235 | 0.0081 | Haiti |
Averages of every year both report within each decade.
Frequently asked questions
- Which has higher vulnerability score, capacity, Haiti or Sudan?
- Haiti, at 0.7311 against 0.721 in Sudan as of 2024.
- What is the difference in vulnerability score, capacity between Haiti and Sudan?
- 0.0101, with Haiti ahead.
- How many years of comparable data are there for Haiti and Sudan?
- 10 years are reported by both, from 2015 to 2024.
- How do Haiti and Sudan rank globally for vulnerability score, capacity?
- Haiti ranks 22nd and Sudan ranks 24th of 177 countries.
- Where does this data come from?
- International Monetary Fund, published as Vulnerability score, Capacity. 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.