Moba fire, 30 August 2026 Moba
The fire started on 30 August 2026 in Moba, Democratic Republic of the Congo, and satellites saw it burning for 26 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 10,056 hectares from heat detections, spread across a single municipality.
It is the 40th largest in Tanganyika since 2016 (of 232 with a page). Number 182 in Democratic Republic of the Congo in 2026, of 523.
Compare with…
Suggestions: Moba · 2024Moba · 2016Moba · 2025Moba · 2020
- Burnt area
- 10,056ha
- GWIS perimeter (Copernicus)
- Duration
- 26days
- 30 Aug 2026 – 24 Sept 2026
- Municipalities hit
- 1
- territories
- Started on
- 30 Aug
- 2026
- Heat detections
- 350
- in a single hotspot: 78 MW
- Danger at start
- 29
- High · FWI index
- Average daily power
- 105MW
- 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.
The weather it burned in
It had gone more than two months without rain (1 mm or more) when it started. Rain came after the fire: 1.2 mm on 3 Oct.
This area had burned before
90% of the perimeter overlaps earlier fires recorded since 2016: 4,147 ha in 2016, 2,685 ha in 2017, 2,714 ha in 2018, 4,957 ha in 2019, 1,837 ha in 2020, 4,487 ha in 2021, 4,129 ha in 2022, 2,021 ha in 2023, 3,306 ha in 2024, 5,775 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 9,097 ha that had burned before.
- 3,149 ha Moba fire, September 2024 8,176 ha in total; the hectares shown are those it shares with this fire
- 2,965 ha Moba fire, September 2016 9,378 ha in total; the hectares shown are those it shares with this fire
- 2,492 ha Moba fire, August 2025 7,388 ha in total; the hectares shown are those it shares with this fire
- 1,837 ha Moba fire, October 2020 8,257 ha in total; the hectares shown are those it shares with this fire
- 1,647 ha Moba fire, September 2019 5,523 ha in total; the hectares shown are those it shares with this fire
- 269 ha Moba fire, October 2022 5,827 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
-
Moba where it started10,130 ha reached on 30 Aug0.3 %
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 were about 14 hectares of built-up land and about 4,200 residents (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) |
|---|---|---|---|---|---|
| 30 Aug | 27.9 °C | 29 % | 38 km/h | 0.0 mm | High 29 |
| 31 Aug | 28.8 °C | 28 % | 39 km/h | 0.0 mm | High 31 |
| 1 Sept | 28.8 °C | 30 % | 37 km/h | 0.0 mm | High 30 |
| 2 Sept | 29.4 °C | 28 % | 35 km/h | 0.0 mm | High 30 |
| 3 Sept | 30.5 °C | 20 % | 33 km/h | 0.0 mm | High 35 |
| 4 Sept | 31.0 °C | 26 % | 37 km/h | 0.0 mm | High 36 |
| 5 Sept | 31.1 °C | 27 % | 36 km/h | 0.0 mm | High 36 |
| 6 Sept | 29.6 °C | 29 % | 40 km/h | 0.0 mm | High 37 |
| 7 Sept | 29.0 °C | 30 % | 38 km/h | 0.0 mm | High 36 |
| 8 Sept | 28.2 °C | 30 % | 38 km/h | 0.0 mm | High 36 |
| 9 Sept | 27.0 °C | 35 % | 38 km/h | 0.0 mm | High 33 |
| 10 Sept | 27.4 °C | 34 % | 36 km/h | 0.0 mm | High 32 |
| 11 Sept | 28.8 °C | 31 % | 36 km/h | 0.0 mm | High 32 |
| 12 Sept | 28.2 °C | 37 % | 32 km/h | 0.0 mm | High 30 |
| 13 Sept | 29.2 °C | 34 % | 30 km/h | 0.0 mm | High 29 |
| 14 Sept | 29.8 °C | 33 % | 30 km/h | 0.1 mm | High 29 |
| 15 Sept | 29.5 °C | 37 % | 31 km/h | 1.0 mm | Moderate 21 |
| 16 Sept | 27.4 °C | 38 % | 36 km/h | 0.3 mm | High 25 |
| 17 Sept | 27.6 °C | 34 % | 37 km/h | 0.0 mm | High 27 |
| 18 Sept | 29.5 °C | 34 % | 40 km/h | 0.0 mm | High 30 |
| 19 Sept | 28.9 °C | 34 % | 38 km/h | 0.1 mm | High 30 |
| 20 Sept | 30.4 °C | 23 % | 41 km/h | 0.0 mm | High 37 |
| 21 Sept | 29.6 °C | 31 % | 40 km/h | 0.0 mm | High 37 |
| 22 Sept | 29.8 °C | 33 % | 33 km/h | 0.0 mm | High 33 |
| 23 Sept | 29.5 °C | 36 % | 35 km/h | 0.2 mm | High 32 |
| 24 Sept | 29.0 °C | 40 % | 29 km/h | 0.7 mm | High 24 |
| 25 Sept after | 29.4 °C | 40 % | 32 km/h | 0.6 mm | High 24 |
| 26 Sept after | 30.0 °C | 39 % | 33 km/h | 0.3 mm | High 26 |
| 27 Sept after | 28.4 °C | 39 % | 29 km/h | 0.8 mm | Moderate 21 |
| 28 Sept after | 30.5 °C | 27 % | 39 km/h | 0.0 mm | High 33 |
| 29 Sept after | 30.4 °C | 33 % | 42 km/h | 0.0 mm | High 34 |
| 30 Sept after | 30.1 °C | 29 % | 38 km/h | 0.0 mm | High 33 |
| 1 Oct after | 29.1 °C | 33 % | 32 km/h | 0.2 mm | High 32 |
| 2 Oct after | 28.4 °C | 35 % | 32 km/h | 0.3 mm | High 31 |
| 3 Oct after | 29.2 °C | 40 % | 34 km/h | 1.2 mm | Moderate 19 |
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 19 September 2026 the air beside the fire reached 79 µg/m³ of PM2.5. That day averaged 44: 2.9 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 · 350Every 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 Moba fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 30 August 2026 to 24 September 2026 (26 days). The perimeter dates it from 2 September 2026 to 17 September 2026.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 10,056 hectares (100.6 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Moba (10,130 ha, 0.3 %).
- What was the weather like?
- During the fire the temperature reached 31.1 °C, humidity dropped to 20 % and gusts hit 41 km/h. The fire danger index (FWI) reached 37, class High.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Democratic Republic of the Congo (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 adjusted with the VIIRS detections inside the perimeter, which said 2 September 2026 to 17 September 2026. 350 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 ADM2 (Creative Commons Attribution 3.0 Intergovernmental Organisations (CC BY 3.0 IGO)). 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.