Korea vs Peru: Agricultural greenhouse gases emissions — Field burning of
Korea
20.68 Tonnes of CO2-equivalent
in 2022
Peru
75.01 Tonnes of CO2-equivalent
in 2021
Korea rank
4th
Peru rank
6th
Agricultural greenhouse gases emissions — Field burning of over time
- Korea
- Peru
How they compare
Peru currently reports 75.01 Tonnes of CO2-equivalent against 20.68 Tonnes of CO2-equivalent in Korea, a difference of 54.33 Tonnes of CO2-equivalent.
That makes Peru's figure about 3.6 times Korea's.
The two have swapped places 1 time across 22 shared years of data; in 2000 it was Korea ahead.
Korea ranks 4th and Peru ranks 6th of 4 groups.
Peru has averaged higher in every one of the 3 decades both report.
Head to head by decade
| Decade | Korea | Peru | Difference | Ahead |
|---|---|---|---|---|
| 2000s | 47.48 Tonnes of CO2-equivalent | 55.83 Tonnes of CO2-equivalent | 8.35 Tonnes of CO2-equivalent | Peru |
| 2010s | 35.95 Tonnes of CO2-equivalent | 72.95 Tonnes of CO2-equivalent | 37 Tonnes of CO2-equivalent | Peru |
| 2020s | 28.65 Tonnes of CO2-equivalent | 74.63 Tonnes of CO2-equivalent | 45.97 Tonnes of CO2-equivalent | Peru |
Averages of every year both report within each decade.
Frequently asked questions
- Which has higher agricultural greenhouse gases emissions — field burning of, Korea or Peru?
- Peru, at 75.01 Tonnes of CO2-equivalent against 20.68 Tonnes of CO2-equivalent in Korea as of 2021.
- What is the difference in agricultural greenhouse gases emissions — field burning of between Korea and Peru?
- 54.33 Tonnes of CO2-equivalent, with Peru ahead.
- How many years of comparable data are there for Korea and Peru?
- 22 years are reported by both, from 2000 to 2021.
- How do Korea and Peru rank globally for agricultural greenhouse gases emissions — field burning of?
- Korea ranks 4th and Peru ranks 6th of 4 groups.
- Where does this data come from?
- Organisation for Economic Co-operation and Development, published as Agricultural greenhouse gases emissions — Field burning of agricultural residues. Statizoid refreshes it automatically from the source and publishes the full history for both places.