Latvia vs Steiermark: Organic animal farming by utilised agricultural area, livestock unit
Latvia
68,630 Livestock unit (LSU)
in 2023
Steiermark
60,250 Livestock unit (LSU)
in 2023
Latvia rank
13th
Steiermark rank
10th
Organic animal farming by utilised agricultural area, livestock unit over time
- Latvia
- Steiermark
How they compare
Latvia currently reports 68,630 Livestock unit (LSU) against 60,250 Livestock unit (LSU) in Steiermark, a difference of 8,380 Livestock unit (LSU).
That makes Latvia's figure about 1.1 times Steiermark's.
The two have swapped places 1 time across 5 shared years of data; in 2010 it was Steiermark ahead.
Latvia ranks 13th and Steiermark ranks 10th of 25 countries.
Latvia has averaged higher in every one of the 2 decades both report.
Head to head by decade
| Decade | Latvia | Steiermark | Difference | Ahead |
|---|---|---|---|---|
| 2010s | 57,953 Livestock unit (LSU) | 56,810 Livestock unit (LSU) | 1,143 Livestock unit (LSU) | Latvia |
| 2020s | 78,130 Livestock unit (LSU) | 63,125 Livestock unit (LSU) | 15,005 Livestock unit (LSU) | Latvia |
Averages of every year both report within each decade.
Frequently asked questions
- Which has higher organic animal farming by utilised agricultural area, livestock unit, Latvia or Steiermark?
- Latvia, at 68,630 Livestock unit (LSU) against 60,250 Livestock unit (LSU) in Steiermark as of 2023.
- What is the difference in organic animal farming by utilised agricultural area, livestock unit between Latvia and Steiermark?
- 8,380 Livestock unit (LSU), with Latvia ahead.
- How many years of comparable data are there for Latvia and Steiermark?
- 5 years are reported by both, from 2010 to 2023.
- How do Latvia and Steiermark rank globally for organic animal farming by utilised agricultural area, livestock unit?
- Latvia ranks 13th and Steiermark ranks 10th of 25 countries.
- Where does this data come from?
- Eurostat, published as Organic animal farming by utilised agricultural area, livestock unit, economic size of the farm and NUTS 2 region. Statizoid refreshes it automatically from the source and publishes the full history for both places.