Bolivia vs Peru: Vulnerability score, Ecosystems
Vulnerability score, Ecosystems over time
- Bolivia
- Peru
How they compare
Bolivia currently reports 0.4439 against 0.438 in Peru, a difference of 0.0059.
Across all 10 years both countries report, Bolivia has been ahead every year.
Bolivia ranks 100th and Peru ranks 103rd of 180 countries.
Bolivia has averaged higher in every one of the 2 decades both report.
Head to head by decade
| Decade | Bolivia | Peru | Difference | Ahead |
|---|---|---|---|---|
| 2010s | 0.4438 | 0.4368 | 0.0069 | Bolivia |
| 2020s | 0.4439 | 0.4378 | 0.006 | Bolivia |
Averages of every year both report within each decade.
Frequently asked questions
- Which has higher vulnerability score, ecosystems, Bolivia or Peru?
- Bolivia, at 0.4439 against 0.438 in Peru as of 2024.
- What is the difference in vulnerability score, ecosystems between Bolivia and Peru?
- 0.0059, with Bolivia ahead.
- How many years of comparable data are there for Bolivia and Peru?
- 10 years are reported by both, from 2015 to 2024.
- How do Bolivia and Peru rank globally for vulnerability score, ecosystems?
- Bolivia ranks 100th and Peru ranks 103rd of 180 countries.
- Where does this data come from?
- International Monetary Fund, published as Vulnerability score, Ecosystems. 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.