Burned area
satellite only12,973ha
Perimeter published by GWIS (Copernicus).
- Source
- GWIS (Copernicus)
- Date
- 31 Jul 2026 – 2 Aug 2026
+− cross-check
No official record is matched to this page to compare it with.
KZ · Kazakhstan · –
Dzhangil`dinskiy fire, 31 July 2026 Жангелді ауданы · Dzhangil`dinskiy
Out · last detection 2 Aug 2026, 09:05 UTC
The fire started on 31 July 2026 in Dzhangil`dinskiy, Kazakhstan, and satellites saw it burning for 3 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 12,973 hectares from heat detections, spread across a single municipality.
Number 5 in Kazakhstan in 2026, of 52.
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-11-05matches 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 only3days
31 Jul 2026 to 2 Aug 2026: first and last day with fire on the page.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- last detection: 2 Aug 2026, 09:05 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 only31 Jul 2026
First day with fire seen by the satellites or the perimeter.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- 31 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 only334
VIIRS detections at 375 m. Most intense hotspot: 91 MW.
- Source
- NASA FIRMS · VIIRS (Suomi NPP)
- Date
- 31 Jul 2026 – 2 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 only3,715MW
Total radiative power on 1 August 2026; hotspots that day: 299.
- Source
- NASA FIRMS · VIIRS (FRP)
- Date
- 1 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
model66.3FWI · extreme
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 9.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 31 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
model39.1°C · 18% RH
High of 39.1 °C and minimum humidity of 18% on 31 July 2026; gusts of 51 km/h on 31 July 2026.
- Source
- weather model at the fire’s grid cell
- Date
- 31 Jul 2026 – 2 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
-
logStart date: 1 August 2026 → 31 July 2026.
-
· reconstructed weatherWeather and FWI computed from the ERA5 reanalysis
-
logStart date: 31 July 2026 → 1 August 2026.
-
logStart date: 1 August 2026 → 31 July 2026.
-
· reconstructed GHSLPopulation and built-up area computed
Area logged each night
Move the slider to see which area the page published each day.
Versioned permanent link
https://worldfires.org/en/fire/dzhangil-dinskiy-2026-08?v=2026-11-05A 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 dzhangil-dinskiy-2026-08.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-31 | 5 | 7 | 39.1 | 23.9 | 18 | 30.3 | 50.8 | 0.4 | 66.3 | extremo | 1 |
| 2026-08-01 | 299 | 3,715 | 34.1 | 17.8 | 17 | 25.2 | 41.4 | 0 | 63.7 | extremo | 1 |
| 2026-08-02 | 30 | 175 | 30.3 | 18.2 | 25 | 26.9 | 45.7 | 0 | 63.7 | extremo | 1 |
| 2026-08-03 | 0 | 0 | 28.6 | 16.9 | 32 | 16.2 | 31.7 | 0.6 | 41.4 | muy_alto | 0 |
| 2026-08-04 | 0 | 0 | 31.5 | 17.1 | 30 | 26.1 | 40.3 | 0.1 | 44.3 | muy_alto | 0 |
| 2026-08-05 | 0 | 0 | 31.7 | 18.4 | 25 | 20.2 | 37.8 | 0 | 43.7 | muy_alto | 0 |
| 2026-08-06 | 0 | 0 | 32 | 19.2 | 26 | 14.9 | 29.9 | 0 | 39.8 | muy_alto | 0 |
| 2026-08-07 | 0 | 0 | 31.1 | 19.2 | 27 | 18.6 | 33.1 | 0 | 41.1 | muy_alto | 0 |
| 2026-08-08 | 0 | 0 | 33 | 15.9 | 18 | 13 | 27 | 0 | 43.5 | muy_alto | 0 |
| 2026-08-09 | 0 | 0 | 38.5 | 18.3 | 15 | 14.2 | 26.3 | 0 | 52.7 | extremo | 0 |
| 2026-08-10 | 0 | 0 | 40.1 | 21.8 | 14 | 16.1 | 30.2 | 0 | 62.3 | extremo | 0 |
| 2026-08-11 | 0 | 0 | 29.7 | 21.4 | 21 | 27.8 | 47.2 | 0 | 64.1 | extremo | 0 |
| 2026-08-12 | 0 | 0 | 28.5 | 15.3 | 28 | 20.1 | 31.3 | 0 | 36.2 | 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
- 12,973ha
- GWIS perimeter (Copernicus)
- Duration
- 3days
- 31 Jul 2026 – 2 Aug 2026
- Municipalities hit
- 1
- districts
- Started on
- 31 Jul
- 2026
- Heat detections
- 334
- in a single hotspot: 91 MW
- Danger at start
- 66
- Extreme · FWI index
- Average daily power
- 1.3GW
- detected power per day, on average
Where it burned
HOTSPOTS BY DAY
31 Jul2 Aug
2 Aug 2026
How it evolved, day by day
31 Jul
1 Aug
2 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
39°high
51km/h · peak gust
17%lowest humidity
It had gone 9 days without rain (1 mm or more) when it started.
This area had burned before
23% of the perimeter overlaps earlier fires recorded since 2016: 1,166 ha in 2018, 1,814 ha in 2021.
How big is it?
London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.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).
Berlin boundary: geoBoundaries · Federal Agency for Cartography and Geodesy (dl-de/by-2-0).
This compares size, not location: both shapes are at the same scale, north up, centred on each other.
What happened to each town
-
13,156 ha reached on 31 Jul0.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)
Started with Extreme FWI: 45 % of the area in Kazakhstan Strong wind: 19 % of the area in Kazakhstan
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 31 Jul | 39.1 °C | 18 % | 51 km/h | 0.4 mm | Extreme 66 |
| 1 Aug | 34.1 °C | 17 % | 41 km/h | 0.0 mm | Extreme 64 |
| 2 Aug | 30.3 °C | 25 % | 46 km/h | 0.0 mm | Extreme 64 |
| 3 Aug after | 28.6 °C | 32 % | 32 km/h | 0.6 mm | Very high 41 |
| 4 Aug after | 31.5 °C | 30 % | 40 km/h | 0.1 mm | Very high 44 |
| 5 Aug after | 31.7 °C | 25 % | 38 km/h | 0.0 mm | Very high 44 |
| 6 Aug after | 32.0 °C | 26 % | 30 km/h | 0.0 mm | Very high 40 |
| 7 Aug after | 31.1 °C | 27 % | 33 km/h | 0.0 mm | Very high 41 |
| 8 Aug after | 33.0 °C | 18 % | 27 km/h | 0.0 mm | Very high 44 |
| 9 Aug after | 38.5 °C | 15 % | 26 km/h | 0.0 mm | Extreme 53 |
| 10 Aug after | 40.1 °C | 14 % | 30 km/h | 0.0 mm | Extreme 62 |
| 11 Aug after | 29.7 °C | 21 % | 47 km/h | 0.0 mm | Extreme 64 |
| 12 Aug after | 28.5 °C | 28 % | 31 km/h | 0.0 mm | High 36 |
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
↔
Before · 24 Jul 2026
After · 9 Aug 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 5 August 2026 the air beside the fire reached 19 µg/m³ of PM2.5, but no daily average passed the WHO guideline (15).
PM2.5 peak19 µg/m³
Days over the guideline0 days
PM1019 µg/m³
Optical depth0.51
WHO 15
30 Jul1 Aug3 Aug5 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 · 334Every 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,331 haDzhangil`dinskiy Жангелді ауданы11 July 2018 · 2 days · 16 km away
- 7,154 haDzhangil`dinskiy Жангелді ауданы20 June 2021 · 3 days · 20 km away
- 6,287 haDzhangil`dinskiy Жангелді ауданы22 June 2021 · 3 days · 21 km away
- 9,856 haDzhangil`dinskiy Жангелді ауданы1 August 2026 · 2 days · 27 km away
- 3,792 haDzhangil`dinskiy Жангелді ауданы11 July 2018 · 2 days · 29 km away
- 5,929 haDzhangil`dinskiy Жангелді ауданы20 June 2021 · 1 day · 36 km away
Frequently asked questions
- How long did the Dzhangil`dinskiy fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 31 July 2026 to 2 August 2026 (3 days). The perimeter dates it from 1 August 2026 to 2 August 2026.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 12,973 hectares (129.7 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Dzhangil`dinskiy (13,156 ha, 0.3 %).
- What was the weather like?
- During the fire the temperature reached 39.1 °C, humidity dropped to 17 % and gusts hit 51 km/h. The fire danger index (FWI) reached 66, class Extreme.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Kazakhstan (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 · 3 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
- Start date: 1 August 2026 → 31 July 2026.
- Start date: 31 July 2026 → 1 August 2026.
- Start date: 1 August 2026 → 31 July 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 adjusted with the VIIRS detections inside the perimeter, which said 1 August 2026 to 2 August 2026. 334 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.