Skip to content
worldfires
ET · Ethiopia · →

Gog fire, 28 January 2026 Gog

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

The fire started on 28 January 2026 in Gog, Ethiopia, and satellites saw it burning for 4 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 3,160 hectares from heat detections, spread across a single municipality.

It is the 280th largest in Gambela since 2016 (of 611 with a page). Number 71 in Ethiopia in 2026, of 187.

Compare with…
Burnt area
3,160ha
GWIS perimeter (Copernicus)
Duration
4days
28 Jan 2026 – 31 Jan 2026
Municipalities hit
1
districts
Started on
28 Jan
2026
Heat detections
39
in a single hotspot: 95 MW
Danger at start
45
Very high · FWI index
Average daily power
193MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 28 Jan31 Jan
30 Jan 2026

How it evolved, day by day

28 Jan 2026 · 173 MW · 14 29 Jan 2026 · 239 MW · 11 30 Jan 2026 · 168 MW · 14
28 Jan 29 Jan 30 Jan

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

The weather it burned in

40°high
32km/h · peak gust
17%lowest humidity

It had gone more than two months without rain (1 mm or more) when it started.

This area had burned before

97% of the perimeter overlaps earlier fires recorded since 2016: 1,637 ha in 2016, 781 ha in 2017, 536 ha in 2019, 873 ha in 2020, 1,184 ha in 2021, 603 ha in 2022, 814 ha in 2024, 676 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 3,050 ha that had burned before.

How big is it?

10 km
It burned the equivalent of 2% of the area of London (32 km² against 1,583 km²).

London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).

This compares size, not location: both shapes are at the same scale, north up, centred on each other.

What happened to each town

  1. Gog where it started
    3,180 ha reached on 28 Jan
    1.0 %

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 2025
Built-up area< 0.1 ha
Residents< 20

Inside 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)
28 Jan 38.7 °C 24 % 32 km/h 0.0 mm Very high 45
29 Jan 39.1 °C 18 % 27 km/h 0.0 mm Very high 42
30 Jan 39.7 °C 17 % 28 km/h 0.0 mm Very high 45
31 Jan 38.5 °C 20 % 21 km/h 0.0 mm Very high 43
1 Feb after 35.3 °C 27 % 44 km/h 0.0 mm Extreme 52
2 Feb after 37.6 °C 23 % 23 km/h 0.0 mm High 37
3 Feb after 39.7 °C 20 % 23 km/h 0.0 mm Very high 40
4 Feb after 40.1 °C 21 % 30 km/h 0.0 mm Very high 42
5 Feb after 36.4 °C 23 % 29 km/h 0.0 mm Very high 48
6 Feb after 39.8 °C 22 % 30 km/h 0.0 mm Very high 43
7 Feb after 39.1 °C 19 % 25 km/h 0.0 mm Very high 42
8 Feb after 38.5 °C 16 % 29 km/h 0.0 mm Very high 45
9 Feb after 37.1 °C 29 % 27 km/h 0.0 mm Very high 41

Before and after, from space

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

Before · 21 Jan 2026
After · 7 Feb 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 30 January 2026 the air beside the fire reached 118 µg/m³ of PM2.5. That day averaged 75: 5.0 times the WHO daily guideline (15).

PM2.5 peak118 µg/m³
Days over the guideline8 days
PM10122 µg/m³
Optical depth1.31
26272829303112
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 · 39Every 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 Gog fire last?
According to the heat detections seen by satellite inside the perimeter, it burned from 28 January 2026 to 31 January 2026 (4 days). The perimeter dates it from 28 January 2026 to 30 January 2026.
How much area did it burn?
The perimeter GWIS (Copernicus) rebuilt from heat detections is 3,160 hectares (31.6 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Gog (3,180 ha, 1.0 %).
What was the weather like?
During the fire the temperature reached 39.7 °C, humidity dropped to 17 % and gusts hit 32 km/h. The fire danger index (FWI) reached 45, 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

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.

RSS Changes to this page

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.

How we know this
  • Perimeter: GWIS (Copernicus), rebuilt from heat detections rather than mapped on imagery.
  • Dates adjusted with the VIIRS detections inside the perimeter, which said 28 January 2026 to 30 January 2026. 39 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.

How we build fire pages: methodology ›

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.