Dorbod-Mongol Autonomous County fire, October 2025 杜尔伯特蒙古族自治县 · Dorbod-Mongol Autonomous County
The fire started on 27 October 2025 in Dorbod-Mongol Autonomous County, China, and satellites saw it burning for 12 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 13,434 hectares from heat detections, spread across a single municipality.
It is the 35th largest in Heilongjiang Province since 2016 (of 1852 with a page). Number 16 in China in 2025, of 711.
- Burnt area
- 13,434ha
- GWIS perimeter (Copernicus)
- Duration
- 12days
- 27 Oct 2025 – 7 Nov 2025
- Municipalities hit
- 1
- counties
- Started on
- 27 Oct
- 2025
- Heat detections
- 344
- in a single hotspot: 59 MW
- Danger at start
- 8
- Low · FWI index
- Average daily power
- 295MW
- 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 6 days without rain (1 mm or more) when it started.
This area had burned before
75% of the perimeter overlaps earlier fires recorded since 2016: 1,309 ha in 2017, 312 ha in 2018, 184 ha in 2019, 1,918 ha in 2020, 2,003 ha in 2022, 10,779 ha in 2024. Part of it burned more than once, so the yearly figures add up to more than the 10,067 ha that had burned before.
- 7,079 ha Dorbod-Mongol Autonomous County fire, February 2024 7,524 ha in total; the hectares shown are those it shares with this fire
- 2,028 ha Dorbod-Mongol Autonomous County fire, October 2024 2,087 ha in total; the hectares shown are those it shares with this fire
- 1,687 ha Dorbod-Mongol Autonomous County fire, October 2022 1,711 ha in total; the hectares shown are those it shares with this fire
- 918 ha Dorbod-Mongol Autonomous County fire, April 2020 1,065 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).
Beijing (Dongcheng and Xicheng) boundary: geoBoundaries · Lee Beryman, OpenStreetMap · © OpenStreetMap contributors (ODbL 1.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).
This compares size, not location: both shapes are at the same scale, north up, centred on each other.
What happened to each town
-
13,429 ha reached on 28 Oct2.2 %
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 26 hectares of built-up land and about 1,100 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) |
|---|---|---|---|---|---|
| 24 Oct | 8.7 °C | 38 % | 34 km/h | 0.0 mm | Low 8 |
| 25 Oct | 9.4 °C | 32 % | 35 km/h | 0.0 mm | Low 10 |
| 26 Oct | 4.4 °C | 41 % | 44 km/h | 0.1 mm | Low 11 |
| 27 Oct | 2.9 °C | 43 % | 45 km/h | 0.0 mm | Low 10 |
| 28 Oct | 3.7 °C | 37 % | 25 km/h | 0.0 mm | Low 8 |
| 29 Oct | 7.5 °C | 58 % | 34 km/h | 0.0 mm | Low 8 |
| 30 Oct | 8.3 °C | 30 % | 34 km/h | 0.0 mm | Low 9 |
| 31 Oct | 9.5 °C | 37 % | 23 km/h | 0.0 mm | Low 8 |
| 1 Nov | 5.2 °C | 51 % | 49 km/h | 0.1 mm | Low 11 |
| 2 Nov | 0.6 °C | 46 % | 52 km/h | 0.0 mm | Low 11 |
| 3 Nov | 7.3 °C | 36 % | 53 km/h | 0.0 mm | Moderate 12 |
| 4 Nov | 10.9 °C | 23 % | 38 km/h | 0.0 mm | Moderate 12 |
| 5 Nov | 10.6 °C | 51 % | 28 km/h | 0.0 mm | Low 9 |
| 6 Nov | 9.9 °C | 40 % | 48 km/h | 0.0 mm | Moderate 14 |
| 7 Nov | -0.2 °C | 40 % | 32 km/h | 0.0 mm | Low 10 |
| 8 Nov after | 1.7 °C | 57 % | 38 km/h | 1.2 mm | Very low 4 |
| 9 Nov after | 1.4 °C | 41 % | 50 km/h | 0.0 mm | Low 7 |
| 10 Nov after | -0.7 °C | 45 % | 26 km/h | 0.0 mm | Low 5 |
| 11 Nov after | 4.8 °C | 38 % | 28 km/h | 0.0 mm | Low 7 |
| 12 Nov after | 7.1 °C | 40 % | 38 km/h | 0.0 mm | Low 10 |
| 13 Nov after | 2.8 °C | 24 % | 50 km/h | 0.0 mm | Moderate 13 |
| 14 Nov after | 0.9 °C | 34 % | 17 km/h | 0.0 mm | Low 7 |
| 15 Nov after | 3.6 °C | 38 % | 37 km/h | 0.0 mm | Low 11 |
| 16 Nov after | 0.2 °C | 37 % | 45 km/h | 0.0 mm | Moderate 13 |
| 17 Nov after | -3.4 °C | 35 % | 46 km/h | 0.0 mm | Moderate 12 |
| 18 Nov after | -1.4 °C | 39 % | 28 km/h | 0.0 mm | Low 9 |
| 19 Nov after | 6.4 °C | 26 % | 39 km/h | 0.0 mm | Moderate 13 |
| 20 Nov after | 1.8 °C | 35 % | 40 km/h | 0.0 mm | Moderate 12 |
| 21 Nov after | 2.1 °C | 35 % | 35 km/h | 0.0 mm | Moderate 12 |
| 22 Nov after | 8.5 °C | 34 % | 38 km/h | 0.0 mm | Moderate 12 |
| 23 Nov after | 4.4 °C | 52 % | 24 km/h | 0.0 mm | Low 8 |
| 24 Nov after | -0.3 °C | 47 % | 31 km/h | 0.0 mm | Low 9 |
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 29 October 2025 the air beside the fire reached 63 µg/m³ of PM2.5. That day averaged 37: 2.5 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 · 344Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 7,524 haDorbod-Mongol Autonomous County 杜尔伯特蒙古族自治县14 February 2024 · 4 days · 2 km away
- 3,794 haDorbod-Mongol Autonomous County 杜尔伯特蒙古族自治县2 November 2025 · 6 days · 17 km away
- 4,766 haZhenlai County 镇赉县13 March 2021 · 6 days · 33 km away
- 17,268 haZhenlai County 镇赉县14 March 2025 · 11 days · 37 km away
- 28,521 haZhenlai County 镇赉县11 November 2025 · 13 days · 38 km away
- 10,640 haZhenlai County 镇赉县7 March 2016 · 13 days · 39 km away
Frequently asked questions
- How long did the Dorbod-Mongol Autonomous County fire last?
- GWIS (Copernicus) dates it between 27 October 2025 and 7 November 2025: 12 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 13,434 hectares (134.3 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Dorbod-Mongol Autonomous County (13,429 ha, 2.2 %).
- What was the weather like?
- During the fire the temperature reached 10.9 °C, humidity dropped to 23 % and gusts hit 53 km/h. The fire danger index (FWI) reached 14, class Moderate.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of China (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.
Emergency number: 119 · Emergency number and official warnings ›
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. 344 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.