How long did the Guba fire last?

GWIS (Copernicus) dates it between 11 January 2023 and 15 January 2023: 5 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,367 hectares (23.7 km²). It is an estimate: official national figures may differ.

Which municipalities burned?

The fire entered 2 municipalities: Guba (2,103 ha, 0.3 %); Dangura (278 ha, 0.1 %).

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.

ET · Ethiopia · 2023-01-11 → 2023-01-15

Guba fire, January 2023 Guba, Dangura

Out · last detection 15 Jan 2023, 11:46 UTC

The fire started on 11 January 2023 in Guba, Ethiopia, and satellites saw it burning for 5 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 2,367 hectares from heat detections, spread across 2 municipalities.

It is the 517th largest in Beneshangul Gumu since 2016 (of 699 with a page). Number 73 in Ethiopia in 2023, of 101.

The power measured by the satellite is low (17.9 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.

Compare with…

Suggestions: Guba · 2019 Guba · 2025 Quara · 2016

Burnt area: 2,367ha; GWIS perimeter (Copernicus)
Duration: 5days; 11 Jan 2023 – 15 Jan 2023
Municipalities hit: 2; districts
Started on: 11 Jan; 2023
Heat detections: 82; in a single hotspot: 18 MW
Average daily power: 74MW; detected power per day, on average

HOTSPOTS BY DAY 11 Jan15 Jan

Play back 15 Jan 2023

How it evolved, day by day

11 Jan 12 Jan 13 Jan 14 Jan 15 Jan

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

This area had burned before

25% of the perimeter overlaps earlier fires recorded since 2016: 581 ha in 2019.

How big is it?

It burned the equivalent of 1.5% of the area of London (24 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

Guba where it started

2,103 ha reached on 11 Jan

0.3 %
Dangura

278 ha reached on 12 Jan

0.1 %

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.

Before and after, from space

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

↔

Before · 4 Jan 2023

After · 22 Jan 2023

Before After

If the day is cloudy, change the date: each satellite passes once a day. In false colour the burnt ground looks brown or red.

Detections table · 82Every 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 time	Satellite	FRP (MW)	Lat	Lon

Other fires nearby

All fires in Ethiopia ›

Frequently asked questions

How long did the Guba fire last?: GWIS (Copernicus) dates it between 11 January 2023 and 15 January 2023: 5 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,367 hectares (23.7 km²). It is an estimate: official national figures may differ.
Which municipalities burned?: The fire entered 2 municipalities: Guba (2,103 ha, 0.3 %); Dangura (278 ha, 0.1 %).
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

NASA FIRMS ↗
GWIS · Copernicus ↗

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?

Dates or duration Place or towns Burned area Name It was not a wildfire Same fire as another page Something else

What really happened?

Your connection to the fire (optional) Email (optional)

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 from the perimeter: the VIIRS detections inside it did not change them. 82 Suomi-NPP VIIRS detections on those dates.
We have not matched this page with any official record.

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.

Where it burned