Skip to content
worldfires
SD · Sudan · →

Keilak fire, January 2025 Keilak

Out · last detection 4 Feb 2025, 10:24 UTC

The fire started on 31 January 2025 in Keilak, Sudan, and satellites saw it burning for 4 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 2,463 hectares from heat detections, spread across a single municipality.

It is the 112th largest in West Kordofan since 2016 (of 177 with a page). Number 261 in Sudan in 2025, of 390.

Compare with…
Burnt area
2,463ha
GWIS perimeter (Copernicus)
Duration
4days
31 Jan 2025 – 3 Feb 2025
Municipalities hit
1
localities
Started on
31 Jan
2025
Heat detections
123
in a single hotspot: 51 MW
Danger at start
65
Extreme · FWI index
Average daily power
154MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 31 Jan3 Feb
4 Feb 2025

How it evolved, day by day

31 Jan 2025 · 376 MW · 21 1 Feb 2025 · 200 MW · 54 2 Feb 2025 · 132 MW · 19 3 Feb 2025 · 59 MW · 11 4 Feb 2025 · 3 MW · 1
31 Jan 1 Feb 2 Feb 3 Feb 4 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

40°high
39km/h · peak gust
9%lowest humidity

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

This area had burned before

73% of the perimeter overlaps earlier fires recorded since 2016: 974 ha in 2016, 605 ha in 2017, 127 ha in 2020, 462 ha in 2021, 178 ha in 2022, 405 ha in 2023. Part of it burned more than once, so the yearly figures add up to more than the 1,791 ha that had burned before.

How big is it?

10 km
It burned the equivalent of 1.6% of the area of London (25 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. Keilak where it started
    2,477 ha reached on 30 Jan
    0.3 %

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)
31 Jan 36.0 °C 11 % 39 km/h 0.0 mm Extreme 65
1 Feb 37.3 °C 9 % 34 km/h 0.0 mm Extreme 64
2 Feb 38.5 °C 10 % 32 km/h 0.0 mm Extreme 63
3 Feb 39.5 °C 11 % 32 km/h 0.0 mm Extreme 64
4 Feb after 40.2 °C 11 % 31 km/h 0.0 mm Extreme 64
5 Feb after 40.1 °C 11 % 34 km/h 0.0 mm Extreme 66
6 Feb after 39.3 °C 10 % 36 km/h 0.0 mm Extreme 68
7 Feb after 38.2 °C 11 % 39 km/h 0.0 mm Extreme 69
8 Feb after 39.1 °C 11 % 38 km/h 0.0 mm Extreme 68
9 Feb after 38.5 °C 11 % 34 km/h 0.0 mm Extreme 67
10 Feb after 38.9 °C 8 % 35 km/h 0.0 mm Extreme 63
11 Feb after 39.7 °C 8 % 35 km/h 0.0 mm Extreme 68
12 Feb after 38.5 °C 12 % 35 km/h 0.0 mm Extreme 65
13 Feb after 38.6 °C 14 % 37 km/h 0.0 mm Extreme 65

Before and after, from space

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

Before · 24 Jan 2025
After · 10 Feb 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 6 February 2025 the air beside the fire reached 75 µg/m³ of PM2.5. That day averaged 56: 3.7 times the WHO daily guideline (15).

PM2.5 peak75 µg/m³
Days over the guideline9 days
PM10318 µg/m³
Optical depth0.37
293031123456
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 · 123Every 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 Sudan ›

Frequently asked questions

How long did the Keilak fire last?
GWIS (Copernicus) dates it between 31 January 2025 and 3 February 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 2,463 hectares (24.6 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Keilak (2,477 ha, 0.3 %).
What was the weather like?
During the fire the temperature reached 39.5 °C, humidity dropped to 9 % and gusts hit 39 km/h. The fire danger index (FWI) reached 65, class Extreme.
Where does this data come from?
From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of 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

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