Skip to content
worldfires
SS · South Sudan · →

Awerial fire, January 2026 Awerial

Out · last detection 15 Feb 2026, 11:18 UTC

The fire started on 31 January 2026 in Awerial, South Sudan, and satellites saw it burning for 15 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 5,377 hectares from heat detections, spread across a single municipality.

It is the 141th largest in Lakes since 2016 (of 158 with a page). Number 154 in South Sudan in 2026, of 183.

Compare with…
Burnt area
5,377ha
GWIS perimeter (Copernicus)
Duration
15days
31 Jan 2026 – 14 Feb 2026
Municipalities hit
1
counties
Started on
31 Jan
2026
Heat detections
173
in a single hotspot: 169 MW
Danger at start
45
Very high · FWI index
Average daily power
118MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 31 Jan14 Feb
15 Feb 2026

How it evolved, day by day

31 Jan 2026 · 54 MW · 4 3 Feb 2026 · 821 MW · 60 4 Feb 2026 · 135 MW · 18 5 Feb 2026 · 13 MW · 5 6 Feb 2026 · 66 MW · 10 8 Feb 2026 · 52 MW · 9 9 Feb 2026 · 5 MW · 1 11 Feb 2026 · 71 MW · 7 12 Feb 2026 · 38 MW · 6 13 Feb 2026 · 90 MW · 21 14 Feb 2026 · 9 MW · 1 15 Feb 2026 · 68 MW · 7
31 Jan 3 Feb 4 Feb 6 Feb 9 Feb 12 Feb 14 Feb

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
36km/h · peak gust
14%lowest humidity

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

This area had burned before

49% of the perimeter overlaps earlier fires recorded since 2016: 433 ha in 2018, 1,285 ha in 2021, 732 ha in 2023, 658 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 2,636 ha that had burned before.

How big is it?

10 km
It burned the equivalent of 3.4% of the area of London (54 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. Awerial where it started
    5,412 ha reached on 24 Jan
    1.2 %

Burnt area inside each municipality, from crossing the GWIS perimeter with administrative boundaries. The distance is from the town centre to the nearest fire: staying a kilometre away does not mean it reached the houses.

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)
31 Jan 37.4 °C 18 % 30 km/h 0.0 mm Very high 45
1 Feb 33.4 °C 27 % 25 km/h 0.0 mm Very high 40
2 Feb 36.8 °C 26 % 26 km/h 0.0 mm High 38
3 Feb 38.7 °C 20 % 36 km/h 0.0 mm Very high 45
4 Feb 39.1 °C 14 % 35 km/h 0.0 mm Very high 50
5 Feb 36.8 °C 25 % 36 km/h 0.0 mm Very high 46
6 Feb 37.0 °C 25 % 27 km/h 0.0 mm Very high 44
7 Feb 35.5 °C 20 % 19 km/h 0.0 mm Very high 42
8 Feb 37.0 °C 22 % 21 km/h 0.0 mm Very high 41
9 Feb 36.4 °C 22 % 22 km/h 0.0 mm Very high 43
10 Feb 33.1 °C 33 % 30 km/h 0.3 mm Very high 41
11 Feb 37.8 °C 25 % 26 km/h 0.0 mm High 35
12 Feb 36.1 °C 24 % 22 km/h 0.0 mm High 36
13 Feb 37.7 °C 17 % 28 km/h 0.0 mm Very high 44
14 Feb 37.5 °C 16 % 29 km/h 0.0 mm Very high 42
15 Feb after 37.3 °C 28 % 27 km/h 0.0 mm Very high 42
16 Feb after 36.7 °C 29 % 32 km/h 0.2 mm Very high 43
17 Feb after 38.4 °C 25 % 26 km/h 0.0 mm Very high 41
18 Feb after 36.9 °C 31 % 24 km/h 0.1 mm Very high 41
19 Feb after 34.5 °C 33 % 28 km/h 0.1 mm Very high 38
20 Feb after 36.7 °C 25 % 22 km/h 0.0 mm High 35
21 Feb after 36.6 °C 17 % 30 km/h 0.0 mm Very high 44
22 Feb after 36.5 °C 12 % 34 km/h 0.0 mm Extreme 52
23 Feb after 35.1 °C 13 % 25 km/h 0.0 mm Very high 47
24 Feb after 35.2 °C 12 % 34 km/h 0.0 mm Extreme 53

Before and after, from space

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

Before · 24 Jan 2026
After · 21 Feb 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 1 February 2026 the air beside the fire reached 44 µg/m³ of PM2.5. That day averaged 30: 2.0 times the WHO daily guideline (15).

PM2.5 peak44 µg/m³
Days over the guideline19 days
PM1049 µg/m³
Optical depth0.79
2930311234567891011121314151617
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 · 173Every 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 Sudan ›

Frequently asked questions

How long did the Awerial fire last?
GWIS (Copernicus) dates it between 31 January 2026 and 14 February 2026: 15 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,377 hectares (53.8 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Awerial (5,412 ha, 1.2 %).
What was the weather like?
During the fire the temperature reached 39.1 °C, humidity dropped to 14 % and gusts hit 36 km/h. The fire danger index (FWI) reached 50, class Very high.
Where does this data come from?
From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of South Sudan (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

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

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.