Croatia vs Lithuania: Water use in the manufacturing industry by activity and supply
Croatia
12.09 Million cubic metres
in 2024
Lithuania
10.38 Million cubic metres
in 2024
Croatia rank
17th
Lithuania rank
19th
Water use in the manufacturing industry by activity and supply over time
- Croatia
- Lithuania
How they compare
Croatia currently reports 12.09 Million cubic metres against 10.38 Million cubic metres in Lithuania, a difference of 1.71 Million cubic metres.
That makes Croatia's figure about 1.2 times Lithuania's.
Across all 25 years both countries report, Croatia has been ahead every year.
Croatia ranks 17th and Lithuania ranks 19th of 33 countries.
Croatia has averaged higher in every one of the 3 decades both report.
Head to head by decade
| Decade | Croatia | Lithuania | Difference | Ahead |
|---|---|---|---|---|
| 2000s | 12.97 Million cubic metres | 9.61 Million cubic metres | 3.36 Million cubic metres | Croatia |
| 2010s | 10.96 Million cubic metres | 9.02 Million cubic metres | 1.95 Million cubic metres | Croatia |
| 2020s | 11.46 Million cubic metres | 10.3 Million cubic metres | 1.17 Million cubic metres | Croatia |
Averages of every year both report within each decade.
Frequently asked questions
- Which has higher water use in the manufacturing industry by activity and supply, Croatia or Lithuania?
- Croatia, at 12.09 Million cubic metres against 10.38 Million cubic metres in Lithuania as of 2024.
- What is the difference in water use in the manufacturing industry by activity and supply between Croatia and Lithuania?
- 1.71 Million cubic metres, with Croatia ahead.
- How many years of comparable data are there for Croatia and Lithuania?
- 25 years are reported by both, from 2000 to 2024.
- How do Croatia and Lithuania rank globally for water use in the manufacturing industry by activity and supply?
- Croatia ranks 17th and Lithuania ranks 19th of 33 countries.
- Where does this data come from?
- Eurostat, published as Water use in the manufacturing industry by activity and supply category. Statizoid refreshes it automatically from the source and publishes the full history for both places.