Colniza fire, 7 August 2026 Colniza
The fire started on 7 August 2026 in Colniza, Brazil, and satellites saw it burning for 26 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 7,040 hectares from heat detections, spread across a single municipality.
It is the 729th largest in Mato Grosso since 2016 (of 1996 with a page). Number 215 in Brazil in 2026, of 769.
Compare with…
- Burnt area
- 7,040ha
- GWIS perimeter (Copernicus)
- Duration
- 26days
- 7 Aug 2026 – 1 Sept 2026
- Municipalities hit
- 1
- municipalities
- Started on
- 7 Aug
- 2026
- Heat detections
- 303
- in a single hotspot: 132 MW
- Danger at start
- 18
- Moderate · FWI index
- Average daily power
- 159MW
- 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 3 days without rain (1 mm or more) when it started. Rain came after the fire: 1.7 mm on 8 Sept.
This area had burned before
100% of the perimeter overlaps earlier fires recorded since 2016: 1,092 ha in 2017, 1,102 ha in 2019, 7,279 ha in 2022, 1,504 ha in 2023, 6,898 ha in 2024, 6,593 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 7,043 ha that had burned before.
- 6,898 ha Colniza fire, July 2024 45,354 ha in total; the hectares shown are those it shares with this fire
- 5,609 ha Colniza fire, August 2025 23,149 ha in total; the hectares shown are those it shares with this fire
- 4,221 ha Colniza fire, August 2022 20,521 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
-
Colniza where it started7,081 ha reached on 7 Aug0.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 2025Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2025, 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. The GHSL 2025 epoch is a projection made from 2020 and earlier data.
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) |
|---|---|---|---|---|---|
| 7 Aug | 33.8 °C | 42 % | 20 km/h | 0.1 mm | Moderate 18 |
| 8 Aug | 34.2 °C | 41 % | 25 km/h | 0.0 mm | Moderate 19 |
| 9 Aug | 34.0 °C | 44 % | 26 km/h | 0.0 mm | Moderate 19 |
| 10 Aug | 33.6 °C | 47 % | 28 km/h | 1.2 mm | Moderate 14 |
| 11 Aug | 32.7 °C | 49 % | 21 km/h | 0.0 mm | Moderate 15 |
| 12 Aug | 29.5 °C | 65 % | 27 km/h | 3.2 mm | Very low 3 |
| 13 Aug | 32.1 °C | 50 % | 34 km/h | 0.1 mm | Low 8 |
| 14 Aug | 33.1 °C | 43 % | 22 km/h | 0.0 mm | Moderate 14 |
| 15 Aug | 34.5 °C | 29 % | 29 km/h | 0.0 mm | High 24 |
| 16 Aug | 33.9 °C | 36 % | 28 km/h | 0.0 mm | High 23 |
| 17 Aug | 33.6 °C | 41 % | 33 km/h | 0.0 mm | High 25 |
| 18 Aug | 32.4 °C | 48 % | 25 km/h | 0.1 mm | Moderate 19 |
| 19 Aug | 33.3 °C | 43 % | 20 km/h | 0.0 mm | Moderate 20 |
| 20 Aug | 33.9 °C | 38 % | 27 km/h | 0.0 mm | High 22 |
| 21 Aug | 33.4 °C | 40 % | 27 km/h | 0.0 mm | High 23 |
| 22 Aug | 34.7 °C | 35 % | 30 km/h | 0.0 mm | High 24 |
| 23 Aug | 33.5 °C | 41 % | 18 km/h | 0.0 mm | High 23 |
| 24 Aug | 32.6 °C | 51 % | 25 km/h | 0.8 mm | Moderate 15 |
| 25 Aug | 34.6 °C | 40 % | 21 km/h | 0.0 mm | Moderate 20 |
| 26 Aug | 34.1 °C | 40 % | 22 km/h | 0.0 mm | Moderate 21 |
| 27 Aug | 33.4 °C | 52 % | 31 km/h | 0.8 mm | Moderate 18 |
| 28 Aug | 33.0 °C | 52 % | 36 km/h | 0.2 mm | Moderate 18 |
| 29 Aug | 34.5 °C | 42 % | 25 km/h | 0.0 mm | Moderate 21 |
| 30 Aug | 34.7 °C | 46 % | 29 km/h | 0.2 mm | High 22 |
| 31 Aug | 35.4 °C | 44 % | 30 km/h | 0.0 mm | High 22 |
| 1 Sept | 34.8 °C | 43 % | 18 km/h | 0.2 mm | Moderate 20 |
| 2 Sept after | 33.8 °C | 45 % | 23 km/h | 0.2 mm | Moderate 21 |
| 3 Sept after | 34.3 °C | 44 % | 27 km/h | 0.0 mm | High 23 |
| 4 Sept after | 33.8 °C | 43 % | 20 km/h | 0.6 mm | Moderate 21 |
| 5 Sept after | 33.9 °C | 44 % | 27 km/h | 0.4 mm | Moderate 21 |
| 6 Sept after | 33.2 °C | 45 % | 22 km/h | 0.3 mm | High 24 |
| 7 Sept after | 32.2 °C | 50 % | 27 km/h | 0.3 mm | High 24 |
| 8 Sept after | 33.6 °C | 45 % | 25 km/h | 1.7 mm | Low 11 |
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 23 August 2026 the air beside the fire reached 414 µg/m³ of PM2.5. That day averaged 226: 15 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 · 303Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 45,354 haColniza6 July 2024 · 73 days · 9 km away
- 23,149 haColniza8 August 2025 · 26 days · 10 km away
- 20,521 haColniza11 August 2022 · 32 days · 10 km away
- 17,234 haColniza7 August 2019 · 19 days · 16 km away
- 10,457 haColniza11 August 2021 · 25 days · 26 km away
- 7,112 haColniza11 August 2022 · 35 days · 28 km away
Frequently asked questions
- How long did the Colniza fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 7 August 2026 to 1 September 2026 (26 days). The perimeter dates it from 14 August 2026 to 31 August 2026.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 7,040 hectares (70.4 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Colniza (7,081 ha, 0.2 %).
- What was the weather like?
- During the fire the temperature reached 35.4 °C, humidity dropped to 29 % and gusts hit 36 km/h. The fire danger index (FWI) reached 25, class High.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Brazil (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: 193 · Emergency number and official warnings ›
Satellite cross-check
History of this page · 1 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
- Last day with fire: 31 August 2026 → 1 September 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.
- Dates adjusted with the VIIRS detections inside the perimeter, which said 14 August 2026 to 31 August 2026. 303 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 2025, 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.