Latvia vs United States of America: SUT Use at purchasers' prices (for 'Developer API') — Intermediate

Latvia
38,440 National currency
in 2023
United States of America
21.44 million National currency
in 2024
Latvia rank
6th
United States of America rank
7th

SUT Use at purchasers' prices (for 'Developer API') — Intermediate over time

  • Latvia
  • United States of America
05.0M10.0M15.0M20.0M199720102024

How they compare

United States of America currently reports 21.44 million National currency against 38,440 National currency in Latvia, a difference of 21.40 million National currency.

That makes United States of America's figure about 557.7 times Latvia's.

Across all 14 years both countries report, United States of America has been ahead every year.

Latvia ranks 6th and United States of America ranks 7th of 6 groups.

United States of America has averaged higher in every one of the 2 decades both report.

Head to head by decade

Decade Latvia United States of America Difference Ahead
2010s 25,903 National currency 13.94 million National currency 13.91 million National currency United States of America
2020s 34,464 National currency 18.68 million National currency 18.65 million National currency United States of America

Averages of every year both report within each decade.

Frequently asked questions

Which has higher sut use at purchasers' prices (for 'developer api') — intermediate, Latvia or United States of America?
United States of America, at 21.44 million National currency against 38,440 National currency in Latvia as of 2024.
What is the difference in sut use at purchasers' prices (for 'developer api') — intermediate between Latvia and United States of America?
21.40 million National currency, with United States of America ahead.
How many years of comparable data are there for Latvia and United States of America?
14 years are reported by both, from 2010 to 2023.
How do Latvia and United States of America rank globally for sut use at purchasers' prices (for 'developer api') — intermediate?
Latvia ranks 6th and United States of America ranks 7th of 6 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

Share, cite or embed this page

Cite this page

Latvia vs United States of America: SUT Use at purchasers' prices (for 'Developer API') — Intermediate. Statizoid, drawing on Organisation for Economic Co-operation and Development. Retrieved 21 August 2026, from https://economy.statizoid.com/compare/sut-use-at-purchasers-prices-for-developer-api-intermediate-consumption/latvia-2/united-states/

Embed or link this data

Paste this into a page to link back to these figures. The data itself is free to reuse under OECD Terms and Conditions (attribution required); please keep the attribution.

<a href="https://economy.statizoid.com/compare/sut-use-at-purchasers-prices-for-developer-api-intermediate-consumption/latvia-2/united-states/">Latvia vs United States of America: SUT Use at purchasers' prices (for 'Developer API') — Intermediate</a> — Statizoid

About this data

Indicator
SUT Use at purchasers' prices (for 'Developer API') — Intermediate consumption
Unit
National currency
Source
Organisation for Economic Co-operation and Development
Licence
OECD Terms and Conditions (attribution required)
Coverage
48 places, 677 data points, 1990–2024
Last refreshed

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