Mirninsky Ulus fire, 29 July 2026 Mirninsky Ulus
The fire started on 29 July 2026 in Mirninsky Ulus, Russia, and satellites saw it burning for 36 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 21,204 hectares from heat detections, spread across a single municipality.
It is the 258th largest in Sakha Republic since 2016 (of 1422 with a page). Number 54 in Russia in 2026, of 419.
- Burnt area
- 21,204ha
- GWIS perimeter (Copernicus)
- Duration
- 36days
- 29 Jul 2026 – 2 Sept 2026
- Municipalities hit
- 1
- districts
- Started on
- 29 Jul
- 2026
- Heat detections
- 2,279
- in a single hotspot: 524 MW
- Danger at start
- 20
- Moderate · FWI index
- Energy released
- 37.3GW
- sum of detected power
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 8 days without rain (1 mm or more) when it started. Rain came after the fire: 1.0 mm on 29 Aug.
This area had burned before
3% of the perimeter overlaps earlier fires recorded since 2016: 567 ha in 2020.
What happened to each town
-
Mirninsky Ulus where it started22,577 ha reached on 29 Jul0.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.
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) |
|---|---|---|---|---|---|
| 29 Jul | 30.6 °C | 24 % | 21 km/h | 0.0 mm | Moderate 20 |
| 30 Jul | 30.6 °C | 23 % | 28 km/h | 0.0 mm | High 23 |
| 31 Jul | 30.6 °C | 26 % | 20 km/h | 0.0 mm | High 21 |
| 1 Aug | 31.1 °C | 25 % | 26 km/h | 0.0 mm | High 24 |
| 2 Aug | 28.4 °C | 29 % | 46 km/h | 3.5 mm | Moderate 11 |
| 3 Aug | 14.1 °C | 46 % | 43 km/h | 0.0 mm | Moderate 13 |
| 4 Aug | 14.7 °C | 37 % | 29 km/h | 0.0 mm | Moderate 13 |
| 5 Aug | 21.0 °C | 30 % | 25 km/h | 0.0 mm | Moderate 16 |
| 6 Aug | 23.4 °C | 27 % | 44 km/h | 0.0 mm | High 24 |
| 7 Aug | 21.6 °C | 37 % | 45 km/h | 0.6 mm | Moderate 20 |
| 8 Aug | 22.8 °C | 45 % | 27 km/h | 0.0 mm | Moderate 16 |
| 9 Aug | 17.8 °C | 41 % | 37 km/h | 0.1 mm | Moderate 19 |
| 10 Aug | 17.5 °C | 40 % | 26 km/h | 0.0 mm | Moderate 17 |
| 11 Aug | 17.4 °C | 36 % | 27 km/h | 0.0 mm | Moderate 18 |
| 12 Aug | 18.0 °C | 35 % | 10 km/h | 0.0 mm | Moderate 14 |
| 13 Aug | 16.1 °C | 46 % | 30 km/h | 0.8 mm | Moderate 12 |
| 14 Aug | 14.0 °C | 54 % | 28 km/h | 0.1 mm | Moderate 12 |
| 15 Aug | 13.1 °C | 53 % | 30 km/h | 0.0 mm | Moderate 12 |
| 16 Aug | 18.2 °C | 50 % | 41 km/h | 0.2 mm | Moderate 15 |
| 17 Aug | 18.4 °C | 53 % | 41 km/h | 1.7 mm | Low 7 |
| 18 Aug | 16.0 °C | 51 % | 27 km/h | 0.0 mm | Low 9 |
| 19 Aug | 15.6 °C | 42 % | 21 km/h | 0.0 mm | Moderate 11 |
| 20 Aug | 18.0 °C | 32 % | 10 km/h | 0.0 mm | Moderate 13 |
| 21 Aug | 19.5 °C | 31 % | 12 km/h | 0.0 mm | Moderate 16 |
| 22 Aug | 19.1 °C | 36 % | 16 km/h | 0.0 mm | Moderate 16 |
| 23 Aug | 19.5 °C | 32 % | 11 km/h | 0.0 mm | Moderate 16 |
| 24 Aug | 21.5 °C | 30 % | 24 km/h | 0.0 mm | Moderate 21 |
| 25 Aug | 20.4 °C | 36 % | 21 km/h | 0.0 mm | Moderate 20 |
| 26 Aug | 21.1 °C | 30 % | 32 km/h | 0.0 mm | High 24 |
| 27 Aug | 20.5 °C | 30 % | 26 km/h | 0.0 mm | High 23 |
| 28 Aug | 20.3 °C | 33 % | 18 km/h | 0.0 mm | Moderate 21 |
| 29 Aug | 18.9 °C | 48 % | 32 km/h | 1.0 mm | Moderate 12 |
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 28 August 2026 the air beside the fire reached 3,107 µg/m³ of PM2.5. That day averaged 1,967: 131 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 · 2,279Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 46,446 haMirninsky Ulus23 June 2020 · 16 days · 12 km away
- 9,968 haMirninsky Ulus3 August 2026 · 14 days · 25 km away
- 71,903 haMirninsky Ulus29 July 2026 · 35 days · 31 km away
- 6,515 haMirninsky Ulus19 August 2026 · 14 days · 35 km away
- 5,590 haMirninsky Ulus29 June 2020 · 8 days · 38 km away
- 5,007 haMirninsky Ulus14 August 2020 · 10 days · 39 km away
Frequently asked questions
- How long did the Mirninsky Ulus fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 29 July 2026 to 2 September 2026 (36 days). The perimeter dates it from 29 July 2026 to 26 August 2026.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 21,204 hectares (212.0 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Mirninsky Ulus (22,577 ha, 0.1 %).
- What was the weather like?
- During the fire the temperature reached 31.1 °C, humidity dropped to 23 % and gusts hit 46 km/h. The fire danger index (FWI) reached 24, class High.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Russia (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: 112
Satellite cross-check
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
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 (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.