Skip to content
worldfires
ET · Ethiopia · →

Abobo fire, December 2025 Gog, Abobo

Out · last detection 8 Jan 2026, 11:30 UTC

The fire started on 31 December 2025 in Abobo, Ethiopia, and satellites saw it burning for 8 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 7,057 hectares from heat detections, spread across 2 municipalities.

It is the 89th largest in Gambela since 2016 (of 611 with a page). Number 14 in Ethiopia in 2025, of 127.

Burnt area
7,057ha
GWIS perimeter (Copernicus)
Duration
8days
31 Dec 2025 – 7 Jan 2026
Municipalities hit
2
districts
Started on
31 Dec
2025
Heat detections
129
in a single hotspot: 62 MW
Danger at start
36
High · FWI index
Energy released
1.2GW
sum of detected power

Where it burned

8 Jan 2026
HOTSPOTS BY DAY 31 Dec7 Jan

How it evolved, day by day

12345678

Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.

The weather it burned in

38°high
30km/h · peak gust
18%lowest humidity

It had gone 55 days without rain (1 mm or more) when it started.

This area had burned before

62% of the perimeter overlaps earlier fires recorded since 2016: 3,363 ha in 2016, 156 ha in 2017, 329 ha in 2018, 479 ha in 2021, 241 ha in 2022, 1,268 ha in 2023. Part of it burned more than once, so the yearly figures add up to more than the 4,347 ha that had burned before.

What happened to each town

  1. Gog
    6,134 ha reached on 2 Jan
    1.9 %
  2. Abobo where it started
    972 ha reached on 1 Jan
    0.3 %

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)
31 Dec 36.7 °C 23 % 18 km/h 0.0 mm High 36
1 Jan 37.4 °C 22 % 18 km/h 0.0 mm High 36
2 Jan 34.7 °C 24 % 25 km/h 0.0 mm Very high 40
3 Jan 37.5 °C 25 % 18 km/h 0.0 mm High 37
4 Jan 37.8 °C 20 % 18 km/h 0.0 mm High 36
5 Jan 37.8 °C 18 % 17 km/h 0.0 mm Very high 39
6 Jan 37.6 °C 24 % 30 km/h 0.0 mm Very high 42
7 Jan 38.0 °C 24 % 21 km/h 0.0 mm High 37
8 Jan after 38.9 °C 16 % 23 km/h 0.0 mm Very high 39
9 Jan after 38.1 °C 20 % 27 km/h 0.0 mm Very high 44
10 Jan after 37.5 °C 19 % 23 km/h 0.0 mm Very high 41
11 Jan after 38.3 °C 21 % 25 km/h 0.0 mm Very high 41
12 Jan after 38.0 °C 20 % 17 km/h 0.0 mm Very high 41
13 Jan after 38.2 °C 19 % 30 km/h 0.0 mm Very high 45
14 Jan after 37.0 °C 21 % 28 km/h 0.0 mm Very high 43
15 Jan after 37.5 °C 21 % 28 km/h 0.0 mm Very high 44
16 Jan after 36.3 °C 21 % 20 km/h 0.0 mm Very high 43
17 Jan after 36.8 °C 20 % 24 km/h 0.0 mm Very high 47

Before and after, from space

Drag the line to compare the same ground before the fire and after it.

Before · 24 Dec 2025
After · 14 Jan 2026

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 · Copernicus

On 10 January 2026 the air beside the fire reached 60 µg/m³ of PM2.5. That day averaged 41: 2.8 times the WHO daily guideline (15).

PM2.5 peak60 µg/m³
Days over the guideline13 days
PM1064 µg/m³
Optical depth0.72
29303112345678910
Good Fair Moderate Poor Very poor Extremely poor

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 · 129Every 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 timeSatelliteFRP (MW)LatLon

Other fires nearby

All fires in Ethiopia ›

Frequently asked questions

How long did the Abobo fire last?
GWIS (Copernicus) dates it between 31 December 2025 and 7 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 7,057 hectares (70.6 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Gog (6,134 ha, 1.9 %); Abobo (972 ha, 0.3 %).
What was the weather like?
During the fire the temperature reached 38.0 °C, humidity dropped to 18 % and gusts hit 30 km/h. The fire danger index (FWI) reached 42, class Very high.
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

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
What do you think is wrong?

We will only use your email to reply about this report. Privacy.

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.