Yambio fire, 1 January 2026 Yambio, Ibba
The fire started on 1 January 2026 in Yambio, South Sudan, and satellites saw it burning for 23 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 26,367 hectares from heat detections, spread across 2 municipalities.
It is the 38th largest in Western Equatoria since 2016 (of 359 with a page). Number 10 in South Sudan in 2026, of 190.
Compare with…
Suggestions: Yambio · 2020Ibba · 2025Yambio · 2016Ibba · 2016
- Burnt area
- 26,367ha
- GWIS perimeter (Copernicus)
- Duration
- 23days
- 1 Jan 2026 – 23 Jan 2026
- Municipalities hit
- 2
- counties
- Started on
- 1 Jan
- 2026
- Heat detections
- 779
- in a single hotspot: 0 MW
- Danger at start
- 38
- High · FWI index
- Average daily power
- 327MW
- 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 16 days without rain (1 mm or more) when it started.
This area had burned before
77% of the perimeter overlaps earlier fires recorded since 2016: 10,823 ha in 2016, 7,253 ha in 2017, 3,668 ha in 2018, 3,947 ha in 2019, 10,503 ha in 2020, 3,582 ha in 2021, 4,854 ha in 2022, 1,335 ha in 2023, 2,425 ha in 2024, 2,760 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 20,303 ha that had burned before.
- 6,855 ha Yambio fire, January 2020 18,919 ha in total; the hectares shown are those it shares with this fire
- 2,538 ha Ibba fire, January 2025 10,986 ha in total; the hectares shown are those it shares with this fire
- 127 ha Yambio fire, December 2016 5,821 ha in total; the hectares shown are those it shares with this fire
- 59 ha Ibba fire, December 2016 6,671 ha in total; the hectares shown are those it shares with this fire
- 46 ha Yambio fire, January 2018 7,014 ha in total; the hectares shown are those it shares with this fire
- 29 ha Ibba fire, December 2016 5,471 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
-
Yambio where it started25,000 ha2.8 %
-
1,536 ha0.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 2025Inside 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) |
|---|---|---|---|---|---|
| 1 Jan | 34.4 °C | 20 % | 22 km/h | 0.0 mm | High 38 |
| 2 Jan | 34.7 °C | 30 % | 30 km/h | 0.0 mm | Very high 40 |
| 3 Jan | 35.1 °C | 25 % | 36 km/h | 0.0 mm | Very high 41 |
| 4 Jan | 35.7 °C | 18 % | 28 km/h | 0.0 mm | Very high 43 |
| 5 Jan | 34.8 °C | 20 % | 21 km/h | 0.0 mm | Very high 42 |
| 6 Jan | 35.6 °C | 20 % | 27 km/h | 0.0 mm | Very high 44 |
| 7 Jan | 36.3 °C | 19 % | 32 km/h | 0.0 mm | Very high 44 |
| 8 Jan | 36.7 °C | 18 % | 32 km/h | 0.0 mm | Very high 44 |
| 9 Jan | 35.6 °C | 20 % | 28 km/h | 0.0 mm | Very high 43 |
| 10 Jan | 34.1 °C | 23 % | 26 km/h | 0.0 mm | Very high 44 |
| 11 Jan | 34.6 °C | 22 % | 31 km/h | 0.0 mm | Very high 44 |
| 12 Jan | 35.4 °C | 22 % | 26 km/h | 0.0 mm | Very high 46 |
| 13 Jan | 35.5 °C | 20 % | 37 km/h | 0.0 mm | Very high 48 |
| 14 Jan | 35.0 °C | 22 % | 46 km/h | 0.0 mm | Extreme 53 |
| 15 Jan | 34.9 °C | 22 % | 41 km/h | 0.0 mm | Extreme 50 |
| 16 Jan | 34.2 °C | 19 % | 37 km/h | 0.0 mm | Very high 48 |
| 17 Jan | 35.2 °C | 18 % | 24 km/h | 0.0 mm | Very high 45 |
| 18 Jan | 35.9 °C | 17 % | 31 km/h | 0.0 mm | Very high 47 |
| 19 Jan | 35.6 °C | 19 % | 37 km/h | 0.0 mm | Very high 49 |
| 20 Jan | 36.3 °C | 21 % | 34 km/h | 0.0 mm | Very high 48 |
| 21 Jan | 34.6 °C | 23 % | 37 km/h | 0.0 mm | Very high 49 |
| 22 Jan | 36.7 °C | 20 % | 31 km/h | 0.0 mm | Very high 46 |
| 23 Jan | 35.9 °C | 22 % | 24 km/h | 0.0 mm | Very high 43 |
| 24 Jan after | 36.9 °C | 20 % | 27 km/h | 0.0 mm | Very high 45 |
| 25 Jan after | 37.9 °C | 14 % | 35 km/h | 0.0 mm | Very high 50 |
| 26 Jan after | 36.8 °C | 15 % | 33 km/h | 0.0 mm | Very high 49 |
| 27 Jan after | 36.5 °C | 16 % | 30 km/h | 0.0 mm | Very high 49 |
| 28 Jan after | 34.1 °C | 21 % | 27 km/h | 0.0 mm | Very high 44 |
| 29 Jan after | 35.9 °C | 18 % | 31 km/h | 0.0 mm | Very high 47 |
| 30 Jan after | 36.6 °C | 18 % | 33 km/h | 0.0 mm | Very high 49 |
| 31 Jan after | 36.3 °C | 17 % | 21 km/h | 0.0 mm | Very high 47 |
| 1 Feb after | 32.4 °C | 32 % | 34 km/h | 0.0 mm | Very high 41 |
| 2 Feb after | 34.7 °C | 24 % | 26 km/h | 0.0 mm | High 35 |
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 2 January 2026 the air beside the fire reached 159 µg/m³ of PM2.5. That day averaged 81: 5.4 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 · 0Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
Frequently asked questions
- How long did the Yambio fire last?
- GWIS (Copernicus) dates it between 1 January 2026 and 23 January 2026: 23 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 26,367 hectares (263.7 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Yambio (25,000 ha, 2.8 %); Ibba (1,536 ha, 0.2 %).
- What was the weather like?
- During the fire the temperature reached 36.7 °C, humidity dropped to 17 % and gusts hit 46 km/h. The fire danger index (FWI) reached 53, 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
History of this page · 4 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
- Last day with fire: 30 January 2026 → 23 January 2026.
- Start date: 26 December 2025 → 1 January 2026.
- Last day with fire: 23 January 2026 → 30 January 2026.
- Start date: 1 January 2026 → 26 December 2025.
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; 3 polygons grouped in this page.
- 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 2025, 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.