Nepal vs Uganda: Vulnerability score, Capacity
Vulnerability score, Capacity over time
- Nepal
- Uganda
How they compare
Uganda currently reports 0.6798 against 0.6695 in Nepal, a difference of 0.0103.
The two have swapped places 2 times across 10 shared years of data; in 2015 it was Uganda ahead.
Nepal ranks 41st and Uganda ranks 38th of 177 countries.
Uganda has averaged higher in every one of the 2 decades both report.
Head to head by decade
| Decade | Nepal | Uganda | Difference | Ahead |
|---|---|---|---|---|
| 2010s | 0.677 | 0.6794 | 0.0023 | Uganda |
| 2020s | 0.6641 | 0.6796 | 0.0155 | Uganda |
Averages of every year both report within each decade.
Frequently asked questions
- Which has higher vulnerability score, capacity, Nepal or Uganda?
- Uganda, at 0.6798 against 0.6695 in Nepal as of 2024.
- What is the difference in vulnerability score, capacity between Nepal and Uganda?
- 0.0103, with Uganda ahead.
- How many years of comparable data are there for Nepal and Uganda?
- 10 years are reported by both, from 2015 to 2024.
- How do Nepal and Uganda rank globally for vulnerability score, capacity?
- Nepal ranks 41st and Uganda ranks 38th 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.