Seruyan fire, July 2026 Seruyan, Kotawaringin Timur
The fire started on 31 July 2026 in Seruyan, Indonesia, and satellites saw it burning for 87 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 231,721 hectares from heat detections, spread across 2 municipalities.
This page is probably a fire complex, not a single fire. GWIS merges into one perimeter the fires that touch over weeks, which in large burning seasons can join dozens of separate fires. The total area is reliable; the origin and dates refer to the whole complex.
Other fire pages in the same area and on the same dates:
- 71,250 haKotawaringin Timur 3 August 2026 · 84 days
- 38,422 haKotawaringin TimurJuly 2026 · 91 days
- 26,032 haSeruyan 20 September 2026 · 36 days
- 9,337 haSeruyan 20 August 2026 · 38 days
- 7,313 haSeruyan18 August 2026 · 45 days
- 7,010 haSeruyan18 August 2026 · 40 days
- 3,275 haSeruyan 14 September 2026 · 13 days
- 3,040 haSeruyan 19 September 2026 · 37 days
It is the 2th largest in Central Kalimantan since 2016 (of 316 with a page). Number 2 in Indonesia in 2026, of 1009.
Compare with…
Is it still active?
No detections since 25 Oct 2026, 18:34 UTC. That usually means no flame is visible from space any more, although hotspots may remain. 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.
- Burnt area
- 231,721ha
- GWIS perimeter (Copernicus)
- Duration
- 87days
- 31 Jul 2026 – 25 Oct 2026
- Municipalities hit
- 2
- regencies
- Started on
- 31 Jul
- 2026
- Heat detections
- 15,819
- in a single hotspot: 359 MW
- Average daily power
- 1.6GW
- detected power per day, on average
Where it burned
How it evolved, day by day
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
It had gone 4 days without rain (1 mm or more) when it started. Rain came after the fire: 10.9 mm on 26 Oct.
This area had burned before
42% of the perimeter overlaps earlier fires recorded since 2016: 1,734 ha in 2016, 969 ha in 2017, 26,644 ha in 2018, 94,722 ha in 2019, 59,485 ha in 2023, 23 ha in 2024. Part of it burned more than once, so the yearly figures add up to more than the 97,599 ha that had burned before.
- 19,619 ha Kotawaringin Timur fire, August 2019 25,190 ha in total; the hectares shown are those it shares with this fire
- 9,420 ha Kotawaringin Timur fire, September 2019 3,922 ha in total; the hectares shown are those it shares with this fire
- 7,339 ha Kotawaringin Timur fire, September 2018 7,394 ha in total; the hectares shown are those it shares with this fire
- 6,916 ha Kotawaringin Timur fire, August 2018 7,295 ha in total; the hectares shown are those it shares with this fire
- 5,843 ha Kotawaringin Timur fire, September 2023 6,412 ha in total; the hectares shown are those it shares with this fire
- 5,277 ha Kotawaringin Timur fire, August 2023 5,452 ha in total; the hectares shown are those it shares with this fire
- 3,775 ha Seruyan fire, September 2019 3,692 ha in total; the hectares shown are those it shares with this fire
- 2,659 ha Kotawaringin Timur fire, October 2023 2,685 ha in total; the hectares shown are those it shares with this fire
How big is it?
London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).
Jakarta boundary: geoBoundaries · Badan Pusat Statistik (BPS - Statistics Indonesia), World Food Programme, OCHA ROAP (CC BY 3.0 IGO).
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
-
Seruyan where it started172,796 ha reached on 31 Jul10 %
-
59,342 ha reached on 31 Jul3.8 %
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.
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) · forecast models, provisional until the ERA5 reanalysis arrives
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 31 Jul | 32.4 °C | 50 % | 10 km/h | 0.0 mm | fwi. 0 |
| 1 Aug | 32.9 °C | 50 % | 10 km/h | 0.0 mm | fwi. 0 |
| 2 Aug | 32.9 °C | 50 % | 10 km/h | 0.0 mm | fwi. 0 |
| 3 Aug | 33.0 °C | 50 % | 10 km/h | 0.0 mm | fwi. 0 |
| 4 Aug | 33.2 °C | 50 % | 10 km/h | 0.0 mm | fwi. 0 |
| 5 Aug | 32.5 °C | 48 % | 35 km/h | 0.0 mm | fwi. 0 |
| 6 Aug | 32.7 °C | 50 % | 35 km/h | 0.3 mm | fwi. 0 |
| 7 Aug | 31.9 °C | 47 % | 39 km/h | 0.2 mm | fwi. 0 |
| 8 Aug | 32.7 °C | 47 % | 35 km/h | 0.0 mm | fwi. 0 |
| 9 Aug | 31.6 °C | 49 % | 37 km/h | 0.0 mm | fwi. 0 |
| 10 Aug | 32.3 °C | 50 % | 30 km/h | 0.1 mm | fwi. 0 |
| 11 Aug | 32.6 °C | 49 % | 33 km/h | 0.0 mm | fwi. 0 |
| 12 Aug | 32.3 °C | 51 % | 32 km/h | 0.3 mm | fwi. 0 |
| 13 Aug | 32.0 °C | 57 % | 36 km/h | 0.6 mm | fwi. 0 |
| 14 Aug | 31.8 °C | 59 % | 37 km/h | 2.2 mm | fwi. 0 |
| 15 Aug | 32.1 °C | 55 % | 40 km/h | 0.9 mm | fwi. 0 |
| 16 Aug | 32.5 °C | 52 % | 37 km/h | 0.3 mm | fwi. 0 |
| 17 Aug | 33.2 °C | 49 % | 36 km/h | 0.0 mm | fwi. 0 |
| 18 Aug | 33.1 °C | 42 % | 45 km/h | 0.0 mm | fwi. 0 |
| 19 Aug | 33.2 °C | 48 % | 36 km/h | 0.1 mm | fwi. 0 |
| 20 Aug | 33.2 °C | 45 % | 35 km/h | 0.0 mm | fwi. 0 |
| 21 Aug | 33.4 °C | 45 % | 34 km/h | 0.0 mm | fwi. 0 |
| 22 Aug | 33.6 °C | 47 % | 35 km/h | 0.2 mm | fwi. 0 |
| 23 Aug | 32.4 °C | 54 % | 41 km/h | 0.9 mm | fwi. 0 |
| 24 Aug | 31.8 °C | 53 % | 45 km/h | 1.5 mm | fwi. 0 |
| 25 Aug | 32.3 °C | 46 % | 48 km/h | 0.0 mm | fwi. 0 |
| 26 Aug | 32.6 °C | 45 % | 42 km/h | 0.0 mm | fwi. 0 |
| 27 Aug | 32.3 °C | 47 % | 43 km/h | 0.0 mm | fwi. 0 |
| 28 Aug | 32.4 °C | 45 % | 43 km/h | 0.0 mm | fwi. 0 |
| 29 Aug | 33.0 °C | 47 % | 37 km/h | 0.0 mm | fwi. 0 |
| 30 Aug | 33.7 °C | 48 % | 35 km/h | 0.0 mm | fwi. 0 |
| 31 Aug | 32.9 °C | 54 % | 35 km/h | 2.6 mm | fwi. 0 |
| 1 Sept | 32.9 °C | 46 % | 48 km/h | 0.0 mm | fwi. 0 |
| 2 Sept | 32.9 °C | 46 % | 38 km/h | 0.1 mm | fwi. 0 |
| 3 Sept | 32.7 °C | 47 % | 42 km/h | 0.2 mm | fwi. 0 |
| 4 Sept | 32.6 °C | 52 % | 40 km/h | 2.4 mm | fwi. 0 |
| 5 Sept | 32.1 °C | 49 % | 42 km/h | 0.2 mm | fwi. 0 |
| 6 Sept | 33.0 °C | 46 % | 40 km/h | 0.0 mm | fwi. 0 |
| 7 Sept | 31.8 °C | 56 % | 39 km/h | 3.9 mm | fwi. 0 |
| 8 Sept | 31.6 °C | 56 % | 39 km/h | 2.6 mm | fwi. 0 |
| 9 Sept | 32.6 °C | 50 % | 42 km/h | 0.3 mm | fwi. 0 |
| 10 Sept | 32.6 °C | 52 % | 45 km/h | 0.6 mm | fwi. 0 |
| 11 Sept | 33.1 °C | 46 % | 48 km/h | 0.0 mm | fwi. 0 |
| 12 Sept | 33.4 °C | 51 % | 39 km/h | 1.6 mm | fwi. 0 |
| 13 Sept | 32.1 °C | 60 % | 41 km/h | 4.8 mm | fwi. 0 |
| 14 Sept | 32.3 °C | 52 % | 44 km/h | 0.4 mm | fwi. 0 |
| 15 Sept | 33.0 °C | 47 % | 38 km/h | 0.0 mm | fwi. 0 |
| 16 Sept | 32.6 °C | 47 % | 42 km/h | 1.3 mm | fwi. 0 |
| 17 Sept | 32.9 °C | 42 % | 37 km/h | 5.7 mm | fwi. 0 |
| 18 Sept | 33.6 °C | 39 % | 38 km/h | 0.0 mm | fwi. 0 |
| 19 Sept | 34.1 °C | 43 % | 40 km/h | 0.1 mm | fwi. 0 |
| 20 Sept | 34.7 °C | 36 % | 42 km/h | 0.0 mm | fwi. 0 |
| 21 Sept | 34.4 °C | 45 % | 38 km/h | 0.0 mm | fwi. 0 |
| 22 Sept | 35.0 °C | 36 % | 40 km/h | 0.0 mm | fwi. 0 |
| 23 Sept | 34.9 °C | 41 % | 39 km/h | 0.3 mm | fwi. 0 |
| 24 Sept | 34.6 °C | 50 % | 33 km/h | 2.5 mm | fwi. 0 |
| 25 Sept | 33.4 °C | 67 % | 37 km/h | 5.4 mm | fwi. 0 |
| 26 Sept | 34.5 °C | 53 % | 32 km/h | 4.3 mm | fwi. 0 |
| 27 Sept | 33.9 °C | 57 % | 29 km/h | 3.9 mm | fwi. 0 |
| 28 Sept | 34.7 °C | 45 % | 31 km/h | 1.5 mm | fwi. 0 |
| 29 Sept | 35.7 °C | 44 % | 31 km/h | 1.5 mm | fwi. 0 |
| 30 Sept | 33.2 °C | 54 % | 28 km/h | 5.8 mm | fwi. 0 |
| 1 Oct | 34.2 °C | 41 % | 38 km/h | 5.2 mm | fwi. 0 |
| 2 Oct | 33.1 °C | 53 % | 37 km/h | 0.8 mm | fwi. 0 |
| 3 Oct | 33.4 °C | 49 % | 39 km/h | 0.2 mm | fwi. 0 |
| 4 Oct | 33.7 °C | 46 % | 39 km/h | 0.0 mm | fwi. 0 |
| 5 Oct | 34.4 °C | 43 % | 40 km/h | 0.3 mm | fwi. 0 |
| 6 Oct | 33.8 °C | 47 % | 41 km/h | 0.0 mm | fwi. 0 |
| 7 Oct | 34.0 °C | 46 % | 37 km/h | 0.3 mm | fwi. 0 |
| 8 Oct | 34.0 °C | 40 % | 34 km/h | 1.6 mm | fwi. 0 |
| 9 Oct | 33.8 °C | 49 % | 33 km/h | 2.7 mm | fwi. 0 |
| 10 Oct | 33.2 °C | 54 % | 38 km/h | 0.8 mm | fwi. 0 |
| 11 Oct | 34.3 °C | 41 % | 44 km/h | 0.9 mm | fwi. 0 |
| 12 Oct | 34.2 °C | 42 % | 41 km/h | 0.1 mm | fwi. 0 |
| 13 Oct | 34.7 °C | 41 % | 45 km/h | 0.0 mm | fwi. 0 |
| 14 Oct | 34.5 °C | 43 % | 39 km/h | 0.1 mm | fwi. 0 |
| 15 Oct | 33.1 °C | 61 % | 38 km/h | 4.9 mm | fwi. 0 |
| 16 Oct | 33.8 °C | 51 % | 38 km/h | 3.3 mm | fwi. 0 |
| 17 Oct | 33.8 °C | 47 % | 46 km/h | 0.1 mm | fwi. 0 |
| 18 Oct | 34.0 °C | 46 % | 37 km/h | 0.1 mm | fwi. 0 |
| 19 Oct | 33.8 °C | 60 % | 34 km/h | 9.2 mm | fwi. 0 |
| 20 Oct | 35.2 °C | 42 % | 33 km/h | 1.2 mm | fwi. 0 |
| 21 Oct | 34.2 °C | 42 % | 40 km/h | 1.7 mm | fwi. 0 |
| 22 Oct | 33.9 °C | 42 % | 41 km/h | 0.4 mm | fwi. 0 |
| 23 Oct | 33.7 °C | 48 % | 35 km/h | 1.1 mm | fwi. 0 |
| 24 Oct | 33.8 °C | 53 % | 31 km/h | 3.0 mm | fwi. 0 |
| 25 Oct | 34.4 °C | 55 % | 27 km/h | 3.2 mm | fwi. 0 |
| 26 Oct after | 29.9 °C | 79 % | 20 km/h | 10.9 mm | fwi. 0 |
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
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 26 September 2026 the air beside the fire reached 1,002 µg/m³ of PM2.5. That day averaged 422: 28 times the WHO daily guideline (15).
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 · 15,819Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
Frequently asked questions
- How long did the Seruyan fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 31 July 2026 to 25 October 2026 (87 days). The perimeter dates it from 3 August 2026 to 25 October 2026.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 231,721 hectares (2,317.2 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Seruyan (172,796 ha, 10 %); Kotawaringin Timur (59,342 ha, 3.8 %).
- Is the Seruyan fire still active?
- No fire detections since 25 Oct 2026, 18:34 UTC. A lack of detections is not an official extinction.
- What was the weather like?
- During the fire the temperature reached 35.7 °C, humidity dropped to 36 % and gusts hit 48 km/h. The fire danger index (FWI) reached 0, class Very low.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Indonesia (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.
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; 26 polygons grouped in this page.
- Dates adjusted with the VIIRS detections inside the perimeter, which said 3 August 2026 to 25 October 2026. 15,819 Suomi-NPP VIIRS detections on those dates.
- We have not matched this page with any official record.
- Weather: ECMWF IFS model, provisional until the ERA5 reanalysis arrives. No FWI: there are fewer than 30 days of data before the start.
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 (Creative Commons Attribution 3.0 Intergovernmental Organisations (CC BY 3.0 IGO)). 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.