Stellenbosch fire, January 2026 Stellenbosch, Drakenstein, Breede Valley
The fire started on 8 January 2026 in Stellenbosch, South Africa, and satellites saw it burning for 20 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 36,649 hectares from heat detections, spread across 4 municipalities.
It is the 3th largest in Western Cape since 2016 (of 164 with a page). The largest in South Africa in 2026, of 147.
Compare with…
- Burnt area
- 36,649ha
- GWIS perimeter (Copernicus)
- Duration
- 20days
- 8 Jan 2026 – 27 Jan 2026
- Municipalities hit
- 4
- municipalities
- Started on
- 8 Jan
- 2026
- Heat detections
- 1,584
- in a single hotspot: 620 MW
- Danger at start
- 17
- Moderate · FWI index
- Average daily power
- 1.6GW
- 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 0 days without rain (1 mm or more) when it started. Rain came after the fire: 1.6 mm on 3 Feb.
This area had burned before
45% of the perimeter overlaps earlier fires recorded since 2016: 308 ha in 2016, 4,345 ha in 2019, 7,709 ha in 2020, 4,829 ha in 2021, 30 ha in 2024.
- 7,709 ha Drakenstein fire, February 2020 12,648 ha in total; the hectares shown are those it shares with this fire
- 4,829 ha Theewaterskloof fire, February 2021 15,825 ha in total; the hectares shown are those it shares with this fire
- 4,345 ha Theewaterskloof fire, February 2019 7,148 ha in total; the hectares shown are those it shares with this fire
- 30 ha Breede Valley fire, February 2024 4,847 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
-
Stellenbosch where it started17,861 ha reached on 7 Jan21 %
-
12,820 ha reached on 9 Jan8.3 %
-
3,498 ha reached on 11 Jan0.9 %
-
2,613 ha reached on 8 Jan0.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 were about 38 hectares of built-up land and about 2,400 residents (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) |
|---|---|---|---|---|---|
| 7 Jan | 29.9 °C | 27 % | 34 km/h | 0.4 mm | Moderate 17 |
| 8 Jan | 27.7 °C | 30 % | 66 km/h | 0.0 mm | High 26 |
| 9 Jan | 28.4 °C | 32 % | 62 km/h | 0.1 mm | High 27 |
| 10 Jan | 33.2 °C | 30 % | 49 km/h | 0.0 mm | High 26 |
| 11 Jan | 35.8 °C | 21 % | 38 km/h | 0.0 mm | High 30 |
| 12 Jan | 32.3 °C | 38 % | 40 km/h | 0.0 mm | High 27 |
| 13 Jan | 33.0 °C | 29 % | 40 km/h | 0.0 mm | High 28 |
| 14 Jan | 29.9 °C | 31 % | 60 km/h | 0.2 mm | High 33 |
| 15 Jan | 19.9 °C | 56 % | 56 km/h | 2.4 mm | Low 6 |
| 16 Jan | 24.7 °C | 43 % | 43 km/h | 0.0 mm | Moderate 13 |
| 17 Jan | 24.7 °C | 35 % | 58 km/h | 0.3 mm | High 21 |
| 18 Jan | 24.1 °C | 37 % | 45 km/h | 0.0 mm | Moderate 20 |
| 19 Jan | 28.6 °C | 29 % | 56 km/h | 0.0 mm | High 27 |
| 20 Jan | 30.1 °C | 30 % | 63 km/h | 0.0 mm | High 30 |
| 21 Jan | 34.2 °C | 22 % | 44 km/h | 0.0 mm | High 31 |
| 22 Jan | 27.4 °C | 38 % | 46 km/h | 0.0 mm | High 28 |
| 23 Jan | 28.4 °C | 30 % | 35 km/h | 0.0 mm | High 25 |
| 24 Jan | 32.7 °C | 23 % | 35 km/h | 0.0 mm | High 30 |
| 25 Jan | 33.6 °C | 23 % | 38 km/h | 0.0 mm | High 31 |
| 26 Jan | 29.3 °C | 30 % | 48 km/h | 0.6 mm | High 27 |
| 27 Jan | 29.0 °C | 36 % | 41 km/h | 0.0 mm | High 27 |
| 28 Jan after | 29.2 °C | 34 % | 53 km/h | 0.0 mm | High 30 |
| 29 Jan after | 33.6 °C | 24 % | 36 km/h | 0.0 mm | High 30 |
| 30 Jan after | 34.6 °C | 26 % | 38 km/h | 0.0 mm | High 32 |
| 31 Jan after | 32.5 °C | 32 % | 48 km/h | 0.0 mm | High 35 |
| 1 Feb after | 33.2 °C | 27 % | 40 km/h | 0.0 mm | High 31 |
| 2 Feb after | 31.3 °C | 40 % | 40 km/h | 0.5 mm | High 29 |
| 3 Feb after | 32.0 °C | 38 % | 33 km/h | 1.6 mm | Moderate 16 |
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 11 January 2026 the air beside the fire reached 87 µg/m³ of PM2.5. That day averaged 50: 3.3 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 · 1,584Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 12,648 haDrakensteinFebruary 2020 · 8 days · 7 km away
- 7,148 haTheewaterskloof18 February 2019 · 6 days · 12 km away
- 7,971 haDrakensteinFebruary 2017 · 6 days · 18 km away
- 15,825 haTheewaterskloofFebruary 2021 · 9 days · 19 km away
- 8,831 haCity of Cape TownJanuary 2017 · 9 days · 32 km away
- 11,589 haTheewaterskloofJanuary 2019 · 5 days · 34 km away
Frequently asked questions
- How long did the Stellenbosch fire last?
- GWIS (Copernicus) dates it between 8 January 2026 and 27 January 2026: 20 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 36,649 hectares (366.5 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 4 municipalities: Stellenbosch (17,861 ha, 21 %); Drakenstein (12,820 ha, 8.3 %); Breede Valley (3,498 ha, 0.9 %); Theewaterskloof (2,613 ha, 0.8 %).
- What was the weather like?
- During the fire the temperature reached 35.8 °C, humidity dropped to 21 % and gusts hit 66 km/h. The fire danger index (FWI) reached 33, class High.
- 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.
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; 2 polygons grouped in this page.
- Dates from the perimeter: the VIIRS detections inside it did not change them. 1,584 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 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.