Skip to content
worldfires
RU · Russia · –

Yeravninsky Rayon fire, 23 June 2025 Yeravninsky Rayon, Bauntovsky Rayon

Out · last detection 29 Jun 2025, 05:13 UTC

The fire started on 23 June 2025 in Yeravninsky Rayon, Russia, and satellites saw it burning for 7 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 3,200 hectares from heat detections, spread across 2 municipalities.

It is the 176th largest in Buryatia since 2016 (of 198 with a page). Number 227 in Russia in 2025, of 238.

Burnt area
3,200ha
GWIS perimeter (Copernicus)
Duration
7days
23 Jun 2025 – 29 Jun 2025
Municipalities hit
2
districts
Started on
23 Jun
2025
Heat detections
242
in a single hotspot: 175 MW
Danger at start
39
Very high · FWI index
Average daily power
388MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 23 Jun29 Jun
29 Jun 2025

How it evolved, day by day

23 Jun 2025 · 27 MW · 22 24 Jun 2025 · 126 MW · 37 25 Jun 2025 · 2,195 MW · 127 26 Jun 2025 · 287 MW · 45 27 Jun 2025 · 2 MW · 2 28 Jun 2025 · 62 MW · 5 29 Jun 2025 · 16 MW · 4
23 Jun 25 Jun 27 Jun 29 Jun

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

The weather it burned in

33°high
48km/h · peak gust
20%lowest humidity

It had gone 4 days without rain (1 mm or more) when it started. Rain came after the fire: 14.2 mm on 30 Jun.

This area had burned before

66% of the perimeter overlaps earlier fires recorded since 2016: 625 ha in 2016, 1,811 ha in 2020. Part of it burned more than once, so the yearly figures add up to more than the 2,101 ha that had burned before.

How big is it?

10 km
It burned the equivalent of 2% of the area of London (32 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

  1. Yeravninsky Rayon where it started
    3,193 ha reached on 23 Jun
    0.1 %
  2. 26 ha
    0.0 %

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 2025
Built-up area< 0.1 ha
Residents< 20

Inside 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)
23 Jun 28.5 °C 29 % 41 km/h 0.3 mm Very high 39
24 Jun 29.3 °C 25 % 22 km/h 0.0 mm High 28
25 Jun 32.7 °C 20 % 31 km/h 0.0 mm High 36
26 Jun 30.9 °C 30 % 46 km/h 1.0 mm High 32
27 Jun 28.1 °C 33 % 35 km/h 0.9 mm Moderate 16
28 Jun 23.4 °C 35 % 48 km/h 0.0 mm High 30
29 Jun 24.2 °C 30 % 26 km/h 0.0 mm High 23
30 Jun after 17.9 °C 42 % 54 km/h 14.2 mm Very low 1

Its twins: fires that started in the same weather

It started with an FWI of 39.3, a minimum humidity of 29% and 4 days without rain. Fires in the area that started in weather like this since 2016: 6.

FWI at the start 39.3
Minimum humidity 29 %
Days without rain 4
this fire chosen twins rest of the area
Almost identicalSimilar

Outlines of the closest twins

Khorinsky Rayon fire, July 2016
9,433 ha 7 days FWI 25.6 Min. humidity 29 % 167 km away, in 2016

First rain (1 mm or more) after it ended: 3.2 mm on 10 Jul.

What happened to them

Fires in the area that started in similar weather: 6. With fewer than 15 we give no figures: they would be more noise than signal.

This is a bank of analogues: it shows what usually happens, not what will happen. With fewer than 15 twins we give no figures. How we calculate it

How it ended

14.2 mmfirst rain
30 Junthe day after it ended
48km/h · max. gust

It was considered over on 29 Jun, and on 30 Jun 14.2 mm fell. We do not know whether the rain or the firefighters put it out.

Weather on this page: Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)

How a twin is chosen

  • Same area: fires that have already ended, less than 250 km from this one, since 2016.
  • Same start: we compare the FWI on the first day, the minimum humidity that day and the run of days without rain before it. The slider sets how much they may differ.
  • Only pages with final weather data (ERA5 reanalysis) calculated in the same way as this fire’s; agricultural and grass burns and pages with data under review are left out.
  • Fires burning at the same time as this one (a week before or after) are left out: they share the same spell of weather and do not count as a precedent.
  • They are sorted by similarity, and the outlines of the first five are drawn.

How we calculate it

Before and after, from space

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

Before · 16 Jun 2025
After · 6 Jul 2025

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 · Copernicus

On 25 June 2025 the air beside the fire reached 236 µg/m³ of PM2.5. That day averaged 143: 9.5 times the WHO daily guideline (15).

PM2.5 peak236 µg/m³
Days over the guideline11 days
PM10250 µg/m³
Optical depth2.95
21 Jun24 Jun27 Jun30 Jun
Good Fair Moderate Poor Very poor Extremely poor

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 · 242Every 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 timeSatelliteFRP (MW)LatLon

Other fires nearby

All fires in Russia

Frequently asked questions

How long did the Yeravninsky Rayon fire last?
GWIS (Copernicus) dates it between 23 June 2025 and 29 June 2025: 7 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 3,200 hectares (32.0 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Yeravninsky Rayon (3,193 ha, 0.1 %); Bauntovsky Rayon (26 ha, 0.0 %).
What was the weather like?
During the fire the temperature reached 32.7 °C, humidity dropped to 20 % and gusts hit 48 km/h. The fire danger index (FWI) reached 39, class Very 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 · 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.

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?

We will only use your email to reply about this report. Privacy. This is not an emergency service: if there is a fire now, call 112.

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. 242 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.

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 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.