Skip to content
worldfires
BW · Botswana · →

Tshabong fire, 3 August 2023 Tshabong

Out · last detection 10 Aug 2023, 11:55 UTC

The fire started on 3 August 2023 in Tshabong, Botswana, and satellites saw it burning for 8 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 5,519 hectares from heat detections, spread across a single municipality.

It is the 148th largest in Kgalagadi since 2016 (of 432 with a page). Number 97 in Botswana in 2023, of 381.

Compare with…
Burnt area
5,519ha
GWIS perimeter (Copernicus)
Duration
8days
3 Aug 2023 – 10 Aug 2023
Municipalities hit
1
subdistricts
Started on
3 Aug
2023
Heat detections
277
in a single hotspot: 90 MW
Danger at start
55
Extreme · FWI index
Average daily power
364MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 3 Aug10 Aug
10 Aug 2023

How it evolved, day by day

3 Aug 2023 · 0 MW · 1 4 Aug 2023 · 462 MW · 79 5 Aug 2023 · 1,808 MW · 112 6 Aug 2023 · 205 MW · 26 7 Aug 2023 · 194 MW · 25 8 Aug 2023 · 219 MW · 28 9 Aug 2023 · 12 MW · 5 10 Aug 2023 · 9 MW · 1
3 Aug 5 Aug 7 Aug 9 Aug

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

The weather it burned in

28°high
49km/h · peak gust
11%lowest humidity

It had gone more than two months without rain (1 mm or more) when it started.

This area had burned before

34% of the perimeter overlaps earlier fires recorded since 2016: 1,957 ha in 2021.

How big is it?

10 km
It burned the equivalent of 3.5% of the area of London (55 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. Tshabong where it started
    5,542 ha reached on 3 Aug
    0.2 %

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 area< 0.1 ha
Residents< 20

Inside the perimeter there was no noticeable 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)
3 Aug 23.7 °C 26 % 49 km/h 0.0 mm Extreme 55
4 Aug 24.0 °C 22 % 45 km/h 0.0 mm Extreme 51
5 Aug 24.9 °C 17 % 39 km/h 0.0 mm Very high 47
6 Aug 25.6 °C 12 % 40 km/h 0.0 mm Extreme 53
7 Aug 26.3 °C 12 % 34 km/h 0.0 mm Very high 47
8 Aug 27.3 °C 13 % 31 km/h 0.0 mm Very high 44
9 Aug 27.8 °C 11 % 40 km/h 0.0 mm Extreme 58
10 Aug 22.7 °C 21 % 49 km/h 0.0 mm Extreme 60
11 Aug after 25.5 °C 22 % 46 km/h 0.0 mm Extreme 57
12 Aug after 29.5 °C 17 % 48 km/h 0.0 mm Extreme 59
13 Aug after 30.0 °C 12 % 49 km/h 0.0 mm Extreme 67
14 Aug after 28.6 °C 8 % 33 km/h 0.0 mm Extreme 54
15 Aug after 30.4 °C 5 % 23 km/h 0.0 mm Extreme 53
16 Aug after 32.9 °C 7 % 55 km/h 0.0 mm Very extreme 85
17 Aug after 29.3 °C 14 % 54 km/h 0.0 mm Very extreme 85
18 Aug after 24.3 °C 12 % 31 km/h 0.0 mm Extreme 54
19 Aug after 28.1 °C 3 % 53 km/h 0.0 mm Very extreme 82
20 Aug after 27.4 °C 7 % 26 km/h 0.0 mm Extreme 62

Before and after, from space

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

Before · 27 Jul 2023
After · 17 Aug 2023

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 11 August 2023 the air beside the fire reached 23 µg/m³ of PM2.5, but no daily average passed the WHO guideline (15).

PM2.5 peak23 µg/m³
Days over the guideline0 days
PM1033 µg/m³
Optical depth0.36
12345678910111213
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 · 277Every 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 Botswana ›

Frequently asked questions

How long did the Tshabong fire last?
GWIS (Copernicus) dates it between 3 August 2023 and 10 August 2023: 8 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 5,519 hectares (55.2 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Tshabong (5,542 ha, 0.2 %).
What was the weather like?
During the fire the temperature reached 27.8 °C, humidity dropped to 11 % and gusts hit 49 km/h. The fire danger index (FWI) reached 60, class Extreme.
Where does this data come from?
From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Botswana (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 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.

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. 277 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 ADM2 (Public Domain). 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.