Skip to content
worldfires
ID · Indonesia · →

Seruyan fire, 20 August 2026 Seruyan

Out · last detection 26 Sept 2026, 17:39 UTC

The fire started on 20 August 2026 in Seruyan, Indonesia, and satellites saw it burning for 38 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 9,337 hectares from heat detections, spread across a single municipality.

It is the 42th largest in Central Kalimantan since 2016 (of 310 with a page). Number 107 in Indonesia in 2026, of 988.

Burnt area
9,337ha
GWIS perimeter (Copernicus)
Duration
38days
20 Aug 2026 – 26 Sept 2026
Municipalities hit
1
regencies
Started on
20 Aug
2026
Heat detections
854
in a single hotspot: 113 MW
Danger at start
30
High · FWI index
Energy released
4.5GW
sum of detected power

Where it burned

26 Sept 2026
HOTSPOTS BY DAY 20 Aug26 Sept

How it evolved, day by day

2021232425262728293031123456891112131415171819202122232426

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

The weather it burned in

37°high
33km/h · peak gust
31%lowest humidity

It had gone 42 days without rain (1 mm or more) when it started.

This area had burned before

53% of the perimeter overlaps earlier fires recorded since 2016: 4,473 ha in 2019, 712 ha in 2023.

What happened to each town

  1. Seruyan where it started
    9,402 ha reached on 20 Aug
    0.6 %

Burnt area inside each municipality, from crossing the GWIS perimeter with administrative boundaries. The distance is from the town centre 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) · Copernicus Climate Change Service (ERA5)

Day High Min. humidity Peak gust Rain Danger (FWI)
20 Aug 34.4 °C 43 % 30 km/h 0.0 mm High 30
21 Aug 34.5 °C 41 % 28 km/h 0.0 mm High 30
22 Aug 33.7 °C 48 % 26 km/h 0.0 mm High 27
23 Aug 31.9 °C 57 % 25 km/h 0.0 mm High 22
24 Aug 32.3 °C 53 % 30 km/h 0.0 mm High 24
25 Aug 33.6 °C 45 % 33 km/h 0.0 mm High 26
26 Aug 34.0 °C 43 % 27 km/h 0.0 mm High 26
27 Aug 34.0 °C 39 % 32 km/h 0.0 mm High 30
28 Aug 33.1 °C 40 % 33 km/h 0.0 mm High 30
29 Aug 33.8 °C 44 % 30 km/h 0.0 mm High 29
30 Aug 34.5 °C 44 % 27 km/h 0.0 mm High 28
31 Aug 34.8 °C 41 % 31 km/h 0.0 mm High 30
1 Sept 34.0 °C 42 % 32 km/h 0.0 mm High 30
2 Sept 34.2 °C 40 % 28 km/h 0.0 mm High 29
3 Sept 33.2 °C 46 % 26 km/h 0.0 mm High 28
4 Sept 32.5 °C 53 % 31 km/h 0.0 mm High 27
5 Sept 33.2 °C 44 % 32 km/h 0.0 mm High 28
6 Sept 33.3 °C 47 % 26 km/h 0.0 mm High 26
7 Sept 31.9 °C 57 % 28 km/h 0.0 mm High 24
8 Sept 32.3 °C 56 % 27 km/h 0.0 mm High 24
9 Sept 33.3 °C 48 % 30 km/h 0.0 mm High 25
10 Sept 33.9 °C 47 % 30 km/h 0.0 mm High 26
11 Sept 34.7 °C 43 % 32 km/h 0.0 mm High 28
12 Sept 34.2 °C 45 % 28 km/h 0.0 mm High 27
13 Sept 32.8 °C 56 % 29 km/h 0.2 mm High 25
14 Sept 34.0 °C 43 % 30 km/h 0.0 mm High 28
15 Sept 33.6 °C 46 % 25 km/h 0.0 mm High 26
16 Sept 31.2 °C 55 % 26 km/h 0.0 mm High 24
17 Sept 30.9 °C 55 % 21 km/h 0.0 mm High 22
18 Sept 35.0 °C 37 % 26 km/h 0.0 mm High 29
19 Sept 35.7 °C 36 % 30 km/h 0.0 mm High 32
20 Sept 36.9 °C 31 % 31 km/h 0.0 mm High 36
21 Sept 35.5 °C 40 % 28 km/h 0.0 mm High 35
22 Sept 36.0 °C 34 % 31 km/h 0.0 mm High 36
23 Sept 35.3 °C 41 % 31 km/h 0.0 mm High 35
24 Sept 36.3 °C 40 % 31 km/h 0.0 mm High 34
25 Sept 32.3 °C 65 % 25 km/h 3.5 mm Low 6
26 Sept 34.5 °C 53 % 31 km/h 1.8 mm Low 10
27 Sept after 33.3 °C 59 % 22 km/h 17.0 mm Very low 2
28 Sept after 33.8 °C 49 % 21 km/h 0.0 mm Low 9
29 Sept after 34.6 °C 47 % 31 km/h 3.3 mm Low 6
30 Sept after 33.5 °C 59 % 25 km/h 2.7 mm Very low 4
1 Oct after 34.5 °C 38 % 25 km/h 0.5 mm Moderate 15
2 Oct after 35.3 °C 40 % 30 km/h 0.0 mm Moderate 19
3 Oct after 34.9 °C 44 % 27 km/h 0.0 mm Moderate 19
4 Oct after 34.9 °C 43 % 25 km/h 0.0 mm Moderate 19
5 Oct after 35.4 °C 40 % 29 km/h 0.0 mm Moderate 21

Before and after, from space

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

Before · 13 Aug 2026
After · 3 Oct 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 21 September 2026 the air beside the fire reached 510 µg/m³ of PM2.5. That day averaged 319: 21 times the WHO daily guideline (15).

PM2.5 peak510 µg/m³
Days over the guideline36 days
PM10529 µg/m³
Optical depth8.41
252627282930311234567891011121314151617181920212223242526272829
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 · 854Every 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

Other fires nearby

All fires in Indonesia ›

Frequently asked questions

How long did the Seruyan fire last?
According to the heat detections seen by satellite inside the perimeter, it burned from 20 August 2026 to 26 September 2026 (38 days). The perimeter dates it from 27 August 2026 to 26 September 2026.
How much area did it burn?
The perimeter GWIS (Copernicus) rebuilt from heat detections is 9,337 hectares (93.4 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Seruyan (9,402 ha, 0.6 %).
Is the Seruyan fire still active?
No fire detections since 26 Sept 2026, 17:39 UTC. A lack of detections is not an official extinction.
What was the weather like?
During the fire the temperature reached 36.9 °C, humidity dropped to 31 % and gusts hit 33 km/h. The fire danger index (FWI) reached 36, class High.
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

Satellite cross-check

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.

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.