Skip to content
worldfires
RU · Russia · –

Yeravninsky Rayon fire, 13 April 2025 Yeravninsky Rayon

Out · last detection 15 Apr 2025, 19:10 UTC

The fire started on 13 April 2025 in Yeravninsky Rayon, Russia, and satellites saw it burning for 3 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 8,330 hectares from heat detections, spread across a single municipality.

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

Burnt area
8,330ha
GWIS perimeter (Copernicus)
Duration
3days
13 Apr 2025 – 15 Apr 2025
Municipalities hit
1
districts
Started on
13 Apr
2025
Heat detections
409
in a single hotspot: 234 MW
Danger at start
8
Low · FWI index
Average daily power
1.9GW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 13 Apr15 Apr
15 Apr 2025

How it evolved, day by day

13 Apr 2025 · 277 MW · 55 14 Apr 2025 · 4,619 MW · 253 15 Apr 2025 · 774 MW · 101
13 Apr 14 Apr 15 Apr

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

The weather it burned in

18°high
38km/h · peak gust
16%lowest humidity

It had gone 22 days without rain (1 mm or more) when it started. Rain came after the fire: 1.2 mm on 16 Apr.

This area had burned before

No earlier perimeters overlap this fire since 2016, when the satellite record begins.

How big is it?

10 km
It burned the equivalent of 5.3% of the area of London (83 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
    8,325 ha reached on 13 Apr
    0.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 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)
13 Apr 13.5 °C 27 % 34 km/h 0.0 mm Low 8
14 Apr 18.0 °C 16 % 38 km/h 0.0 mm Moderate 14
15 Apr 16.6 °C 20 % 22 km/h 0.0 mm Low 11
16 Apr after 12.0 °C 32 % 41 km/h 1.2 mm Moderate 13

Its twins: fires that started in the same weather

It started with an FWI of 8.4, a minimum humidity of 27% and 22 days without rain. Fires in the area that started in weather like this since 2016: 36.

FWI at the start 8.4
Minimum humidity 27 %
Days without rain 22
this fire chosen twins rest of the area
Almost identicalSimilar

Outlines of the closest twins

Tungokochensky District fire, September 2024
8,832 ha 21 days FWI 8.2 Min. humidity 27 % 112 km away, in 2024

First rain (1 mm or more) after it ended: 4.8 mm on 9 Oct.

What happened to them

12 days
median duration
5,664 ha
median area
28 %
went past 10,000 ha
4.1 mm
rain at the end (median; 35 of 36 had it)

It burned an area similar to its twins (8,330 ha against a median of 5,664 ha) and lasted 3 days, against 12 days.

In 1 of 36, not even 1 mm fell in the ten days after the end: they went out without rain. In the rest, the first rainy day brought a median of 4.1 mm.

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

1.2 mmfirst rain
16 Aprthe day after it ended
38km/h · max. gust

It was considered over on 15 Apr, and on 16 Apr 1.2 mm fell. We do not know whether the rain or the firefighters put it out. Twins with rain when they ended: 35 of 36, with a median of 4.1 mm.

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 · 6 Apr 2025
After · 22 Apr 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 15 April 2025 the air beside the fire reached 535 µg/m³ of PM2.5. That day averaged 241: 16 times the WHO daily guideline (15).

PM2.5 peak535 µg/m³
Days over the guideline8 days
PM10551 µg/m³
Optical depth2.84
11 Apr13 Apr15 Apr17 Apr
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 · 409Every 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 13 April 2025 and 15 April 2025: 3 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 8,330 hectares (83.3 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Yeravninsky Rayon (8,325 ha, 0.3 %).
What was the weather like?
During the fire the temperature reached 18.0 °C, humidity dropped to 16 % and gusts hit 38 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 Russia (geoBoundaries). It is not an official report.
How did the fires that started in similar weather in this area end?
Fires less than 250 km away that started since 2016 with a similar FWI, humidity and dry spell: 36. Their median duration was 12 days and their median area 5,664 ha; 28 % went past 10,000 ha. In 1 of 36, not even 1 mm fell in the ten days after the end: they went out without rain. In the rest, the first rainy day brought a median of 4.1 mm.

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