Croatia vs Latvia: SUT Use at purchasers': Intermediate consumption
SUT Use at purchasers': Intermediate consumption over time
- Croatia
- Latvia
How they compare
Croatia currently reports 63,103 National currency against 38,440 National currency in Latvia, a difference of 24,663 National currency.
That makes Croatia's figure about 1.6 times Latvia's.
Across all 13 years both countries report, Croatia has been ahead every year.
Croatia ranks 3rd and Latvia ranks 6th of 3 countries.
Croatia has averaged higher in every one of the 2 decades both report.
Head to head by decade
| Decade | Croatia | Latvia | Difference | Ahead |
|---|---|---|---|---|
| 2010s | 40,037 National currency | 25,903 National currency | 14,134 National currency | Croatia |
| 2020s | 52,045 National currency | 33,139 National currency | 18,906 National currency | Croatia |
Averages of every year both report within each decade.
Frequently asked questions
- Which has higher sut use at purchasers' prices (for 'developer api') — intermediate, Croatia or Latvia?
- Croatia, at 63,103 National currency against 38,440 National currency in Latvia as of 2022.
- What is the difference in sut use at purchasers' prices (for 'developer api') — intermediate between Croatia and Latvia?
- 24,663 National currency, with Croatia ahead.
- How many years of comparable data are there for Croatia and Latvia?
- 13 years are reported by both, from 2010 to 2022.
- How do Croatia and Latvia rank globally for sut use at purchasers' prices (for 'developer api') — intermediate?
- Croatia ranks 3rd and Latvia ranks 6th of 3 countries.
- Where does this data come from?
- Organisation for Economic Co-operation and Development, published as SUT Use at purchasers' prices (for 'Developer API') — Intermediate consumption. Statizoid refreshes it automatically from the source and publishes the full history for both places.
Individual pages
About this data
This dataset provides the whole set of OECD SUT Use at purchasers' prices and is recommended for users who wish to query a large amount of data. It is not designed for visualising results using the Table and Chart buttons. To access the ‘Developer API query builder’, click on the ‘Developer API’ button above. The application programming interface (API), based on the SDMX standard, allows a developer to access the data using simple RESTful URL and HTTP header options for various choices of response formats including JSON. The query filter is generated according to the current data selection. To change the data selection, use the filters on the left. To get started check the API documentation. For any question contact us The mapping table between old OECD.Stat and new OECD Data Explorer codes is available here Historical data for Korea from 2015 to 2019 is available here Historical data for Norway from 2010 to 2021 is available here Japanese data from 2011 to 2021 according to 2015 benchmark year is available here