Burned area
satellite only24,232ha
Perimeter published by GWIS (Copernicus).
- Source
- GWIS (Copernicus)
- Date
- 19 Jul 2026 – 30 Aug 2026
+− cross-check
No official record is matched to this page to compare it with.
RU · Russia · –
Evenkiysky Rayon fire, 19 July 2026 Evenkiysky Rayon
Out · last detection 30 Aug 2026, 19:06 UTC
The fire started on 19 July 2026 in Evenkiysky Rayon, Russia, and satellites saw it burning for 43 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 24,232 hectares from heat detections, spread across a single municipality.
Number 43 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 only43days
19 Jul 2026 to 30 Aug 2026: first and last day with fire on the page.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- last detection: 30 Aug 2026, 19:06 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 only19 Jul 2026
First day with fire seen by the satellites or the perimeter.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- 19 Jul 2026
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
Hotspots
satellite only5,200
VIIRS detections at 375 m. Most intense hotspot: 632 MW.
- Source
- NASA FIRMS · VIIRS (Suomi NPP + NOAA-20)
- Date
- 19 Jul 2026 – 30 Aug 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 only18,253MW
Total radiative power on 2 August 2026; hotspots that day: 468.
- Source
- NASA FIRMS · VIIRS (FRP)
- Date
- 2 Aug 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
model17.8FWI · moderate
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 7.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 19 Jul 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
model34.5°C · 20% RH
High of 34.5 °C and minimum humidity of 20% on 31 July 2026; gusts of 52 km/h on 21 July 2026.
- Source
- weather model at the fire’s grid cell
- Date
- 19 Jul 2026 – 30 Aug 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 weatherWeather and FWI computed from the ERA5 reanalysis
-
· reconstructed GHSLPopulation and built-up area computed
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
- 24,232 ha
- Dates
- 19 Jul 2026 – 30 Aug 2026
- Name
- Evenkiysky Rayon
- Official record
- —
Versioned permanent link
https://worldfires.org/en/fire/evenkiysky-rayon-2026-07-2?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 evenkiysky-rayon-2026-07-2.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-07-19 | 1 | 2 | 25.2 | 14.4 | 38 | 14.3 | 28.4 | 0 | 17.8 | moderado | 1 |
| 2026-07-20 | 0 | 0 | 23.3 | 14.3 | 48 | 16 | 39.6 | 0 | 24.1 | alto | 1 |
| 2026-07-21 | 17 | 49 | 25.4 | 13.2 | 32 | 20 | 52.2 | 0 | 34.6 | alto | 1 |
| 2026-07-22 | 102 | 606 | 28.2 | 11.8 | 20 | 13.3 | 37.8 | 0 | 39 | muy_alto | 1 |
| 2026-07-23 | 166 | 1,054 | 29.1 | 11.9 | 25 | 7.2 | 24.1 | 0 | 32.2 | alto | 1 |
| 2026-07-24 | 106 | 429 | 29.6 | 14.5 | 27 | 12.3 | 31.3 | 0 | 35.9 | alto | 1 |
| 2026-07-25 | 79 | 707 | 28.5 | 15 | 35 | 12.7 | 34.6 | 0.1 | 36.8 | alto | 1 |
| 2026-07-26 | 74 | 166 | 28.9 | 15.8 | 23 | 12.3 | 31.7 | 0 | 37.7 | alto | 1 |
| 2026-07-27 | 186 | 1,310 | 31.3 | 13.5 | 17 | 9.5 | 27.4 | 0 | 43.2 | muy_alto | 1 |
| 2026-07-28 | 303 | 4,199 | 32.9 | 13.7 | 19 | 11.4 | 31.3 | 0 | 45.4 | muy_alto | 1 |
| 2026-07-29 | 340 | 4,528 | 32.6 | 14.5 | 18 | 13.2 | 35.6 | 0 | 51.7 | extremo | 1 |
| 2026-07-30 | 223 | 2,308 | 34.1 | 16.5 | 18 | 9.1 | 23 | 0 | 41.5 | muy_alto | 1 |
| 2026-07-31 | 100 | 245 | 34.5 | 15.3 | 20 | 6.8 | 17.3 | 0 | 37.4 | alto | 1 |
| 2026-08-01 | 193 | 699 | 32.6 | 15.4 | 25 | 5.5 | 16.6 | 0 | 37.1 | alto | 1 |
| 2026-08-02 | 468 | 18,253 | 31.9 | 16.2 | 24 | 16.8 | 41.4 | 0.6 | 52.8 | extremo | 1 |
| 2026-08-03 | 20 | 76 | 21.1 | 10.9 | 31 | 14.4 | 34.9 | 0 | 34.9 | alto | 1 |
| 2026-08-04 | 13 | 27 | 21.3 | 7.6 | 26 | 8.6 | 25.6 | 0 | 30 | alto | 1 |
| 2026-08-05 | 129 | 508 | 24.6 | 6.7 | 21 | 7.5 | 23 | 0 | 32 | alto | 1 |
| 2026-08-06 | 286 | 2,736 | 26.6 | 9.2 | 23 | 17.8 | 45.7 | 0 | 48.6 | muy_alto | 1 |
| 2026-08-07 | 112 | 163 | 24.1 | 14.9 | 46 | 11.8 | 33.5 | 0.7 | 29.9 | alto | 1 |
| 2026-08-08 | 93 | 137 | 26.5 | 15.3 | 38 | 14.1 | 30.2 | 0 | 27 | alto | 1 |
| 2026-08-09 | 2 | 10 | 21 | 12.3 | 36 | 14.1 | 40 | 0 | 35 | alto | 1 |
| 2026-08-10 | 68 | 128 | 21.4 | 11.9 | 38 | 9.3 | 24.8 | 0.1 | 27 | alto | 1 |
| 2026-08-11 | 82 | 166 | 21.1 | 12.3 | 33 | 12.9 | 34.6 | 0 | 32.7 | alto | 1 |
| 2026-08-12 | 8 | 47 | 19.7 | 8.6 | 34 | 7.7 | 22.3 | 0 | 26.4 | alto | 1 |
| 2026-08-13 | 26 | 29 | 19.3 | 10.9 | 37 | 12.1 | 29.9 | 0 | 31.7 | alto | 1 |
| 2026-08-14 | 7 | 11 | 17.8 | 7.8 | 55 | 8.5 | 28.1 | 1.3 | 23.3 | alto | 1 |
| 2026-08-15 | 6 | 11 | 17.7 | 7.6 | 44 | 11.2 | 32.8 | 0 | 14.8 | moderado | 1 |
| 2026-08-16 | 25 | 56 | 20 | 8.4 | 40 | 11.1 | 32.4 | 0 | 22.1 | alto | 1 |
| 2026-08-17 | 71 | 113 | 23.2 | 8.3 | 36 | 9.9 | 23.8 | 0 | 26.7 | alto | 1 |
| 2026-08-18 | 75 | 179 | 20.4 | 7 | 47 | 10 | 31.7 | 0.1 | 24 | alto | 1 |
| 2026-08-19 | 78 | 177 | 20 | 7.7 | 32 | 9.1 | 27 | 0 | 23.9 | alto | 1 |
| 2026-08-20 | 107 | 264 | 21 | 4.1 | 29 | 6.9 | 21.2 | 0 | 27.9 | alto | 1 |
| 2026-08-21 | 110 | 303 | 22.3 | 5.3 | 27 | 4.7 | 15.5 | 0 | 25.5 | alto | 1 |
| 2026-08-22 | 178 | 450 | 22.5 | 4.5 | 29 | 8.9 | 21.6 | 0 | 31 | alto | 1 |
| 2026-08-23 | 349 | 1,088 | 20.7 | 5.5 | 29 | 9.4 | 29.2 | 0 | 32.7 | alto | 1 |
| 2026-08-24 | 190 | 426 | 22.3 | 4.8 | 31 | 7.9 | 22.3 | 0 | 28.2 | alto | 1 |
| 2026-08-25 | 188 | 390 | 23.3 | 6.6 | 29 | 7.6 | 11.5 | 0 | 24.3 | alto | 1 |
| 2026-08-26 | 237 | 783 | 23.2 | 5.5 | 31 | 8.1 | 24.8 | 0 | 30.5 | alto | 1 |
| 2026-08-27 | 173 | 321 | 22.2 | 5.3 | 33 | 6.2 | 11.5 | 0 | 25.1 | alto | 1 |
| 2026-08-28 | 68 | 88 | 20.3 | 4.4 | 34 | 8.1 | 25.6 | 0 | 31.4 | alto | 1 |
| 2026-08-29 | 121 | 192 | 21.3 | 6.2 | 46 | 8.8 | 23.8 | 0 | 25.7 | alto | 1 |
| 2026-08-30 | 20 | 69 | 20.5 | 9.4 | 54 | 12.7 | 35.6 | 1 | 29.9 | alto | 1 |
| 2026-08-31 | 0 | 0 | 24.5 | 12.3 | 42 | 14.2 | 36.7 | 0.1 | 20.7 | moderado | 0 |
| 2026-09-01 | 0 | 0 | 21.5 | 14.5 | 52 | 12.8 | 40.3 | 2.3 | 23 | alto | 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
- 24,232ha
- GWIS perimeter (Copernicus)
- Duration
- 43days
- 19 Jul 2026 – 30 Aug 2026
- Municipalities hit
- 1
- districts
- Started on
- 19 Jul
- 2026
- Heat detections
- 5,200
- in a single hotspot: 632 MW
- Danger at start
- 18
- Moderate · FWI index
- Average daily power
- 1.0GW
- detected power per day, on average
Where it burned
HOTSPOTS BY DAY
19 Jul30 Aug
30 Aug 2026
How it evolved, day by day
19 Jul
2 Aug
16 Aug
25 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
34°high
52km/h · peak gust
17%lowest humidity
It had gone 7 days without rain (1 mm or more) when it started. Rain came after the fire: 2.3 mm on 1 Sept.
This area had burned before
0% of the perimeter overlaps earlier fires recorded since 2016: 33 ha in 2019.
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
-
Evenkiysky Rayon where it started23,433 ha reached on 19 Jul0.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 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) |
|---|---|---|---|---|---|
| 19 Jul | 25.2 °C | 38 % | 28 km/h | 0.0 mm | Moderate 18 |
| 20 Jul | 23.3 °C | 48 % | 40 km/h | 0.0 mm | High 24 |
| 21 Jul | 25.4 °C | 32 % | 52 km/h | 0.0 mm | High 35 |
| 22 Jul | 28.2 °C | 20 % | 38 km/h | 0.0 mm | Very high 39 |
| 23 Jul | 29.1 °C | 25 % | 24 km/h | 0.0 mm | High 32 |
| 24 Jul | 29.6 °C | 27 % | 31 km/h | 0.0 mm | High 36 |
| 25 Jul | 28.5 °C | 35 % | 35 km/h | 0.1 mm | High 37 |
| 26 Jul | 28.9 °C | 23 % | 32 km/h | 0.0 mm | High 38 |
| 27 Jul | 31.3 °C | 17 % | 27 km/h | 0.0 mm | Very high 43 |
| 28 Jul | 32.9 °C | 19 % | 31 km/h | 0.0 mm | Very high 45 |
| 29 Jul | 32.6 °C | 18 % | 36 km/h | 0.0 mm | Extreme 52 |
| 30 Jul | 34.1 °C | 18 % | 23 km/h | 0.0 mm | Very high 42 |
| 31 Jul | 34.5 °C | 20 % | 17 km/h | 0.0 mm | High 37 |
| 1 Aug | 32.6 °C | 25 % | 17 km/h | 0.0 mm | High 37 |
| 2 Aug | 31.9 °C | 24 % | 41 km/h | 0.6 mm | Extreme 53 |
| 3 Aug | 21.1 °C | 31 % | 35 km/h | 0.0 mm | High 35 |
| 4 Aug | 21.3 °C | 26 % | 26 km/h | 0.0 mm | High 30 |
| 5 Aug | 24.6 °C | 21 % | 23 km/h | 0.0 mm | High 32 |
| 6 Aug | 26.6 °C | 23 % | 46 km/h | 0.0 mm | Very high 49 |
| 7 Aug | 24.1 °C | 46 % | 34 km/h | 0.7 mm | High 30 |
| 8 Aug | 26.5 °C | 38 % | 30 km/h | 0.0 mm | High 27 |
| 9 Aug | 21.0 °C | 36 % | 40 km/h | 0.0 mm | High 35 |
| 10 Aug | 21.4 °C | 38 % | 25 km/h | 0.1 mm | High 27 |
| 11 Aug | 21.1 °C | 33 % | 35 km/h | 0.0 mm | High 33 |
| 12 Aug | 19.7 °C | 34 % | 22 km/h | 0.0 mm | High 26 |
| 13 Aug | 19.3 °C | 37 % | 30 km/h | 0.0 mm | High 32 |
| 14 Aug | 17.8 °C | 55 % | 28 km/h | 1.3 mm | High 23 |
| 15 Aug | 17.7 °C | 44 % | 33 km/h | 0.0 mm | Moderate 15 |
| 16 Aug | 20.0 °C | 40 % | 32 km/h | 0.0 mm | High 22 |
| 17 Aug | 23.2 °C | 36 % | 24 km/h | 0.0 mm | High 27 |
| 18 Aug | 20.4 °C | 47 % | 32 km/h | 0.1 mm | High 24 |
| 19 Aug | 20.0 °C | 32 % | 27 km/h | 0.0 mm | High 24 |
| 20 Aug | 21.0 °C | 29 % | 21 km/h | 0.0 mm | High 28 |
| 21 Aug | 22.3 °C | 27 % | 16 km/h | 0.0 mm | High 26 |
| 22 Aug | 22.5 °C | 29 % | 22 km/h | 0.0 mm | High 31 |
| 23 Aug | 20.7 °C | 29 % | 29 km/h | 0.0 mm | High 33 |
| 24 Aug | 22.3 °C | 31 % | 22 km/h | 0.0 mm | High 28 |
| 25 Aug | 23.3 °C | 29 % | 12 km/h | 0.0 mm | High 24 |
| 26 Aug | 23.2 °C | 31 % | 25 km/h | 0.0 mm | High 30 |
| 27 Aug | 22.2 °C | 33 % | 12 km/h | 0.0 mm | High 25 |
| 28 Aug | 20.3 °C | 34 % | 26 km/h | 0.0 mm | High 31 |
| 29 Aug | 21.3 °C | 46 % | 24 km/h | 0.0 mm | High 26 |
| 30 Aug | 20.5 °C | 54 % | 36 km/h | 1.0 mm | High 30 |
| 31 Aug after | 24.5 °C | 42 % | 37 km/h | 0.1 mm | Moderate 21 |
| 1 Sept after | 21.5 °C | 52 % | 40 km/h | 2.3 mm | High 23 |
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
↔
Before · 12 Jul 2026
After · 6 Sept 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 25 August 2026 the air beside the fire reached 3,256 µg/m³ of PM2.5. That day averaged 1,933: 129 times the WHO daily guideline (15).
PM2.5 peak3,256 µg/m³
Days over the guideline41 days
PM103,092 µg/m³
Optical depth4.47
WHO 15
17 Jul27 Jul6 Aug16 Aug26 Aug
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 · 5,200Every 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 |
|---|
Other fires nearby
- 4,954 haEvenkiysky Rayon5 August 2019 · 17 days · 13 km away
- 4,881 haEvenkiysky Rayon23 July 2021 · 20 days · 19 km away
- 4,050 haEvenkiysky Rayon15 July 2019 · 12 days · 19 km away
- 7,696 haEvenkiysky Rayon5 August 2026 · 26 days · 25 km away
- 9,173 haEvenkiysky Rayon5 August 2017 · 18 days · 26 km away
- 19,450 haEvenkiysky Rayon3 August 2017 · 20 days · 35 km away
Frequently asked questions
- How long did the Evenkiysky Rayon fire last?
- GWIS (Copernicus) dates it between 19 July 2026 and 30 August 2026: 43 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 24,232 hectares (242.3 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Evenkiysky Rayon (23,433 ha, 0.0 %).
- What was the weather like?
- During the fire the temperature reached 34.5 °C, humidity dropped to 17 % and gusts hit 52 km/h. The fire danger index (FWI) reached 53, class Extreme.
- 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. 5,200 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.