Mbire fire, 23 August 2026 Mbire
The fire started on 23 August 2026 in Mbire, Zimbabwe, and satellites saw it burning for 13 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 3,781 hectares from heat detections, spread across a single municipality.
It is the 10th largest in Mashonaland Central since 2016 (of 334 with a page). Number 40 in Zimbabwe in 2026, of 378.
The power measured by the satellite is low (27.4 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.
Compare with…
Suggestions: Mbire · 2018Mbire · 2021Mbire · 2017Mbire · 2019
- Burnt area
- 3,781ha
- GWIS perimeter (Copernicus)
- Duration
- 13days
- 23 Aug 2026 – 4 Sept 2026
- Municipalities hit
- 1
- districts
- Started on
- 23 Aug
- 2026
- Heat detections
- 88
- in a single hotspot: 27 MW
- Danger at start
- 32
- High · FWI index
- Average daily power
- 43MW
- 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 more than two months without rain (1 mm or more) when it started.
This area had burned before
39% of the perimeter overlaps earlier fires recorded since 2016: 5 ha in 2016, 315 ha in 2017, 1,161 ha in 2018, 224 ha in 2019, 471 ha in 2021. Part of it burned more than once, so the yearly figures add up to more than the 1,471 ha that had burned before.
- 1,161 ha Mbire fire, September 2018 2,213 ha in total; the hectares shown are those it shares with this fire
- 471 ha Mbire fire, October 2021 1,692 ha in total; the hectares shown are those it shares with this fire
- 287 ha Mbire fire, October 2017 1,594 ha in total; the hectares shown are those it shares with this fire
- 224 ha Mbire fire, October 2019 1,032 ha in total; the hectares shown are those it shares with this fire
- 28 ha Mbire fire, November 2017 1,389 ha in total; the hectares shown are those it shares with this fire
- 5 ha Mbire fire, October 2016 1,394 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
-
Mbire where it started3,803 ha reached on 23 Aug0.8 %
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) |
|---|---|---|---|---|---|
| 23 Aug | 32.0 °C | 28 % | 34 km/h | 0.0 mm | High 32 |
| 24 Aug | 30.1 °C | 34 % | 48 km/h | 0.0 mm | Very high 39 |
| 25 Aug | 29.3 °C | 33 % | 40 km/h | 0.0 mm | High 35 |
| 26 Aug | 31.1 °C | 27 % | 36 km/h | 0.0 mm | High 34 |
| 27 Aug | 28.5 °C | 30 % | 49 km/h | 0.0 mm | Very high 41 |
| 28 Aug | 27.3 °C | 32 % | 46 km/h | 0.0 mm | Very high 39 |
| 29 Aug | 27.1 °C | 43 % | 46 km/h | 0.0 mm | High 33 |
| 30 Aug | 30.5 °C | 37 % | 41 km/h | 0.0 mm | High 32 |
| 31 Aug | 32.6 °C | 30 % | 39 km/h | 0.0 mm | High 35 |
| 1 Sept | 32.9 °C | 27 % | 44 km/h | 0.0 mm | Very high 39 |
| 2 Sept | 31.1 °C | 32 % | 45 km/h | 0.0 mm | Very high 40 |
| 3 Sept | 32.3 °C | 31 % | 44 km/h | 0.0 mm | Very high 41 |
| 4 Sept | 33.6 °C | 30 % | 28 km/h | 0.0 mm | High 34 |
| 5 Sept after | 31.6 °C | 37 % | 44 km/h | 0.0 mm | Very high 40 |
| 6 Sept after | 27.4 °C | 50 % | 44 km/h | 0.1 mm | High 32 |
| 7 Sept after | 30.4 °C | 34 % | 52 km/h | 0.0 mm | Very high 38 |
| 8 Sept after | 27.1 °C | 49 % | 53 km/h | 0.0 mm | High 35 |
| 9 Sept after | 27.8 °C | 33 % | 42 km/h | 0.0 mm | High 33 |
| 10 Sept after | 29.2 °C | 38 % | 45 km/h | 0.0 mm | High 34 |
| 11 Sept after | 31.1 °C | 34 % | 38 km/h | 0.0 mm | High 33 |
| 12 Sept after | 33.0 °C | 34 % | 45 km/h | 0.0 mm | High 37 |
| 13 Sept after | 33.1 °C | 32 % | 41 km/h | 0.0 mm | High 36 |
| 14 Sept after | 33.5 °C | 27 % | 45 km/h | 0.0 mm | Very high 42 |
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 5 September 2026 the air beside the fire reached 65 µg/m³ of PM2.5. That day averaged 41: 2.7 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 · 88Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 23,001 haHurungwe28 September 2022 · 20 days · 20 km away
- 31,897 haHurungwe20 September 2026 · 10 days · 24 km away
- 16,625 haHurungwe19 September 2019 · 7 days · 27 km away
- 18,057 haHurungwe4 September 2021 · 8 days · 29 km away
- 33,869 haHurungwe2 September 2018 · 44 days · 30 km away
- 20,021 haHurungwe 13 October 2026 · 13 days · 36 km away
Frequently asked questions
- How long did the Mbire fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 23 August 2026 to 4 September 2026 (13 days). The perimeter dates it from 23 August 2026 to 3 September 2026.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 3,781 hectares (37.8 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Mbire (3,803 ha, 0.8 %).
- What was the weather like?
- During the fire the temperature reached 33.6 °C, humidity dropped to 27 % and gusts hit 49 km/h. The fire danger index (FWI) reached 41, class Very high.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Zimbabwe (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.
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: 3 September 2026 → 4 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 23 August 2026 to 3 September 2026. 88 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.