Gog fire, 18 January 2025 Gog
The fire started on 18 January 2025 in Gog, Ethiopia, and satellites saw it burning for 1 day. Copernicus’s global GWIS system rebuilt a burnt perimeter of 2,555 hectares from heat detections, spread across a single municipality.
It is the 419th largest in Gambela since 2016 (of 611 with a page). Number 77 in Ethiopia in 2025, of 127.
Compare with…
Suggestions: Gog · 2020Gog · 2021Gog · 2022Gog · 2016
- Burnt area
- 2,555ha
- GWIS perimeter (Copernicus)
- Duration
- 1day
- 18 Jan 2025 – 18 Jan 2025
- Municipalities hit
- 1
- districts
- Started on
- 18 Jan
- 2025
- Heat detections
- 72
- in a single hotspot: 124 MW
- Danger at start
- 47
- Very high · FWI index
- Average daily power
- 1.1GW
- detected power per day, on average
Where it burned
How it evolved, day by day
18 Jan 2025 · 1,097 MW · 66
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
98% of the perimeter overlaps earlier fires recorded since 2016: 1,323 ha in 2016, 1,539 ha in 2020, 1,390 ha in 2021, 838 ha in 2022, 368 ha in 2023. Part of it burned more than once, so the yearly figures add up to more than the 2,516 ha that had burned before.
- 931 ha Gog fire, February 2020 7,994 ha in total; the hectares shown are those it shares with this fire
- 873 ha Gog fire, January 2021 3,722 ha in total; the hectares shown are those it shares with this fire
- 828 ha Gog fire, January 2022 3,331 ha in total; the hectares shown are those it shares with this fire
- 531 ha Gog fire, December 2016 4,357 ha in total; the hectares shown are those it shares with this fire
- 517 ha Gog fire, January 2021 4,103 ha in total; the hectares shown are those it shares with this fire
- 426 ha Gog fire, January 2016 5,067 ha in total; the hectares shown are those it shares with this fire
- 412 ha Gog fire, January 2020 2,039 ha in total; the hectares shown are those it shares with this fire
- 368 ha Gog fire, January 2023 2,257 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
-
Gog where it started2,571 ha reached on 17 Jan0.8 %
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) |
|---|---|---|---|---|---|
| 18 Jan | 39.4 °C | 18 % | 34 km/h | 0.0 mm | Very high 47 |
| 19 Jan after | 39.7 °C | 18 % | 23 km/h | 0.0 mm | Very high 42 |
| 20 Jan after | 40.0 °C | 16 % | 19 km/h | 0.0 mm | Very high 42 |
| 21 Jan after | 40.1 °C | 16 % | 32 km/h | 0.0 mm | Very high 46 |
| 22 Jan after | 39.1 °C | 15 % | 35 km/h | 0.0 mm | Very high 49 |
| 23 Jan after | 38.9 °C | 19 % | 27 km/h | 0.0 mm | Very high 45 |
| 24 Jan after | 37.5 °C | 18 % | 31 km/h | 0.0 mm | Very high 48 |
| 25 Jan after | 38.7 °C | 21 % | 24 km/h | 0.0 mm | Very high 44 |
| 26 Jan after | 38.6 °C | 15 % | 23 km/h | 0.0 mm | Very high 43 |
| 27 Jan after | 38.7 °C | 12 % | 23 km/h | 0.0 mm | Very high 48 |
| 28 Jan after | 38.7 °C | 11 % | 23 km/h | 0.0 mm | Very high 48 |
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 21 January 2025 the air beside the fire reached 54 µg/m³ of PM2.5. That day averaged 42: 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 · 72Every 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 Gog fire last?
- GWIS (Copernicus) dates it between 18 January 2025 and 18 January 2025: 1 day 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,555 hectares (25.6 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Gog (2,571 ha, 0.8 %).
- What was the weather like?
- During the fire the temperature reached 39.4 °C, humidity dropped to 18 % and gusts hit 34 km/h. The fire danger index (FWI) reached 47, 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.
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. 72 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 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.