Dima fire, 3 February 2026 Dima, Gog
The fire started on 3 February 2026 in Dima, Ethiopia, and satellites saw it burning for 4 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 2,123 hectares from heat detections, spread across 2 municipalities.
It is the 555th largest in Gambela since 2016 (of 611 with a page). Number 164 in Ethiopia in 2026, of 190.
Compare with…
Suggestions: Dima · 2024Dima · 2018Dima · 2017Dima · 2017
- Burnt area
- 2,123ha
- GWIS perimeter (Copernicus)
- Duration
- 4days
- 3 Feb 2026 – 6 Feb 2026
- Municipalities hit
- 2
- districts
- Started on
- 3 Feb
- 2026
- Heat detections
- 53
- in a single hotspot: 120 MW
- Average daily power
- 432MW
- 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.
This area had burned before
88% of the perimeter overlaps earlier fires recorded since 2016: 598 ha in 2016, 308 ha in 2017, 616 ha in 2018, 310 ha in 2020, 17 ha in 2021, 9 ha in 2022, 1,601 ha in 2023, 1,437 ha in 2024. Part of it burned more than once, so the yearly figures add up to more than the 1,872 ha that had burned before.
- 1,421 ha Dima fire, February 2024 3,586 ha in total; the hectares shown are those it shares with this fire
- 616 ha Dima fire, January 2018 2,576 ha in total; the hectares shown are those it shares with this fire
- 123 ha Dima fire, January 2017 2,727 ha in total; the hectares shown are those it shares with this fire
- 27 ha Dima fire, December 2017 5,996 ha in total; the hectares shown are those it shares with this fire
- 17 ha Dima fire, January 2021 2,737 ha in total; the hectares shown are those it shares with this fire
- 9 ha Dima fire, March 2022 2,780 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
-
Dima where it started1,440 ha reached on 3 Feb0.2 %
-
698 ha reached on 3 Feb0.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
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 February 2026 the air beside the fire reached 70 µg/m³ of PM2.5. That day averaged 41: 2.8 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 · 53Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 20,169 haDima8 January 2019 · 15 days · 14 km away
- 26,386 haDima3 January 2019 · 7 days · 19 km away
- 17,819 haDima11 January 2018 · 9 days · 26 km away
- 17,615 haDima6 January 2019 · 13 days · 27 km away
- 48,364 haDima31 December 2016 · 23 days · 31 km away
- 18,648 haDima14 February 2023 · 6 days · 31 km away
Frequently asked questions
- How long did the Dima fire last?
- GWIS (Copernicus) dates it between 3 February 2026 and 6 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 2,123 hectares (21.2 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Dima (1,440 ha, 0.2 %); Gog (698 ha, 0.2 %).
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Ethiopia (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.
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. 53 Suomi-NPP VIIRS detections on those dates.
- We have not matched this page with any official record.
- 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 ADM3 (Open Data Commons Open Database License 1.0). 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.