Hungary vs Latvia: Readiness score, Social
Readiness score, Social over time
- Hungary
- Latvia
How they compare
Latvia currently reports 0.4695 against 0.4631 in Hungary, a difference of 0.0064.
The two have swapped places 2 times across 10 shared years of data; in 2015 it was Latvia ahead.
Hungary ranks 42nd and Latvia ranks 41st of 186 countries.
Latvia has averaged higher in every one of the 2 decades both report.
Head to head by decade
| Decade | Hungary | Latvia | Difference | Ahead |
|---|---|---|---|---|
| 2010s | 0.4454 | 0.4526 | 0.0073 | Latvia |
| 2020s | 0.4593 | 0.4694 | 0.0101 | Latvia |
Averages of every year both report within each decade.
Frequently asked questions
- Which has higher readiness score, social, Hungary or Latvia?
- Latvia, at 0.4695 against 0.4631 in Hungary as of 2024.
- What is the difference in readiness score, social between Hungary and Latvia?
- 0.0064, with Latvia ahead.
- How many years of comparable data are there for Hungary and Latvia?
- 10 years are reported by both, from 2015 to 2024.
- How do Hungary and Latvia rank globally for readiness score, social?
- Hungary ranks 42nd and Latvia ranks 41st of 186 countries.
- Where does this data come from?
- International Monetary Fund, published as Readiness score, Social. 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.