Latvia vs Lithuania: Vulnerability score
Vulnerability score over time
- Latvia
- Lithuania
How they compare
Latvia currently reports 0.3597 against 0.3596 in Lithuania, a difference of 0.0001.
The two have swapped places 1 time across 10 shared years of data; in 2015 it was Lithuania ahead.
Latvia ranks 144th and Lithuania ranks 145th of 187 countries.
Lithuania has averaged higher in every one of the 2 decades both report.
Head to head by decade
| Decade | Latvia | Lithuania | Difference | Ahead |
|---|---|---|---|---|
| 2010s | 0.3662 | 0.3689 | 0.0027 | Lithuania |
| 2020s | 0.3616 | 0.3628 | 0.0012 | Lithuania |
Averages of every year both report within each decade.
Frequently asked questions
- Which has higher vulnerability score, Latvia or Lithuania?
- Latvia, at 0.3597 against 0.3596 in Lithuania as of 2024.
- What is the difference in vulnerability score between Latvia and Lithuania?
- 0.0001, with Latvia ahead.
- How many years of comparable data are there for Latvia and Lithuania?
- 10 years are reported by both, from 2015 to 2024.
- How do Latvia and Lithuania rank globally for vulnerability score?
- Latvia ranks 144th and Lithuania ranks 145th 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.