Skip to content
worldfires
RU · Russia · –

Zeysky District fire, 24 June 2026 Zeysky District, Neryungrinsky Municipal District

Out · last detection 28 Jun 2026, 04:56 UTC

The fire started on 24 June 2026 in Zeysky District, Russia, and satellites saw it burning for 5 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 3,253 hectares from heat detections, spread across 2 municipalities.

Number 379 in Russia in 2026, of 420.

GWIS near-real-time perimeter, from the layer that changed in October 2025: this fire is not compared with fires from earlier years, because since then the GWIS layer gives more and larger perimeters.

Burnt area
3,253ha
GWIS perimeter (Copernicus)
Duration
5days
24 Jun 2026 – 28 Jun 2026
Municipalities hit
2
districts
Started on
24 Jun
2026
Heat detections
201
in a single hotspot: 384 MW
Danger at start
17
Moderate · FWI index
Average daily power
990MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 24 Jun28 Jun
28 Jun 2026

How it evolved, day by day

24 Jun 2026 · 712 MW · 26 25 Jun 2026 · 2,826 MW · 87 26 Jun 2026 · 833 MW · 33 27 Jun 2026 · 94 MW · 21 28 Jun 2026 · 484 MW · 34
24 Jun 25 Jun 26 Jun 27 Jun 28 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

26°high
44km/h · peak gust
19%lowest humidity

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

This area had burned before

86% of the perimeter overlaps earlier fires recorded since 2016: 2,790 ha in 2023.

How big is it?

10 km
It burned the equivalent of 2.1% of the area of London (33 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. Zeysky District where it started
    2,530 ha reached on 24 Jun
    0.0 %
  2. 769 ha reached on 24 Jun
    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)
24 Jun 26.5 °C 19 % 44 km/h 0.0 mm Moderate 17
25 Jun 21.5 °C 29 % 41 km/h 0.0 mm Moderate 21
26 Jun 21.9 °C 30 % 35 km/h 0.0 mm Moderate 19
27 Jun 23.4 °C 31 % 22 km/h 0.0 mm Moderate 17
28 Jun 23.7 °C 35 % 28 km/h 0.0 mm Moderate 21
29 Jun after 20.9 °C 55 % 28 km/h 1.4 mm Moderate 13

Before and after, from space

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

Before · 17 Jun 2026
After · 5 Jul 2026

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 26 June 2026 the air beside the fire reached 219 µg/m³ of PM2.5. That day averaged 90: 6.0 times the WHO daily guideline (15).

PM2.5 peak219 µg/m³
Days over the guideline7 days
PM10220 µg/m³
Optical depth1.69
22 Jun24 Jun26 Jun28 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 · 201Every 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 Zeysky District fire last?
GWIS (Copernicus) dates it between 24 June 2026 and 28 June 2026: 5 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,253 hectares (32.5 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Zeysky District (2,530 ha, 0.0 %); Neryungrinsky Municipal District (769 ha, 0.0 %).
What was the weather like?
During the fire the temperature reached 26.5 °C, humidity dropped to 19 % and gusts hit 44 km/h. The fire danger index (FWI) reached 21, 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.

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