Lupane fire, 16 October 2025 Lupane
The fire started on 16 October 2025 in Lupane, Zimbabwe, and satellites saw it burning for 2 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 3,917 hectares from heat detections, spread across a single municipality.
It is the 106th largest in Matabeleland North since 2016 (of 487 with a page). Number 15 in Zimbabwe in 2025, of 150.
- Burnt area
- 3,917ha
- GWIS perimeter (Copernicus)
- Duration
- 2days
- 16 Oct 2025 – 17 Oct 2025
- Municipalities hit
- 1
- districts
- Started on
- 16 Oct
- 2025
- Heat detections
- 131
- in a single hotspot: 100 MW
- Danger at start
- 49
- Very high · FWI index
- Energy released
- 1.8GW
- sum of detected power
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. Rain came after the fire: 4.1 mm on 21 Oct.
This area had burned before
98% of the perimeter overlaps earlier fires recorded since 2016: 55 ha in 2017, 77 ha in 2018, 3,604 ha in 2019, 429 ha in 2021, 2,612 ha in 2022, 45 ha in 2023. Part of it burned more than once, so the yearly figures add up to more than the 3,850 ha that had burned before.
- 3,362 ha Lupane fire, October 2019 26,931 ha in total; the hectares shown are those it shares with this fire
- 2,612 ha Lupane fire, August 2022 66,275 ha in total; the hectares shown are those it shares with this fire
- 429 ha Lupane fire, July 2021 1,040 ha in total; the hectares shown are those it shares with this fire
- 242 ha Lupane fire, October 2019 4,932 ha in total; the hectares shown are those it shares with this fire
- 77 ha Lupane fire, September 2018 6,388 ha in total; the hectares shown are those it shares with this fire
- 55 ha Lupane fire, July 2017 3,776 ha in total; the hectares shown are those it shares with this fire
- 45 ha Lupane fire, September 2023 13,313 ha in total; the hectares shown are those it shares with this fire
What happened to each town
-
Lupane where it started3,939 ha reached on 16 Oct0.4 %
Burnt area inside each municipality, from crossing the GWIS perimeter with administrative boundaries. The distance is from the town centre to the nearest fire: staying a kilometre away does not mean it reached the houses.
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) |
|---|---|---|---|---|---|
| 16 Oct | 37.4 °C | 13 % | 32 km/h | 0.0 mm | Very high 49 |
| 17 Oct | 35.2 °C | 19 % | 50 km/h | 0.0 mm | Extreme 61 |
| 18 Oct after | 35.3 °C | 16 % | 40 km/h | 0.0 mm | Extreme 54 |
| 19 Oct after | 35.6 °C | 17 % | 32 km/h | 0.0 mm | Very high 49 |
| 20 Oct after | 34.0 °C | 24 % | 48 km/h | 0.2 mm | Extreme 56 |
| 21 Oct after | 31.0 °C | 33 % | 45 km/h | 4.1 mm | Moderate 15 |
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 14 October 2025 the air beside the fire reached 26 µg/m³ of PM2.5. That day averaged 16: 1.0 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 · 131Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 26,931 haLupane19 October 2019 · 8 days · 5 km away
- 13,313 haLupane1 September 2023 · 6 days · 14 km away
- 10,854 haLupane10 September 2026 · 11 days · 15 km away
- 23,883 haLupane5 October 2022 · 11 days · 24 km away
- 13,018 haLupane26 August 2019 · 7 days · 26 km away
- 66,275 haLupane29 August 2022 · 20 days · 28 km away
Frequently asked questions
- How long did the Lupane fire last?
- GWIS (Copernicus) dates it between 16 October 2025 and 17 October 2025: 2 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 3,917 hectares (39.2 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Lupane (3,939 ha, 0.4 %).
- What was the weather like?
- During the fire the temperature reached 37.4 °C, humidity dropped to 13 % and gusts hit 50 km/h. The fire danger index (FWI) reached 61, class Extreme.
- 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
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
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.