Skip to content
worldfires
SZ · Eswatini ·

Mhlambanyatsi fire, October 2026 Mhlambanyatsi

Out · last detection 29 Oct 2026, 12:55 UTC

The fire started on 29 October 2026 in Mhlambanyatsi, Eswatini, and satellites saw it burning for 1 day. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,005 hectares from heat detections, spread across a single municipality.

Number 9 in Eswatini in 2026, of 9.

GWIS near-real-time perimeter, from the layer that changed in August 2025: this fire is not compared with fires from earlier years, because since then the GWIS layer gives more and larger perimeters.

Burnt area
1,005ha
GWIS perimeter (Copernicus)
Duration
1day
29 Oct 2026 – 29 Oct 2026
Municipalities hit
1
tinkhundla
Started on
29 Oct
2026
Heat detections
32
in a single hotspot: 247 MW
Danger at start
4
Very low · FWI index
Average daily power
2.0GW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 29 Oct29 Oct

How it evolved, day by day

29 Oct 2026 · 2,031 MW · 32

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

The weather it burned in

20°high
34km/h · peak gust
50%lowest humidity

It had gone one day without rain (1 mm or more) when it started. Rain came after the fire: 3.5 mm on 1 Nov.

This area had burned before

0% of the perimeter overlaps earlier fires recorded since 2016: 3 ha in 2023.

How big is it?

10 km
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

  1. Mhlambanyatsi where it started
    1,009 ha reached on 29 Oct
    2.1 %

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 area1.7 ha
Residents≈ 80

Inside the perimeter there were about 1.7 hectares of built-up land and about 80 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)
29 Oct 20.0 °C 50 % 34 km/h 0.1 mm Very low 4
30 Oct after 22.3 °C 51 % 39 km/h 0.0 mm Low 7
31 Oct after 25.5 °C 51 % 36 km/h 0.0 mm Moderate 11
1 Nov after 28.0 °C 37 % 40 km/h 3.5 mm Moderate 12

Before and after, from space

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

Before · 22 Oct 2026
After · 5 Nov 2026

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

PM2.5 peak18 µg/m³
Days over the guideline0 days
PM1019 µg/m³
Optical depth0.32
272829
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 · 32Every 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 Eswatini

Frequently asked questions

How long did the Mhlambanyatsi fire last?
GWIS (Copernicus) dates it between 29 October 2026 and 29 October 2026: 1 day 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,005 hectares (10.0 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Mhlambanyatsi (1,009 ha, 2.1 %).
Is the Mhlambanyatsi fire still active?
No fire detections since 29 Oct 2026, 12:55 UTC. A lack of detections is not an official extinction.
What was the weather like?
During the fire the temperature reached 20.0 °C, humidity dropped to 50 % and gusts hit 34 km/h. The fire danger index (FWI) reached 4, class Very low.
Where does this data come from?
From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Eswatini (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 · 1 Changes in area, dates, name, official record or merged pages, compared every night since 30 October 2026.
  1. Page published (1,005 ha).

RSS Changes to this page With cross-checks and a citable version

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. 32 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 (Open Data Commons Open Database License 1.0). 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.