Burned area
satellite only18,497ha
Perimeter published by GWIS (Copernicus).
- Source
- GWIS (Copernicus)
- Date
- 21 Jun 2026 – 5 Jul 2026
+− cross-check
No official record is matched to this page to compare it with.
RU · Russia · –
Tigilsky District fire, June 2026 Tigilsky District
Out · last detection 5 Jul 2026, 02:43 UTC
The fire started on 21 June 2026 in Tigilsky District, Russia, and satellites saw it burning for 15 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 18,497 hectares from heat detections, spread across a single municipality.
Number 67 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.
Use this data
Compare with…
Use this data
Fire page data · version 2026-10-24matches the official recordwith caveatssatellite onlymodel
When copying, the sentence is
Tick the figures you want: they make up the lede and the CSV.
Duration by satellite
satellite only15days
21 Jun 2026 to 5 Jul 2026: first and last day with fire on the page.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- last detection: 5 Jul 2026, 02:43 UTC
+− cross-check
Satellites pass a few times a day and cloud or smoke can hide the fire: a lack of detections is not an official extinction. Each country’s emergency service declares a fire contained or out.
Start
satellite only21 Jun 2026
First day with fire seen by the satellites or the perimeter.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- 21 Jun 2026
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
Hotspots
satellite only971
VIIRS detections at 375 m. Most intense hotspot: 82 MW.
- Source
- NASA FIRMS · VIIRS (Suomi NPP)
- Date
- 21 Jun 2026 – 5 Jul 2026
+− cross-check
There is no official record to compare with. Each hotspot is a pixel detected in one satellite pass, not a separate fire.
The worst day
satellite only2,051MW
Total radiative power on 1 July 2026; hotspots that day: 234.
- Source
- NASA FIRMS · VIIRS (FRP)
- Date
- 1 Jul 2026
+− cross-check
Fire radiative power (FRP) measures the energy the fire gives off when the satellite passes. Added up by day, it compares intensity, not area.
Danger at the start
model14.0FWI · moderate
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 2.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 21 Jun 2026, local noon
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
This is an index computed from weather model data, not a measurement of the fire nor an official warning. Danger warnings are issued by each country’s authority. Emergency number and official warnings
Weather during the fire
model22.7°C · 36% RH
High of 22.7 °C and minimum humidity of 36% on 3 July 2026; gusts of 49 km/h on 29 June 2026.
- Source
- weather model at the fire’s grid cell
- Date
- 21 Jun 2026 – 5 Jul 2026
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
These are model values for a cell of about 25 km, not from a weather station: they may differ from what was measured on the ground.
This page’s change log has been kept since 24 October 2026: every night what it publishes is compared and the difference is logged. Anything earlier is reconstructed from each source’s date and marked as reconstructed.
Show
-
· reconstructed GHSLPopulation and built-up area computed
-
· reconstructed weatherWeather and FWI computed from the ERA5 reanalysis
What was saved on 24 October 2026
Every night a snapshot of what the page shows is saved. If anything changes, it appears in the list as a log entry.
- Area
- 18,497 ha
- Dates
- 21 Jun 2026 – 5 Jul 2026
- Name
- Tigilsky District
- Official record
- —
Versioned permanent link
https://worldfires.org/en/fire/tigilsky-district-2026-06?v=2026-10-24A version keeps the area, dates, name and official record; the area as it was logged (changes under 2% are not logged). The map, hotspots and weather always show today’s data.
Citation
A lede of about 60 words figures only, no adjectives
CSV for this fire tigilsky-district-2026-06.csv · daily, no individual hotspots
| fecha | focos_viirs | frp_mw | tmax_c | tmin_c | hr_min_pct | viento_max_kmh | racha_max_kmh | precip_mm | fwi | clase_fwi | dentro_del_incendio |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2026-06-21 | 0 | 0 | 21.6 | 9.1 | 30 | 20.7 | 37.1 | 0 | 14 | moderado | 1 |
| 2026-06-22 | 5 | 21 | 20.7 | 8.7 | 40 | 21.9 | 36.7 | 0 | 15.3 | moderado | 1 |
| 2026-06-23 | 21 | 226 | 19.5 | 9.5 | 36 | 25.5 | 46.4 | 0 | 17.8 | moderado | 1 |
| 2026-06-24 | 54 | 614 | 18.3 | 9 | 37 | 24.2 | 42.8 | 0 | 17.9 | moderado | 1 |
| 2026-06-25 | 101 | 1,290 | 20.1 | 7.8 | 40 | 20.6 | 37.1 | 0.1 | 16.9 | moderado | 1 |
| 2026-06-26 | 18 | 31 | 18.2 | 9.1 | 46 | 18.3 | 34.9 | 0 | 14.8 | moderado | 1 |
| 2026-06-27 | 96 | 957 | 20.7 | 7.8 | 32 | 15.3 | 26.6 | 0 | 15.3 | moderado | 1 |
| 2026-06-28 | 58 | 627 | 22.6 | 9.3 | 31 | 18.1 | 31.7 | 0 | 18.3 | moderado | 1 |
| 2026-06-29 | 75 | 1,170 | 21.6 | 8.3 | 32 | 28.1 | 49 | 0 | 24.7 | alto | 1 |
| 2026-06-30 | 63 | 147 | 18.1 | 11.7 | 46 | 23.5 | 36.4 | 0 | 19.6 | moderado | 1 |
| 2026-07-01 | 234 | 2,051 | 21.6 | 8.4 | 36 | 17 | 31.3 | 0 | 17.3 | moderado | 1 |
| 2026-07-02 | 116 | 1,894 | 20.2 | 10.9 | 39 | 20.3 | 34.6 | 0 | 19.4 | moderado | 1 |
| 2026-07-03 | 103 | 710 | 22.7 | 9 | 36 | 22 | 38.9 | 0 | 21.2 | moderado | 1 |
| 2026-07-04 | 16 | 110 | 21.2 | 12.4 | 42 | 18.8 | 37.8 | 0 | 19.9 | moderado | 1 |
| 2026-07-05 | 11 | 113 | 20.5 | 13.7 | 47 | 16.8 | 29.9 | 0.2 | 18.1 | moderado | 1 |
| 2026-07-06 | 0 | 0 | 19.1 | 10.2 | 50 | 17.5 | 32.4 | 0.1 | 17.4 | moderado | 0 |
| 2026-07-07 | 0 | 0 | 16.9 | 9.6 | 60 | 16 | 28.1 | 0 | 14 | moderado | 0 |
| 2026-07-08 | 0 | 0 | 12.9 | 9.7 | 74 | 17.7 | 33.5 | 2.3 | 3.4 | muy_bajo | 0 |
It is generated in your browser from this page’s data: one file per fire, aggregated by day and without individual hotspots.
Live widget for your story
It updates itself while the fire is still active and links to this page. Free, with the attribution shown at the bottom.
Sources for this page: GWIS (Copernicus), NASA FIRMS (VIIRS), ERA5 (ECMWF/Copernicus C3S) · Open-Meteo.com (CC BY 4.0), GHSL (JRC). Open-Meteo.com · How we build fire pages: methodology
- Burnt area
- 18,497ha
- GWIS perimeter (Copernicus)
- Duration
- 15days
- 21 Jun 2026 – 5 Jul 2026
- Municipalities hit
- 1
- districts
- Started on
- 21 Jun
- 2026
- Heat detections
- 971
- in a single hotspot: 82 MW
- Danger at start
- 14
- Moderate · FWI index
- Average daily power
- 711MW
- detected power per day, on average
Where it burned
HOTSPOTS BY DAY
21 Jun5 Jul
5 Jul 2026
How it evolved, day by day
22 Jun
25 Jun
28 Jun
1 Jul
4 Jul
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
23°high
49km/h · peak gust
30%lowest humidity
It had gone 2 days without rain (1 mm or more) when it started. Rain came after the fire: 2.3 mm on 8 Jul.
This area had burned before
No earlier perimeters overlap this fire since 2016, when the satellite record begins.
How big is it?
London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).
Moscow boundary: geoBoundaries · OpenStreetMap, Wambacher · © OpenStreetMap contributors (ODbL 1.0).
Paris boundary: geoBoundaries · Institut national de l'information géographique et forestière (IGN-F) (Etalab Open License 2.0).
Madrid boundary: geoBoundaries · Open Data ESRI, IGN Central Registry of Cartography Area (CC BY 4.0).
This compares size, not location: both shapes are at the same scale, north up, centred on each other.
What happened to each town
-
Tigilsky District where it started18,246 ha reached on 22 Jun0.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 2025Built-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 Jun | 21.6 °C | 30 % | 37 km/h | 0.0 mm | Moderate 14 |
| 22 Jun | 20.7 °C | 40 % | 37 km/h | 0.0 mm | Moderate 15 |
| 23 Jun | 19.5 °C | 36 % | 46 km/h | 0.0 mm | Moderate 18 |
| 24 Jun | 18.3 °C | 37 % | 43 km/h | 0.0 mm | Moderate 18 |
| 25 Jun | 20.1 °C | 40 % | 37 km/h | 0.1 mm | Moderate 17 |
| 26 Jun | 18.2 °C | 46 % | 35 km/h | 0.0 mm | Moderate 15 |
| 27 Jun | 20.7 °C | 32 % | 27 km/h | 0.0 mm | Moderate 15 |
| 28 Jun | 22.6 °C | 31 % | 32 km/h | 0.0 mm | Moderate 18 |
| 29 Jun | 21.6 °C | 32 % | 49 km/h | 0.0 mm | High 25 |
| 30 Jun | 18.1 °C | 46 % | 36 km/h | 0.0 mm | Moderate 20 |
| 1 Jul | 21.6 °C | 36 % | 31 km/h | 0.0 mm | Moderate 17 |
| 2 Jul | 20.2 °C | 39 % | 35 km/h | 0.0 mm | Moderate 19 |
| 3 Jul | 22.7 °C | 36 % | 39 km/h | 0.0 mm | Moderate 21 |
| 4 Jul | 21.2 °C | 42 % | 38 km/h | 0.0 mm | Moderate 20 |
| 5 Jul | 20.5 °C | 47 % | 30 km/h | 0.2 mm | Moderate 18 |
| 6 Jul after | 19.1 °C | 50 % | 32 km/h | 0.1 mm | Moderate 17 |
| 7 Jul after | 16.9 °C | 60 % | 28 km/h | 0.0 mm | Moderate 14 |
| 8 Jul after | 12.9 °C | 74 % | 34 km/h | 2.3 mm | Very low 3 |
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
↔
Before · 14 Jun 2026
After · 12 Jul 2026
Sentinel-2 did not pass over on that day. Try another date, or use false colour, which is daily.
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 2 July 2026 the air beside the fire reached 228 µg/m³ of PM2.5. That day averaged 134: 8.9 times the WHO daily guideline (15).
PM2.5 peak228 µg/m³
Days over the guideline11 days
PM10230 µg/m³
Optical depth1.84
WHO 15
19 Jun23 Jun27 Jun1 Jul5 Jul
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 · 971Every 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 time | Satellite | FRP (MW) | Lat | Lon |
|---|
Frequently asked questions
- How long did the Tigilsky District fire last?
- GWIS (Copernicus) dates it between 21 June 2026 and 5 July 2026: 15 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 18,497 hectares (185.0 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Tigilsky District (18,246 ha, 0.3 %).
- What was the weather like?
- During the fire the temperature reached 22.7 °C, humidity dropped to 30 % and gusts hit 49 km/h. The fire danger index (FWI) reached 25, 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 With cross-checks and a citable version
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
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. 971 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.
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.