Uror fire, 24 January 2026 Uror
The fire started on 24 January 2026 in Uror, South Sudan, and satellites saw it burning for 8 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 5,032 hectares from heat detections, spread across a single municipality.
It is the 422th largest in Jonglei since 2016 (of 427 with a page). Number 181 in South Sudan in 2026, of 183.
Compare with…
Suggestions: Uror · 2023Uror · 2021Uror · 2020Uror · 2021
- Burnt area
- 5,032ha
- GWIS perimeter (Copernicus)
- Duration
- 8days
- 24 Jan 2026 – 31 Jan 2026
- Municipalities hit
- 1
- counties
- Started on
- 24 Jan
- 2026
- Heat detections
- 93
- in a single hotspot: 147 MW
- Danger at start
- 47
- Very high · FWI index
- Average daily power
- 185MW
- 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 more than two months without rain (1 mm or more) when it started.
This area had burned before
78% of the perimeter overlaps earlier fires recorded since 2016: 1,475 ha in 2016, 501 ha in 2017, 911 ha in 2018, 533 ha in 2020, 2,085 ha in 2021, 2,637 ha in 2023, 142 ha in 2024, 351 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 3,926 ha that had burned before.
- 2,099 ha Uror fire, January 2023 5,093 ha in total; the hectares shown are those it shares with this fire
- 1,707 ha Uror fire, December 2021 5,399 ha in total; the hectares shown are those it shares with this fire
- 487 ha Uror fire, February 2020 11,727 ha in total; the hectares shown are those it shares with this fire
- 79 ha Uror fire, January 2021 29,488 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
-
Uror where it started5,061 ha reached on 24 Jan0.4 %
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) |
|---|---|---|---|---|---|
| 24 Jan | 39.0 °C | 18 % | 34 km/h | 0.0 mm | Very high 47 |
| 25 Jan | 39.4 °C | 12 % | 35 km/h | 0.0 mm | Extreme 56 |
| 26 Jan | 39.5 °C | 14 % | 40 km/h | 0.0 mm | Extreme 57 |
| 27 Jan | 38.9 °C | 13 % | 39 km/h | 0.0 mm | Extreme 58 |
| 28 Jan | 36.7 °C | 15 % | 34 km/h | 0.0 mm | Extreme 54 |
| 29 Jan | 37.3 °C | 18 % | 37 km/h | 0.0 mm | Extreme 57 |
| 30 Jan | 37.9 °C | 20 % | 37 km/h | 0.0 mm | Extreme 56 |
| 31 Jan | 37.5 °C | 17 % | 37 km/h | 0.0 mm | Extreme 56 |
| 1 Feb after | 31.9 °C | 27 % | 23 km/h | 0.0 mm | Very high 42 |
| 2 Feb after | 36.8 °C | 24 % | 23 km/h | 0.0 mm | High 37 |
| 3 Feb after | 38.8 °C | 14 % | 37 km/h | 0.0 mm | Extreme 54 |
| 4 Feb after | 39.4 °C | 15 % | 35 km/h | 0.0 mm | Extreme 53 |
| 5 Feb after | 33.2 °C | 20 % | 29 km/h | 0.0 mm | Very high 50 |
| 6 Feb after | 36.9 °C | 22 % | 23 km/h | 0.0 mm | Very high 44 |
| 7 Feb after | 37.5 °C | 15 % | 31 km/h | 0.0 mm | Very high 49 |
| 8 Feb after | 38.0 °C | 13 % | 30 km/h | 0.0 mm | Very high 48 |
| 9 Feb after | 36.9 °C | 18 % | 21 km/h | 0.0 mm | Very high 46 |
| 10 Feb after | 33.2 °C | 30 % | 36 km/h | 0.6 mm | Very high 45 |
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 February 2026 the air beside the fire reached 104 µg/m³ of PM2.5. That day averaged 55: 3.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 · 93Every 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 Uror fire last?
- GWIS (Copernicus) dates it between 24 January 2026 and 31 January 2026: 8 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 5,032 hectares (50.3 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Uror (5,061 ha, 0.4 %).
- What was the weather like?
- During the fire the temperature reached 39.5 °C, humidity dropped to 12 % and gusts hit 40 km/h. The fire danger index (FWI) reached 58, 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.
- Dates from the perimeter: the VIIRS detections inside it did not change them. 93 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.