Burned area
satellite only2,092ha
Perimeter published by GWIS (Copernicus).
- Source
- GWIS (Copernicus)
- Date
- 6 Nov 2017 – 11 Nov 2017
+− cross-check
No official record is matched to this page to compare it with.
SD · Sudan · –
Talawdi fire, 6 November 2017 Talawdi
Out · last detection 12 Nov 2017, 10:42 UTC
The fire started on 6 November 2017 in Talawdi, Sudan, and satellites saw it burning for 6 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 2,092 hectares from heat detections, spread across a single municipality.
It is the 286th largest in South Kordofan since 2016 (of 314 with a page). Number 118 in Sudan in 2017, of 137.
Use this data
Compare with…
Use this data
Fire page data · version 2026-10-24matches the official recordwith caveatssatellite onlymodel
When copying, the sentence is
Tick the figures you want: they make up the lede and the CSV.
Duration by satellite
satellite only6days
6 Nov 2017 to 11 Nov 2017: first and last day with fire on the page.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- last detection: 12 Nov 2017, 10:42 UTC
+− cross-check
Satellites pass a few times a day and cloud or smoke can hide the fire: a lack of detections is not an official extinction. Each country’s emergency service declares a fire contained or out.
Start
satellite only6 Nov 2017
First day with fire seen by the satellites or the perimeter.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- 6 Nov 2017
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
The worst day
satellite only803MW
Total radiative power on 7 November 2017; hotspots that day: 37.
- Source
- NASA FIRMS · VIIRS (FRP)
- Date
- 7 Nov 2017
+− cross-check
Fire radiative power (FRP) measures the energy the fire gives off when the satellite passes. Added up by day, it compares intensity, not area.
Danger at the start
model36.7FWI · high
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 2.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 6 Nov 2017, local noon
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
This is an index computed from weather model data, not a measurement of the fire nor an official warning. Danger warnings are issued by each country’s authority. Emergency number and official warnings
Weather during the fire
model39.1°C · 15% RH
High of 39.1 °C and minimum humidity of 15% on 10 November 2017; gusts of 34 km/h on 11 November 2017.
- Source
- weather model at the fire’s grid cell
- Date
- 6 Nov 2017 – 11 Nov 2017
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
These are model values for a cell of about 25 km, not from a weather station: they may differ from what was measured on the ground.
This page’s change log has been kept since 24 October 2026: every night what it publishes is compared and the difference is logged. Anything earlier is reconstructed from each source’s date and marked as reconstructed.
Show
-
· reconstructed weatherWeather and FWI computed from the ERA5 reanalysis
-
· reconstructed GHSLPopulation and built-up area computed
What was saved on 24 October 2026
Every night a snapshot of what the page shows is saved. If anything changes, it appears in the list as a log entry.
- Area
- 2,092 ha
- Dates
- 6 Nov 2017 – 11 Nov 2017
- Name
- Talawdi
- Official record
- —
Versioned permanent link
https://worldfires.org/en/fire/talawdi-2017-11-3?v=2026-10-24A version keeps the area, dates, name and official record; the area as it was logged (changes under 2% are not logged). The map, hotspots and weather always show today’s data.
Citation
A lede of about 60 words figures only, no adjectives
CSV for this fire talawdi-2017-11-3.csv · daily, no individual hotspots
| fecha | focos_viirs | frp_mw | tmax_c | tmin_c | hr_min_pct | viento_max_kmh | racha_max_kmh | precip_mm | fwi | clase_fwi | dentro_del_incendio |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2017-11-06 | 3 | 1 | 36.1 | 22.1 | 12 | 13.5 | 25.6 | 0 | 36.7 | alto | 1 |
| 2017-11-07 | 37 | 803 | 37.6 | 21.7 | 12 | 14.9 | 27.4 | 0 | 39.7 | muy_alto | 1 |
| 2017-11-08 | 1 | 4 | 37.8 | 24 | 13 | 14.3 | 25.9 | 0 | 40.2 | muy_alto | 1 |
| 2017-11-09 | 12 | 56 | 38 | 24.7 | 17 | 15.5 | 29.9 | 0 | 42.3 | muy_alto | 1 |
| 2017-11-10 | 2 | 8 | 39.1 | 26.3 | 15 | 17.2 | 32.4 | 0 | 45.1 | muy_alto | 1 |
| 2017-11-11 | 4 | 132 | 38.1 | 25.1 | 13 | 18.3 | 33.8 | 0 | 47.2 | muy_alto | 1 |
| 2017-11-12 | 1 | 3 | 38.2 | 24.7 | 13 | 11.8 | 29.5 | 0 | 41.4 | muy_alto | 0 |
| 2017-11-13 | 0 | 0 | 37.7 | 23.7 | 22 | 11.3 | 19.1 | 0 | 39 | muy_alto | 0 |
| 2017-11-14 | 0 | 0 | 39.3 | 25.6 | 16 | 16.1 | 36.4 | 0 | 44.5 | muy_alto | 0 |
| 2017-11-15 | 0 | 0 | 39.9 | 25.5 | 16 | 13.5 | 33.5 | 0 | 42.6 | muy_alto | 0 |
| 2017-11-16 | 0 | 0 | 40 | 26 | 15 | 12.7 | 30.6 | 0 | 42.8 | muy_alto | 0 |
| 2017-11-17 | 0 | 0 | 38.7 | 25.6 | 18 | 9.4 | 21.6 | 0 | 40.2 | muy_alto | 0 |
| 2017-11-18 | 0 | 0 | 38.2 | 25.7 | 17 | 9.2 | 23.8 | 0 | 40.6 | muy_alto | 0 |
| 2017-11-19 | 0 | 0 | 39.2 | 26 | 15 | 9.2 | 19.1 | 0 | 41.2 | muy_alto | 0 |
| 2017-11-20 | 0 | 0 | 39.8 | 27.5 | 11 | 12.5 | 29.2 | 0 | 47.5 | muy_alto | 0 |
| 2017-11-21 | 0 | 0 | 38.8 | 25.1 | 11 | 19.3 | 38.2 | 0 | 56.2 | extremo | 0 |
It is generated in your browser from this page’s data: one file per fire, aggregated by day and without individual hotspots.
Live widget for your story
It updates itself while the fire is still active and links to this page. Free, with the attribution shown at the bottom.
Sources for this page: GWIS (Copernicus), NASA FIRMS (VIIRS), ERA5 (ECMWF/Copernicus C3S) · Open-Meteo.com (CC BY 4.0), GHSL (JRC). Open-Meteo.com · How we build fire pages: methodology
- Burnt area
- 2,092ha
- GWIS perimeter (Copernicus)
- Duration
- 6days
- 6 Nov 2017 – 11 Nov 2017
- Municipalities hit
- 1
- localities
- Started on
- 6 Nov
- 2017
- Heat detections
- 60
- in a single hotspot: 0 MW
- Danger at start
- 37
- High · FWI index
- Average daily power
- 144MW
- detected power per day, on average
Where it burned
HOTSPOTS BY DAY
6 Nov11 Nov
12 Nov 2017
How it evolved, day by day
7 Nov
10 Nov
12 Nov
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
34km/h · peak gust
12%lowest humidity
It had gone 2 days without rain (1 mm or more) when it started.
This area had burned before
No earlier perimeters overlap this fire since 2016, when the satellite record begins.
How big is it?
London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).
Paris boundary: geoBoundaries · Institut national de l'information géographique et forestière (IGN-F) (Etalab Open License 2.0).
Madrid boundary: geoBoundaries · Open Data ESRI, IGN Central Registry of Cartography Area (CC BY 4.0).
Berlin boundary: geoBoundaries · Federal Agency for Cartography and Geodesy (dl-de/by-2-0).
This compares size, not location: both shapes are at the same scale, north up, centred on each other.
What happened to each town
-
Talawdi where it started2,105 ha0.6 %
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 2015Built-up area< 0.1 ha
Residents< 20
Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2015, 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.
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)
Started with Very dry air: 55 % of the area in Sudan
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 6 Nov | 36.1 °C | 12 % | 26 km/h | 0.0 mm | High 37 |
| 7 Nov | 37.6 °C | 12 % | 27 km/h | 0.0 mm | Very high 40 |
| 8 Nov | 37.8 °C | 13 % | 26 km/h | 0.0 mm | Very high 40 |
| 9 Nov | 38.0 °C | 17 % | 30 km/h | 0.0 mm | Very high 42 |
| 10 Nov | 39.1 °C | 15 % | 32 km/h | 0.0 mm | Very high 45 |
| 11 Nov | 38.1 °C | 13 % | 34 km/h | 0.0 mm | Very high 47 |
| 12 Nov after | 38.2 °C | 13 % | 30 km/h | 0.0 mm | Very high 41 |
| 13 Nov after | 37.7 °C | 22 % | 19 km/h | 0.0 mm | Very high 39 |
| 14 Nov after | 39.3 °C | 16 % | 36 km/h | 0.0 mm | Very high 44 |
| 15 Nov after | 39.9 °C | 16 % | 34 km/h | 0.0 mm | Very high 43 |
| 16 Nov after | 40.0 °C | 15 % | 31 km/h | 0.0 mm | Very high 43 |
| 17 Nov after | 38.7 °C | 18 % | 22 km/h | 0.0 mm | Very high 40 |
| 18 Nov after | 38.2 °C | 17 % | 24 km/h | 0.0 mm | Very high 41 |
| 19 Nov after | 39.2 °C | 15 % | 19 km/h | 0.0 mm | Very high 41 |
| 20 Nov after | 39.8 °C | 11 % | 29 km/h | 0.0 mm | Very high 48 |
| 21 Nov after | 38.8 °C | 11 % | 38 km/h | 0.0 mm | Extreme 56 |
Its twins: fires that started in the same weather
It started with an FWI of 36.7, a minimum humidity of 12% and 2 days without rain. Fires in the area that started in weather like this since 2016: 20.
FWI at the start
36.7
Minimum humidity
12 %
Days without rain
2
this fire
chosen twins
rest of the area
Almost identicalSimilar
Outlines of the closest twins
This fire · Talawdi fire, 6 November 2017
2,092 ha
6 days
FWI 36.7
Min. humidity 12 %
Ghadeer fire, November 2023
3,749 ha
8 days
FWI 36.0
Min. humidity 13 %
144 km away, in 2023
First rain (1 mm or more) after it ended: none in the following ten days.
Fashoda fire, November 2021
36,698 ha
21 days
FWI 39.1
Min. humidity 13 %
183 km away, in 2021
First rain (1 mm or more) after it ended: none in the following ten days.
Al Leri fire, November 2023
2,675 ha
3 days
FWI 40.4
Min. humidity 13 %
90 km away, in 2023
First rain (1 mm or more) after it ended: none in the following ten days.
Ghadeer fire, November 2016
17,636 ha
16 days
FWI 38.2
Min. humidity 15 %
149 km away, in 2016
First rain (1 mm or more) after it ended: none in the following ten days.
Talawdi fire, November 2016
3,994 ha
7 days
FWI 42.1
Min. humidity 14 %
21 km away, in 2016
First rain (1 mm or more) after it ended: none in the following ten days.
What happened to them
- 8 days
- median duration
- 3,866 ha
- median area
- 20 %
- went past 10,000 ha
- —
- rain at the end (median; 0 of 20 had it)
It stayed below its twins: 2,092 ha against a median of 3,866 ha. It lasted 6 days, against 8 days.
In none of them did 1 mm fall in the ten days after the end: they all went out without rain.
This is a bank of analogues: it shows what usually happens, not what will happen. With fewer than 15 twins we give no figures. How we calculate it
How it ended
—first rain
—no rain in ten days
34km/h · max. gust
It was considered over on 11 Nov, and not even 1 mm fell in the following ten days: it went out without rain. None of its 20 twins had rain when they ended.
Weather on this page: Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)
How a twin is chosen
- Same area: fires that have already ended, less than 250 km from this one, since 2016.
- Same start: we compare the FWI on the first day, the minimum humidity that day and the run of days without rain before it. The slider sets how much they may differ.
- Only pages with final weather data (ERA5 reanalysis) calculated in the same way as this fire’s; agricultural and grass burns and pages with data under review are left out.
- Fires burning at the same time as this one (a week before or after) are left out: they share the same spell of weather and do not count as a precedent.
- They are sorted by similarity, and the outlines of the first five are drawn.
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
↔
Before · 30 Oct 2017
After · 18 Nov 2017
Sentinel-2 did not pass over on that day. Try another date, or use false colour, which is daily.
If the day is cloudy, change the date: each satellite passes once a day. In false colour the burnt ground looks brown or red.
Detections table · 0Every 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 time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
Frequently asked questions
- How long did the Talawdi fire last?
- GWIS (Copernicus) dates it between 6 November 2017 and 11 November 2017: 6 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,092 hectares (20.9 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Talawdi (2,105 ha, 0.6 %).
- What was the weather like?
- During the fire the temperature reached 39.1 °C, humidity dropped to 12 % and gusts hit 34 km/h. The fire danger index (FWI) reached 47, class Very high.
- 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.
- How did the fires that started in similar weather in this area end?
- Fires less than 250 km away that started since 2016 with a similar FWI, humidity and dry spell: 20. Their median duration was 8 days and their median area 3,866 ha; 20 % went past 10,000 ha. In none of them did 1 mm fall in the ten days after the end: they all went out without rain.
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 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
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. No 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 2015, 100 m cells), summed inside the perimeter: an estimate of what was there, not a damage count.
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.