Gualeguay fire, 25 December 2022 Gualeguay
The fire started on 25 December 2022 in Gualeguay, Argentina, and satellites saw it burning for 27 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 7,955 hectares from heat detections, spread across a single municipality.
It is the 23th largest in Buenos Aires since 2016 (of 210 with a page). Number 40 in Argentina in 2022, of 442.
Compare with…
- Burnt area
- 7,955ha
- GWIS perimeter (Copernicus)
- Duration
- 27days
- 25 Dec 2022 – 20 Jan 2023
- Municipalities hit
- 1
- departments
- Started on
- 25 Dec
- 2022
- Heat detections
- 1,056
- in a single hotspot: 135 MW
- Danger at start
- 4
- Very low · FWI index
- Average daily power
- 664MW
- detected power per day, on average
Where it burned
How it evolved, day by day
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
It had gone 0 days without rain (1 mm or more) when it started. Rain came after the fire: 3.1 mm on 21 Jan.
This area had burned before
62% of the perimeter overlaps earlier fires recorded since 2016: 1,908 ha in 2020, 4,026 ha in 2021, 1,260 ha in 2022. Part of it burned more than once, so the yearly figures add up to more than the 4,935 ha that had burned before.
- 3,143 ha Gualeguay fire, August 2021 12,331 ha in total; the hectares shown are those it shares with this fire
- 377 ha Gualeguay fire, August 2022 7,983 ha in total; the hectares shown are those it shares with this fire
- 363 ha Gualeguay fire, September 2020 2,200 ha in total; the hectares shown are those it shares with this fire
- 237 ha Gualeguay fire, July 2022 23,596 ha in total; the hectares shown are those it shares with this fire
- 134 ha Gualeguay fire, September 2021 3,714 ha in total; the hectares shown are those it shares with this fire
- 55 ha Gualeguay fire, September 2022 5,162 ha in total; the hectares shown are those it shares with this fire
- 36 ha Gualeguay fire, September 2020 2,365 ha in total; the hectares shown are those it shares with this fire
How big is it?
London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).
Paris boundary: geoBoundaries · Institut national de l'information géographique et forestière (IGN-F) (Etalab Open License 2.0).
Madrid boundary: geoBoundaries · Open Data ESRI, IGN Central Registry of Cartography Area (CC BY 4.0).
Berlin boundary: geoBoundaries · Federal Agency for Cartography and Geodesy (dl-de/by-2-0).
This compares size, not location: both shapes are at the same scale, north up, centred on each other.
What happened to each town
-
Gualeguay where it started8,010 ha reached on 25 Dec1.2 %
Burnt area inside each municipality, from crossing the GWIS perimeter with administrative boundaries. The distance runs from the point marking the centre of each area to the nearest fire: staying a kilometre away does not mean it reached the houses.
People and buildings inside the perimeter
GHSL 2020Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2020, satellite-based estimate).
This is an estimate on 100 m cells, made from satellite imagery and census data: it does not mean that homes burned or that anyone was harmed. The perimeter also contains land that never burned.
Source: Global Human Settlement Layer (GHS-BUILT-S and GHS-POP R2023A), European Commission Joint Research Centre (JRC), © European Union, CC BY 4.0. Sum inside the perimeter computed by WorldFires. human-settlement.emergency.copernicus.eu
The weather day by day
ECMWF ERA5 reanalysis at the fire location, the standard reference for past weather, and the Canadian Fire Weather Index (the same system Copernicus uses), computed by WorldFires from that data. Days after the fire run until the first rain.
Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 25 Dec | 24.8 °C | 36 % | 32 km/h | 0.0 mm | Very low 4 |
| 26 Dec | 29.5 °C | 27 % | 18 km/h | 0.0 mm | Low 10 |
| 27 Dec | 31.6 °C | 24 % | 24 km/h | 0.0 mm | Moderate 13 |
| 28 Dec | 31.4 °C | 24 % | 45 km/h | 0.4 mm | Moderate 20 |
| 29 Dec | 31.6 °C | 29 % | 31 km/h | 0.0 mm | Moderate 17 |
| 30 Dec | 36.5 °C | 24 % | 37 km/h | 0.0 mm | Moderate 20 |
| 31 Dec | 36.8 °C | 31 % | 39 km/h | 0.2 mm | High 24 |
| 1 Jan | 26.1 °C | 49 % | 49 km/h | 10.2 mm | Very low 1 |
| 2 Jan | 31.0 °C | 26 % | 42 km/h | 0.0 mm | Moderate 12 |
| 3 Jan | 32.3 °C | 19 % | 44 km/h | 0.0 mm | Moderate 20 |
| 4 Jan | 32.0 °C | 24 % | 27 km/h | 0.0 mm | Moderate 18 |
| 5 Jan | 34.0 °C | 17 % | 28 km/h | 0.0 mm | Moderate 21 |
| 6 Jan | 36.4 °C | 24 % | 34 km/h | 0.0 mm | High 24 |
| 7 Jan | 35.5 °C | 27 % | 38 km/h | 0.0 mm | High 26 |
| 8 Jan | 34.5 °C | 32 % | 35 km/h | 0.0 mm | High 23 |
| 9 Jan | 35.5 °C | 26 % | 36 km/h | 0.0 mm | High 24 |
| 10 Jan | 37.3 °C | 24 % | 28 km/h | 0.0 mm | High 24 |
| 11 Jan | 29.4 °C | 51 % | 44 km/h | 1.3 mm | Low 10 |
| 12 Jan | 30.2 °C | 29 % | 32 km/h | 0.0 mm | Moderate 19 |
| 13 Jan | 31.0 °C | 20 % | 42 km/h | 0.0 mm | High 28 |
| 14 Jan | 33.2 °C | 16 % | 22 km/h | 0.0 mm | High 24 |
| 15 Jan | 36.4 °C | 20 % | 23 km/h | 0.0 mm | High 26 |
| 16 Jan | 37.2 °C | 22 % | 20 km/h | 0.0 mm | High 30 |
| 17 Jan | 38.0 °C | 22 % | 37 km/h | 0.0 mm | High 37 |
| 18 Jan | 31.5 °C | 32 % | 45 km/h | 0.0 mm | High 34 |
| 19 Jan | 36.0 °C | 40 % | 34 km/h | 0.0 mm | High 26 |
| 20 Jan | 36.9 °C | 38 % | 44 km/h | 10.2 mm | Low 8 |
| 21 Jan after | 33.2 °C | 37 % | 36 km/h | 3.1 mm | Low 7 |
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
If the day is cloudy, change the date: each satellite passes once a day. In false colour the burnt ground looks brown or red.
The smoke
CAMS · CopernicusOn 1 January 2023 the air beside the fire reached 518 µg/m³ of PM2.5. That day averaged 138: 9.2 times the WHO daily guideline (15).
Particles from the Copernicus CAMS model at the centre of the perimeter; these are not measurements in each town. The pale bar is the worst hour, the solid one the daily average.
Open-Meteo.com (CC BY 4.0) · Copernicus Atmosphere Monitoring Service (CAMS)
Detections table · 1,056Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 6,205 haGualeguay6 February 2023 · 41 days · 10 km away
- 7,983 haGualeguay11 August 2022 · 16 days · 12 km away
- 23,596 haGualeguay29 July 2022 · 44 days · 17 km away
- 14,934 haIslas del Ibicuy12 August 2020 · 18 days · 18 km away
- 12,331 haGualeguay13 August 2021 · 20 days · 18 km away
- 29,172 haGualeguay10 August 2020 · 21 days · 26 km away
Frequently asked questions
- How long did the Gualeguay fire last?
- GWIS (Copernicus) dates it between 25 December 2022 and 20 January 2023: 27 days between the first and last heat detection of the perimeter.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 7,955 hectares (79.6 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Gualeguay (8,010 ha, 1.2 %).
- What was the weather like?
- During the fire the temperature reached 38.0 °C, humidity dropped to 16 % and gusts hit 49 km/h. The fire danger index (FWI) reached 37, class High.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Argentina (geoBoundaries). It is not an official report.
Where to verify it
A satellite detection is not an official report. Final figures and the fire’s status are published by each country’s emergency service.
Emergency number: 911 · 100 · Emergency number and official warnings ›
Satellite cross-check
History of this page Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
No changes since 24 October 2026.
Does something look wrong on this page?
This page is built from satellite data and official records, and it sometimes gets things wrong: the wrong dates, the wrong town, two fires merged into one, or something that was not a wildfire at all. If you know this fire first-hand (you live nearby, saw it, fought it or reported on it), tell us what really happened and we will check it.
Report an error
How we know this
- Perimeter: GWIS (Copernicus), rebuilt from heat detections rather than mapped on imagery; 2 polygons grouped in this page.
- Dates from the perimeter: the VIIRS detections inside it did not change them. 1,056 Suomi-NPP VIIRS detections on those dates.
- We have not matched this page with any official record.
- Weather: Copernicus ERA5 reanalysis at the fire location, in cells of about 25 km.
- Built-up area and population come from the JRC Global Human Settlement Layer (epoch 2020, 100 m cells), summed inside the perimeter: an estimate of what was there, not a damage count.
Where this data comes from
The perimeter comes from the Copernicus Global Wildfire Information System (GWIS), which rebuilds it from MODIS and VIIRS heat detections and publishes it under CC BY 4.0. It is not measured on imagery as in Europe, so it is an estimate. Heat detections come from the VIIRS sensors aboard Suomi-NPP and NOAA-20, distributed by NASA FIRMS at 375 m resolution. Municipal boundaries come from geoBoundaries ADM2 (Creative Commons Attribution 3.0 Intergovernmental Organisations (CC BY 3.0 IGO)). The area per municipality is computed by WorldFires by crossing the perimeter with those boundaries, so it may differ from each country’s official figure.