Kiribati vs Vanuatu: Vulnerability score
Vulnerability score over time
- Kiribati
- Vanuatu
How they compare
Vanuatu currently reports 0.5631 against 0.557 in Kiribati, a difference of 0.0061.
The two have swapped places 4 times across 10 shared years of data; in 2015 it was Vanuatu ahead.
Kiribati ranks 23rd and Vanuatu ranks 20th of 187 countries.
Across the 2 decades both report, Kiribati averaged higher in 1 and Vanuatu in 1.
Head to head by decade
| Decade | Kiribati | Vanuatu | Difference | Ahead |
|---|---|---|---|---|
| 2010s | 0.5753 | 0.5856 | 0.0103 | Vanuatu |
| 2020s | 0.5645 | 0.5589 | 0.0056 | Kiribati |
Averages of every year both report within each decade.
Frequently asked questions
- Which has higher vulnerability score, Kiribati or Vanuatu?
- Vanuatu, at 0.5631 against 0.557 in Kiribati as of 2024.
- What is the difference in vulnerability score between Kiribati and Vanuatu?
- 0.0061, with Vanuatu ahead.
- How many years of comparable data are there for Kiribati and Vanuatu?
- 10 years are reported by both, from 2015 to 2024.
- How do Kiribati and Vanuatu rank globally for vulnerability score?
- Kiribati ranks 23rd and Vanuatu ranks 20th 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.