Skip to content
worldfires
ZA · South Africa · →

Collins Chabane fire, 15 September 2025 Collins Chabane, Greater Giyani

Out · last detection 18 Sept 2025, 11:19 UTC

The fire started on 15 September 2025 in Collins Chabane, South Africa, and satellites saw it burning for 4 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 6,473 hectares from heat detections, spread across 2 municipalities.

It is the 23th largest in Limpopo since 2016 (of 221 with a page). Number 13 in South Africa in 2025, of 87.

Compare with…
Burnt area
6,473ha
GWIS perimeter (Copernicus)
Duration
4days
15 Sept 2025 – 18 Sept 2025
Municipalities hit
2
municipalities
Started on
15 Sept
2025
Heat detections
126
in a single hotspot: 57 MW
Danger at start
47
Very high · FWI index
Average daily power
372MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 15 Sept18 Sept
18 Sept 2025

How it evolved, day by day

15 Sept 2025 · 6 MW · 4 16 Sept 2025 · 1,393 MW · 100 17 Sept 2025 · 82 MW · 20 18 Sept 2025 · 9 MW · 2
15 Sept 16 Sept 17 Sept 18 Sept

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

The weather it burned in

39°high
51km/h · peak gust
8%lowest humidity

It had gone 8 days without rain (1 mm or more) when it started. Rain came after the fire: 2.0 mm on 20 Sept.

This area had burned before

34% of the perimeter overlaps earlier fires recorded since 2016: 2,180 ha in 2023.

How big is it?

10 km
It burned the equivalent of 4.1% of the area of London (65 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

  1. Collins Chabane where it started
    6,414 ha reached on 15 Sept
    1.3 %
  2. 97 ha
    0.0 %

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 2025
Built-up area0.40 ha
Residents< 20

Inside the perimeter there were about 0.40 hectares of 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)
15 Sept 32.9 °C 21 % 30 km/h 0.0 mm Very high 47
16 Sept 38.7 °C 8 % 31 km/h 0.0 mm Extreme 53
17 Sept 27.5 °C 32 % 51 km/h 0.0 mm Extreme 53
18 Sept 29.1 °C 44 % 27 km/h 0.0 mm High 29
19 Sept after 33.3 °C 33 % 53 km/h 0.0 mm Very high 46
20 Sept after 27.5 °C 51 % 38 km/h 2.0 mm Moderate 14

Before and after, from space

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

Before · 8 Sept 2025
After · 25 Sept 2025

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 · Copernicus

On 19 September 2025 the air beside the fire reached 26 µg/m³ of PM2.5. That day averaged 18: 1.2 times the WHO daily guideline (15).

PM2.5 peak26 µg/m³
Days over the guideline2 days
PM1026 µg/m³
Optical depth0.49
131415161718192021
Good Fair Moderate Poor Very poor Extremely poor

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 · 126Every 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 timeSatelliteFRP (MW)LatLon

Other fires nearby

All fires in South Africa ›

Frequently asked questions

How long did the Collins Chabane fire last?
GWIS (Copernicus) dates it between 15 September 2025 and 18 September 2025: 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 6,473 hectares (64.7 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Collins Chabane (6,414 ha, 1.3 %); Greater Giyani (97 ha, 0.0 %).
What was the weather like?
During the fire the temperature reached 38.7 °C, humidity dropped to 8 % and gusts hit 51 km/h. The fire danger index (FWI) reached 53, class Extreme.
Where does this data come from?
From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of South Africa (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: 10177 · 112 · Emergency number and official warnings ›

Satellite cross-check

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?

We will only use your email to reply about this report. Privacy. This is not an emergency service: if there is a fire now, call 10177 · 112.

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. 126 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.

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 ADM3 (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.