Skip to content
worldfires
RU · Russia · →

Tazovsky Rayon fire, 21 August 2026 Tazovsky Rayon

Out · last detection 26 Aug 2026, 06:37 UTC

The fire started on 21 August 2026 in Tazovsky Rayon, Russia, and satellites saw it burning for 6 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 13,028 hectares from heat detections, spread across a single municipality.

It is the 31th largest in Yamalo-Nenets Autonomous Okrug since 2016 (of 123 with a page). Number 90 in Russia in 2026, of 421.

Compare with…
Burnt area
13,028ha
GWIS perimeter (Copernicus)
Duration
6days
21 Aug 2026 – 26 Aug 2026
Municipalities hit
1
districts
Started on
21 Aug
2026
Heat detections
1,557
in a single hotspot: 298 MW
Danger at start
24
High · FWI index
Average daily power
3.1GW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 21 Aug26 Aug
26 Aug 2026

How it evolved, day by day

21 Aug 2026 · 983 MW · 160 22 Aug 2026 · 10,630 MW · 549 23 Aug 2026 · 1,931 MW · 315 24 Aug 2026 · 2,573 MW · 324 25 Aug 2026 · 2,518 MW · 189 26 Aug 2026 · 115 MW · 20
21 Aug 22 Aug 23 Aug 24 Aug 25 Aug 26 Aug

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

The weather it burned in

25°high
88km/h · peak gust
33%lowest humidity

It had gone 11 days without rain (1 mm or more) when it started. Rain came after the fire: 15.9 mm on 27 Aug.

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 8.2% of the area of London (130 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. Tazovsky Rayon where it started
    12,420 ha reached on 21 Aug
    0.1 %

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)
21 Aug 25.0 °C 33 % 29 km/h 0.0 mm High 24
22 Aug 23.6 °C 41 % 39 km/h 0.0 mm High 26
23 Aug 22.4 °C 42 % 20 km/h 0.0 mm Moderate 19
24 Aug 22.1 °C 45 % 34 km/h 0.0 mm High 23
25 Aug 20.9 °C 53 % 50 km/h 0.3 mm High 26
26 Aug 18.4 °C 62 % 88 km/h 0.4 mm High 34
27 Aug after 19.1 °C 65 % 59 km/h 15.9 mm Very low 2

Before and after, from space

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

Before · 14 Aug 2026
After · 2 Sept 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 23 August 2026 the air beside the fire reached 691 µg/m³ of PM2.5. That day averaged 365: 24 times the WHO daily guideline (15).

PM2.5 peak691 µg/m³
Days over the guideline6 days
PM10697 µg/m³
Optical depth3.39
1920212223242526272829
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 · 1,557Every 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

Frequently asked questions

How long did the Tazovsky Rayon fire last?
GWIS (Copernicus) dates it between 21 August 2026 and 26 August 2026: 6 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,028 hectares (130.3 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Tazovsky Rayon (12,420 ha, 0.1 %).
What was the weather like?
During the fire the temperature reached 25.0 °C, humidity dropped to 33 % and gusts hit 88 km/h. The fire danger index (FWI) reached 34, 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 · 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.

RSS Changes to this page

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. 1,557 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.