Ezo fire, 4 January 2026 Ezo, Nzara, Tambura
The fire started on 4 January 2026 in Ezo, South Sudan, and satellites saw it burning for 14 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 15,313 hectares from heat detections, spread across 3 municipalities.
It is the 76th largest in Western Equatoria since 2016 (of 361 with a page). Number 23 in South Sudan in 2026, of 183.
Compare with…
Suggestions: Ezo · 2017Nzara · 2020Ezo · 2020Ezo · 2016
- Burnt area
- 15,313ha
- GWIS perimeter (Copernicus)
- Duration
- 14days
- 4 Jan 2026 – 17 Jan 2026
- Municipalities hit
- 3
- counties
- Started on
- 4 Jan
- 2026
- Heat detections
- 374
- in a single hotspot: 163 MW
- Danger at start
- 42
- Very high · FWI index
- Average daily power
- 310MW
- detected power per day, on average
Where it burned
How it evolved, day by day
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
It had gone 59 days without rain (1 mm or more) when it started.
This area had burned before
84% of the perimeter overlaps earlier fires recorded since 2016: 5,508 ha in 2016, 3,917 ha in 2017, 446 ha in 2018, 486 ha in 2019, 5,581 ha in 2020, 1,381 ha in 2021, 1,699 ha in 2022, 993 ha in 2023, 1,056 ha in 2024, 8,513 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 12,848 ha that had burned before.
- 2,274 ha Ezo fire, December 2017 5,455 ha in total; the hectares shown are those it shares with this fire
- 925 ha Nzara fire, December 2020 7,288 ha in total; the hectares shown are those it shares with this fire
- 886 ha Ezo fire, January 2020 7,344 ha in total; the hectares shown are those it shares with this fire
- 629 ha Ezo fire, December 2016 5,052 ha in total; the hectares shown are those it shares with this fire
- 6 ha Nzara fire, December 2017 17,262 ha in total; the hectares shown are those it shares with this fire
- 1 ha Nzara fire, December 2025 120,517 ha in total; the hectares shown are those it shares with this fire
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
-
Ezo where it started10,758 ha reached on 4 Jan1.3 %
-
2,516 ha reached on 4 Jan0.4 %
-
2,137 ha reached on 4 Jan0.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) |
|---|---|---|---|---|---|
| 4 Jan | 36.3 °C | 16 % | 30 km/h | 0.0 mm | Very high 42 |
| 5 Jan | 35.4 °C | 18 % | 22 km/h | 0.0 mm | Very high 42 |
| 6 Jan | 35.7 °C | 19 % | 26 km/h | 0.0 mm | Very high 43 |
| 7 Jan | 36.0 °C | 20 % | 29 km/h | 0.0 mm | Very high 44 |
| 8 Jan | 36.8 °C | 18 % | 32 km/h | 0.0 mm | Very high 45 |
| 9 Jan | 35.8 °C | 20 % | 31 km/h | 0.0 mm | Very high 44 |
| 10 Jan | 34.9 °C | 19 % | 31 km/h | 0.0 mm | Very high 46 |
| 11 Jan | 35.4 °C | 21 % | 26 km/h | 0.0 mm | Very high 44 |
| 12 Jan | 35.9 °C | 20 % | 30 km/h | 0.0 mm | Very high 46 |
| 13 Jan | 35.8 °C | 19 % | 35 km/h | 0.0 mm | Very high 49 |
| 14 Jan | 35.1 °C | 20 % | 41 km/h | 0.0 mm | Extreme 51 |
| 15 Jan | 35.1 °C | 21 % | 39 km/h | 0.0 mm | Extreme 50 |
| 16 Jan | 34.6 °C | 18 % | 35 km/h | 0.0 mm | Very high 48 |
| 17 Jan | 35.6 °C | 16 % | 27 km/h | 0.0 mm | Very high 45 |
| 18 Jan after | 36.1 °C | 17 % | 34 km/h | 0.0 mm | Very high 48 |
| 19 Jan after | 36.1 °C | 17 % | 36 km/h | 0.0 mm | Very high 49 |
| 20 Jan after | 36.8 °C | 19 % | 30 km/h | 0.0 mm | Very high 46 |
| 21 Jan after | 36.1 °C | 20 % | 35 km/h | 0.0 mm | Very high 50 |
| 22 Jan after | 37.2 °C | 20 % | 34 km/h | 0.0 mm | Very high 47 |
| 23 Jan after | 36.7 °C | 20 % | 24 km/h | 0.0 mm | Very high 45 |
| 24 Jan after | 36.7 °C | 22 % | 29 km/h | 0.0 mm | Very high 46 |
| 25 Jan after | 38.2 °C | 13 % | 37 km/h | 0.0 mm | Extreme 52 |
| 26 Jan after | 37.6 °C | 14 % | 34 km/h | 0.0 mm | Extreme 50 |
| 27 Jan after | 37.3 °C | 15 % | 32 km/h | 0.0 mm | Extreme 51 |
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
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 · CopernicusOn 5 January 2026 the air beside the fire reached 134 µg/m³ of PM2.5. That day averaged 84: 5.6 times the WHO daily guideline (15).
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 · 374Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 22,203 haEzo30 December 2025 · 10 days · 21 km away
- 17,262 haNzara10 December 2017 · 11 days · 27 km away
- 12,897 haNzara8 January 2026 · 14 days · 31 km away
- 21,663 haEzo10 December 2025 · 16 days · 34 km away
- 15,095 haEzo8 December 2016 · 9 days · 38 km away
- 14,605 haNzara15 December 2017 · 10 days · 40 km away
Frequently asked questions
- How long did the Ezo fire last?
- GWIS (Copernicus) dates it between 4 January 2026 and 17 January 2026: 14 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 15,313 hectares (153.1 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 3 municipalities: Ezo (10,758 ha, 1.3 %); Nzara (2,516 ha, 0.4 %); Tambura (2,137 ha, 0.2 %).
- What was the weather like?
- During the fire the temperature reached 36.8 °C, humidity dropped to 16 % and gusts hit 41 km/h. The fire danger index (FWI) reached 51, class Extreme.
- 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
How we know this
- Perimeter: GWIS (Copernicus), rebuilt from heat detections rather than mapped on imagery; 2 polygons grouped in this page.
- Dates from the perimeter: the VIIRS detections inside it did not change them. 374 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.
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.