Skip to content
worldfires
SD · Sudan · →

Ad Dinder fire, February 2026 Ad Dinder

Out · last detection 5 Feb 2026, 11:07 UTC

The fire started on 2 February 2026 in Ad Dinder, Sudan, and satellites saw it burning for 4 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 3,374 hectares from heat detections, spread across a single municipality.

It is the 39th largest in Sennar since 2016 (of 130 with a page). Number 85 in Sudan in 2026, of 235.

Compare with…
Burnt area
3,374ha
GWIS perimeter (Copernicus)
Duration
4days
2 Feb 2026 – 5 Feb 2026
Municipalities hit
1
localities
Started on
2 Feb
2026
Heat detections
91
in a single hotspot: 31 MW
Danger at start
56
Extreme · FWI index
Average daily power
234MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 2 Feb5 Feb
5 Feb 2026

How it evolved, day by day

2 Feb 2026 · 28 MW · 5 3 Feb 2026 · 844 MW · 62 4 Feb 2026 · 61 MW · 12 5 Feb 2026 · 5 MW · 1
2 Feb 3 Feb 4 Feb 5 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
34km/h · peak gust
10%lowest humidity

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

This area had burned before

95% of the perimeter overlaps earlier fires recorded since 2016: 369 ha in 2016, 147 ha in 2017, 2,143 ha in 2019, 1,989 ha in 2020, 1,127 ha in 2021, 424 ha in 2022, 1,317 ha in 2023, 829 ha in 2024. Part of it burned more than once, so the yearly figures add up to more than the 3,222 ha that had burned before.

How big is it?

10 km
It burned the equivalent of 2.1% of the area of London (34 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. Ad Dinder where it started
    2,992 ha reached on 31 Jan
    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)
2 Feb 38.5 °C 10 % 23 km/h 0.0 mm Extreme 56
3 Feb 40.1 °C 13 % 34 km/h 0.0 mm Extreme 60
4 Feb 39.2 °C 13 % 32 km/h 0.0 mm Extreme 59
5 Feb 38.0 °C 13 % 31 km/h 0.0 mm Extreme 57
6 Feb after 39.6 °C 12 % 31 km/h 0.0 mm Extreme 57
7 Feb after 38.5 °C 10 % 32 km/h 0.0 mm Extreme 59
8 Feb after 40.1 °C 6 % 30 km/h 0.0 mm Extreme 61
9 Feb after 41.4 °C 9 % 23 km/h 0.0 mm Extreme 59
10 Feb after 40.7 °C 10 % 22 km/h 0.0 mm Extreme 55
11 Feb after 39.8 °C 9 % 24 km/h 0.0 mm Extreme 55
12 Feb after 40.3 °C 9 % 25 km/h 0.0 mm Extreme 60
13 Feb after 42.2 °C 9 % 31 km/h 0.0 mm Extreme 66
14 Feb after 40.6 °C 10 % 33 km/h 0.0 mm Extreme 65
15 Feb after 42.2 °C 10 % 26 km/h 0.0 mm Extreme 60

Before and after, from space

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

Before · 26 Jan 2026
After · 12 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 5 February 2026 the air beside the fire reached 20 µg/m³ of PM2.5, but no daily average passed the WHO guideline (15).

PM2.5 peak20 µg/m³
Days over the guideline0 days
PM1053 µg/m³
Optical depth0.31
3112345678
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 · 91Every 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 Ad Dinder fire last?
GWIS (Copernicus) dates it between 2 February 2026 and 5 February 2026: 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 3,374 hectares (33.7 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Ad Dinder (2,992 ha, 0.2 %).
What was the weather like?
During the fire the temperature reached 40.1 °C, humidity dropped to 10 % and gusts hit 34 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 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. 91 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.