Croatia vs Japan: SUT Use at purchasers' prices (for 'Developer API') — Intermediate
SUT Use at purchasers' prices (for 'Developer API') — Intermediate over time
- Croatia
- Japan
How they compare
Japan currently reports 590.68 million National currency against 63,103 National currency in Croatia, a difference of 590.61 million National currency.
That makes Japan's figure about 9,360.5 times Croatia's.
Across all 8 years both countries report, Japan has been ahead every year.
Croatia ranks 3rd and Japan ranks 2nd of 3 groups.
Japan has averaged higher in every one of the 2 decades both report.
Head to head by decade
| Decade | Croatia | Japan | Difference | Ahead |
|---|---|---|---|---|
| 2010s | 42,018 National currency | 493.04 million National currency | 493.00 million National currency | Japan |
| 2020s | 52,045 National currency | 524.95 million National currency | 524.89 million National currency | Japan |
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 Japan?
- Japan, at 590.68 million National currency against 63,103 National currency in Croatia as of 2022.
- What is the difference in sut use at purchasers' prices (for 'developer api') — intermediate between Croatia and Japan?
- 590.61 million National currency, with Japan ahead.
- How many years of comparable data are there for Croatia and Japan?
- 8 years are reported by both, from 2015 to 2022.
- How do Croatia and Japan rank globally for sut use at purchasers' prices (for 'developer api') — intermediate?
- Croatia ranks 3rd and Japan ranks 2nd of 3 groups.
- 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