How long did the Bindura fire last?

GWIS (Copernicus) dates it between 3 October 2022 and 6 October 2022: 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 1,016 hectares (10.2 km²). It is an estimate: official national figures may differ.

Which municipalities burned?

The fire only entered Bindura (1,022 ha, 0.4 %).

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.

ZW · Zimbabwe · 2022-10-03 → 2022-10-06

Bindura fire, 3 October 2022 Bindura

Out · last detection 6 Oct 2022, 22:41 UTC

The fire started on 3 October 2022 in Bindura, Zimbabwe, and satellites saw it burning for 4 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,016 hectares from heat detections, spread across a single municipality.

It is the 325th largest in Mashonaland Central since 2016 (of 334 with a page). Number 338 in Zimbabwe in 2022, of 346.

Compare with…

Suggestions: Bindura · 2019 Bindura · 2022 Bindura · 2020 Bindura · 2016

Burnt area: 1,016ha; GWIS perimeter (Copernicus)
Duration: 4days; 3 Oct 2022 – 6 Oct 2022
Municipalities hit: 1; districts
Started on: 3 Oct; 2022
Heat detections: 34; in a single hotspot: 51 MW
Average daily power: 58MW; detected power per day, on average

HOTSPOTS BY DAY 3 Oct6 Oct

Play back 6 Oct 2022

How it evolved, day by day

3 Oct 4 Oct 5 Oct 6 Oct

Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.

This area had burned before

38% of the perimeter overlaps earlier fires recorded since 2016: 391 ha in 2019.

391 ha Bindura fire, September 2019 1,313 ha in total; the hectares shown are those it shares with this fire

How big is it?

It burned the equivalent of 0.6% of the area of London (10 km² against 1,583 km²).

London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).

This compares size, not location: both shapes are at the same scale, north up, centred on each other.

What happened to each town

Bindura where it started

1,022 ha reached on 3 Oct

0.4 %

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.

Before and after, from space

Drag the line to compare the same ground before the fire and after it.

↔

Before · 26 Sept 2022

After · 13 Oct 2022

Before After

If the day is cloudy, change the date: each satellite passes once a day. In false colour the burnt ground looks brown or red.

Detections table · 34Every satellite heat detection, one by one, with time, satellite, power and coordinates.

⬇ Download CSV Times in UTC. Each detection is a 375 m pixel: a large fire yields hundreds per pass.

Date and time	Satellite	FRP (MW)	Lat	Lon

Other fires nearby

All fires in Zimbabwe ›

Frequently asked questions

How long did the Bindura fire last?: GWIS (Copernicus) dates it between 3 October 2022 and 6 October 2022: 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 1,016 hectares (10.2 km²). It is an estimate: official national figures may differ.
Which municipalities burned?: The fire only entered Bindura (1,022 ha, 0.4 %).
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

NASA FIRMS ↗
GWIS · Copernicus ↗

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.

RSS Changes to this page

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

What do you think is wrong?

Dates or duration Place or towns Burned area Name It was not a wildfire Same fire as another page Something else

What really happened?

Your connection to the fire (optional) Email (optional)

We will only use your email to reply about this report. Privacy.

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. 34 Suomi-NPP VIIRS detections on those dates.
We have not matched this page with any official record.

How we build fire pages: methodology ›

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.

Where it burned