Binga fire, 30 October 2026 Binga
The fire started on 30 October 2026 in Binga, Zimbabwe, and satellites saw it burning for 4 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 3,465 hectares from heat detections, spread across a single municipality.
It is the 130th largest in Matabeleland North since 2016 (of 492 with a page). Number 51 in Zimbabwe in 2026, of 387.
Compare with…
Suggestions: Binga · 2020Binga · 2017Binga · 2022Binga · 2017
Is it still active?
Satellites detected fire on 2 Nov 2026, 12:04 UTC. Everything suggests it is still burning. Satellites pass a few times a day and cloud or smoke can hide the fire: a lack of detections is not an official extinction. Each country’s emergency service declares a fire contained or out.
- Burnt area
- 3,465ha
- GWIS perimeter (Copernicus)
- Duration
- 4days
- 30 Oct 2026 – 2 Nov 2026
- Municipalities hit
- 1
- districts
- Started on
- 30 Oct
- 2026
- Heat detections
- 59
- in a single hotspot: 54 MW
- Danger at start
- 38
- High · FWI index
- Average daily power
- 109MW
- 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 23 days without rain (1 mm or more) when it started.
This area had burned before
56% of the perimeter overlaps earlier fires recorded since 2016: 1,206 ha in 2017, 1,593 ha in 2020, 841 ha in 2022. Part of it burned more than once, so the yearly figures add up to more than the 1,952 ha that had burned before.
- 1,593 ha Binga fire, September 2020 5,389 ha in total; the hectares shown are those it shares with this fire
- 1,178 ha Binga fire, September 2017 2,242 ha in total; the hectares shown are those it shares with this fire
- 841 ha Binga fire, October 2022 3,573 ha in total; the hectares shown are those it shares with this fire
- 27 ha Binga fire, October 2017 1,219 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
-
Binga where it started3,486 ha reached on 30 Oct0.3 %
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.
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) · forecast models, provisional until the ERA5 reanalysis arrives
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 30 Oct | 32.5 °C | 28 % | 36 km/h | 0.0 mm | High 38 |
| 31 Oct | 33.3 °C | 16 % | 40 km/h | 0.0 mm | Very high 39 |
| 1 Nov | 35.0 °C | 13 % | 41 km/h | 0.0 mm | Very high 45 |
| 2 Nov | 35.7 °C | 14 % | 44 km/h | 0.0 mm | Very high 48 |
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 29 October 2026 the air beside the fire reached 18 µg/m³ of PM2.5, but no daily average passed the WHO 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 · 59Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 5,389 haBingaSeptember 2020 · 7 days · 1 km away
- 5,162 haBinga22 July 2026 · 5 days · 23 km away
- 5,216 haBinga12 September 2017 · 6 days · 26 km away
- 6,794 haBinga14 September 2025 · 7 days · 32 km away
- 3,805 haBinga27 September 2026 · 2 days · 34 km away
- 5,313 haBinga12 September 2022 · 7 days · 37 km away
Frequently asked questions
- How long did the Binga fire last?
- GWIS (Copernicus) dates it between 30 October 2026 and 2 November 2026: 4 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,465 hectares (34.6 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Binga (3,486 ha, 0.3 %).
- Is the Binga fire still active?
- Yes: satellites detected fire on 2 Nov 2026, 12:04 UTC. Check the emergency service for the official status.
- What was the weather like?
- During the fire the temperature reached 35.7 °C, humidity dropped to 13 % and gusts hit 44 km/h. The fire danger index (FWI) reached 48, 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 · 2 Changes in area, dates, name, official record or merged pages, compared every night since 1 November 2026.
- Area: 2,540 → 3,465 ha.
- Page published (2,540 ha).
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 from the perimeter: the VIIRS detections inside it did not change them. 59 Suomi-NPP VIIRS detections on those dates.
- We have not matched this page with any official record.
- Weather: ECMWF IFS model, provisional until the ERA5 reanalysis arrives.
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.