Burned area
satellite only2,913ha
Perimeter published by GWIS (Copernicus).
- Source
- GWIS (Copernicus)
- Date
- 14 Aug 2026 – 25 Aug 2026
+− cross-check
No official record is matched to this page to compare it with.
ID · Indonesia · –
Kupang fire, 14 August 2026 Kupang
Out · last detection 25 Aug 2026, 04:53 UTC
The fire started on 14 August 2026 in Kupang, Indonesia, and satellites saw it burning for 12 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 2,913 hectares from heat detections, spread across a single municipality.
Number 371 in Indonesia in 2026, of 967.
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…
Suggestions: Kupang · 2024Kupang · 2023Kupang · 2023Kupang · 2020
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 only12days
14 Aug 2026 to 25 Aug 2026: first and last day with fire on the page.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- last detection: 25 Aug 2026, 04:53 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 only14 Aug 2026
First day with fire seen by the satellites or the perimeter.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- 14 Aug 2026
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
Hotspots
satellite only54
VIIRS detections at 375 m. Most intense hotspot: 36 MW.
- Source
- NASA FIRMS · VIIRS (Suomi NPP)
- Date
- 14 Aug 2026 – 25 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 only132MW
Total radiative power on 23 August 2026; hotspots that day: 14.
- Source
- NASA FIRMS · VIIRS (FRP)
- Date
- 23 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
model28.2FWI · high
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 36.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 14 Aug 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
model33.2°C · 26% RH
High of 33.2 °C and minimum humidity of 26% on 22 August 2026; gusts of 49 km/h on 25 August 2026.
- Source
- weather model at the fire’s grid cell
- Date
- 14 Aug 2026 – 25 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 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
- 2,913 ha
- Dates
- 14 Aug 2026 – 25 Aug 2026
- Name
- Kupang
- Official record
- —
Versioned permanent link
https://worldfires.org/en/fire/kupang-2026-08-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 kupang-2026-08-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-08-14 | 2 | 7 | 31.8 | 19.1 | 39 | 15.2 | 34.6 | 0 | 28.2 | alto | 1 |
| 2026-08-15 | 1 | 4 | 31.4 | 18.5 | 40 | 15.9 | 35.6 | 0 | 29 | alto | 1 |
| 2026-08-16 | 0 | 0 | 30.9 | 18.2 | 41 | 14.9 | 32 | 0 | 28.6 | alto | 1 |
| 2026-08-17 | 0 | 0 | 30 | 17.6 | 45 | 13.8 | 31 | 0 | 27.2 | alto | 1 |
| 2026-08-18 | 6 | 29 | 32.3 | 16.9 | 28 | 9.6 | 26.6 | 0 | 28.8 | alto | 1 |
| 2026-08-19 | 13 | 91 | 31.9 | 17.5 | 30 | 16.6 | 36.4 | 0 | 34.6 | alto | 1 |
| 2026-08-20 | 2 | 7 | 30.6 | 17.1 | 37 | 13.4 | 31.3 | 0 | 31.7 | alto | 1 |
| 2026-08-21 | 1 | 2 | 31.1 | 17.3 | 37 | 14 | 30.2 | 0 | 32.4 | alto | 1 |
| 2026-08-22 | 12 | 71 | 33.2 | 17.5 | 26 | 19.5 | 42.5 | 0 | 40.1 | muy_alto | 1 |
| 2026-08-23 | 14 | 132 | 30.8 | 17.5 | 41 | 15.5 | 33.1 | 0 | 32.3 | alto | 1 |
| 2026-08-24 | 0 | 0 | 31 | 16.5 | 40 | 16.3 | 34.6 | 0 | 33.1 | alto | 1 |
| 2026-08-25 | 3 | 8 | 32.3 | 16.5 | 33 | 22.9 | 49.3 | 0 | 39.2 | muy_alto | 1 |
| 2026-08-26 | 0 | 0 | 31.6 | 17.1 | 34 | 14.4 | 32.4 | 0 | 32.1 | alto | 0 |
| 2026-08-27 | 0 | 0 | 31.1 | 17.6 | 36 | 14.1 | 38.2 | 0 | 32.2 | alto | 0 |
| 2026-08-28 | 0 | 0 | 32.3 | 19.5 | 34 | 15.3 | 32.8 | 0 | 33.4 | alto | 0 |
| 2026-08-29 | 0 | 0 | 33 | 18.6 | 31 | 15.1 | 31.7 | 0 | 33.9 | alto | 0 |
| 2026-08-30 | 0 | 0 | 34 | 19.1 | 26 | 15.9 | 35.3 | 0 | 38.3 | muy_alto | 0 |
| 2026-08-31 | 0 | 0 | 32.5 | 19 | 32 | 26.6 | 57.6 | 0 | 49.6 | muy_alto | 0 |
| 2026-09-01 | 0 | 0 | 32.8 | 18.7 | 31 | 26.9 | 57.6 | 0 | 50.2 | extremo | 0 |
| 2026-09-02 | 0 | 0 | 32.5 | 17.1 | 24 | 14.8 | 32.8 | 0 | 38.3 | muy_alto | 0 |
| 2026-09-03 | 0 | 0 | 32.8 | 17.7 | 27 | 18.4 | 38.2 | 0 | 42 | muy_alto | 0 |
| 2026-09-04 | 0 | 0 | 31 | 17.2 | 40 | 18.3 | 38.9 | 0 | 36.6 | alto | 0 |
| 2026-09-05 | 0 | 0 | 31 | 19.5 | 40 | 17.4 | 37.8 | 0 | 35.3 | alto | 0 |
| 2026-09-06 | 0 | 0 | 31 | 18.8 | 48 | 16.9 | 36.7 | 0.5 | 31 | alto | 0 |
| 2026-09-07 | 0 | 0 | 32.2 | 20.2 | 42 | 15.6 | 36.7 | 0 | 30.2 | alto | 0 |
| 2026-09-08 | 0 | 0 | 31 | 19.1 | 47 | 11.7 | 28.1 | 0 | 27.3 | alto | 0 |
| 2026-09-09 | 0 | 0 | 32.3 | 21 | 38 | 23.3 | 49.7 | 0 | 37 | alto | 0 |
| 2026-09-10 | 0 | 0 | 33.2 | 20.2 | 36 | 10.5 | 28.1 | 0 | 28.3 | alto | 0 |
| 2026-09-11 | 0 | 0 | 35.5 | 19 | 25 | 11.4 | 26.3 | 0 | 36.1 | 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
- 2,913ha
- GWIS perimeter (Copernicus)
- Duration
- 12days
- 14 Aug 2026 – 25 Aug 2026
- Municipalities hit
- 1
- regencies
- Started on
- 14 Aug
- 2026
- Heat detections
- 54
- in a single hotspot: 36 MW
- Danger at start
- 28
- High · FWI index
- Average daily power
- 39MW
- detected power per day, on average
Where it burned
HOTSPOTS BY DAY
14 Aug25 Aug
25 Aug 2026
How it evolved, day by day
14 Aug
18 Aug
20 Aug
23 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
58km/h · peak gust
26%lowest humidity
It had gone 36 days without rain (1 mm or more) when it started.
This area had burned before
74% of the perimeter overlaps earlier fires recorded since 2016: 757 ha in 2017, 6 ha in 2018, 158 ha in 2021, 1,082 ha in 2023, 556 ha in 2024, 1,400 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 2,164 ha that had burned before.
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
-
Kupang where it started2,933 ha reached on 14 Aug0.6 %
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) |
|---|---|---|---|---|---|
| 14 Aug | 31.8 °C | 39 % | 35 km/h | 0.0 mm | High 28 |
| 15 Aug | 31.4 °C | 40 % | 36 km/h | 0.0 mm | High 29 |
| 16 Aug | 30.9 °C | 41 % | 32 km/h | 0.0 mm | High 29 |
| 17 Aug | 30.0 °C | 45 % | 31 km/h | 0.0 mm | High 27 |
| 18 Aug | 32.3 °C | 28 % | 27 km/h | 0.0 mm | High 29 |
| 19 Aug | 31.9 °C | 30 % | 36 km/h | 0.0 mm | High 35 |
| 20 Aug | 30.6 °C | 37 % | 31 km/h | 0.0 mm | High 32 |
| 21 Aug | 31.1 °C | 37 % | 30 km/h | 0.0 mm | High 32 |
| 22 Aug | 33.2 °C | 26 % | 42 km/h | 0.0 mm | Very high 40 |
| 23 Aug | 30.8 °C | 41 % | 33 km/h | 0.0 mm | High 32 |
| 24 Aug | 31.0 °C | 40 % | 35 km/h | 0.0 mm | High 33 |
| 25 Aug | 32.3 °C | 33 % | 49 km/h | 0.0 mm | Very high 39 |
| 26 Aug after | 31.6 °C | 34 % | 32 km/h | 0.0 mm | High 32 |
| 27 Aug after | 31.1 °C | 36 % | 38 km/h | 0.0 mm | High 32 |
| 28 Aug after | 32.3 °C | 34 % | 33 km/h | 0.0 mm | High 33 |
| 29 Aug after | 33.0 °C | 31 % | 32 km/h | 0.0 mm | High 34 |
| 30 Aug after | 34.0 °C | 26 % | 35 km/h | 0.0 mm | Very high 38 |
| 31 Aug after | 32.5 °C | 32 % | 58 km/h | 0.0 mm | Very high 50 |
| 1 Sept after | 32.8 °C | 31 % | 58 km/h | 0.0 mm | Extreme 50 |
| 2 Sept after | 32.5 °C | 24 % | 33 km/h | 0.0 mm | Very high 38 |
| 3 Sept after | 32.8 °C | 27 % | 38 km/h | 0.0 mm | Very high 42 |
| 4 Sept after | 31.0 °C | 40 % | 39 km/h | 0.0 mm | High 37 |
| 5 Sept after | 31.0 °C | 40 % | 38 km/h | 0.0 mm | High 35 |
| 6 Sept after | 31.0 °C | 48 % | 37 km/h | 0.5 mm | High 31 |
| 7 Sept after | 32.2 °C | 42 % | 37 km/h | 0.0 mm | High 30 |
| 8 Sept after | 31.0 °C | 47 % | 28 km/h | 0.0 mm | High 27 |
| 9 Sept after | 32.3 °C | 38 % | 50 km/h | 0.0 mm | High 37 |
| 10 Sept after | 33.2 °C | 36 % | 28 km/h | 0.0 mm | High 28 |
| 11 Sept after | 35.5 °C | 25 % | 26 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 · 7 Aug 2026
After · 1 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 22 August 2026 the air beside the fire reached 25 µg/m³ of PM2.5, but no daily average passed the WHO guideline (15).
PM2.5 peak25 µg/m³
Days over the guideline0 days
PM1027 µg/m³
Optical depth0.27
WHO 15
13 Aug17 Aug21 Aug25 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 · 54Every 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
- 5,209 haKupang20 August 2023 · 14 days · 6 km away
- 2,686 haKupangJuly 2024 · 5 days · 6 km away
- 4,434 haKupang25 August 2020 · 6 days · 10 km away
- 2,170 haKupang25 August 2023 · 13 days · 17 km away
- 2,391 haKupang14 October 2019 · 10 days · 26 km away
- 2,583 haKupang11 September 2023 · 12 days · 27 km away
Frequently asked questions
- How long did the Kupang fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 14 August 2026 to 25 August 2026 (12 days). The perimeter dates it from 15 August 2026 to 25 August 2026.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 2,913 hectares (29.1 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Kupang (2,933 ha, 0.6 %).
- What was the weather like?
- During the fire the temperature reached 34.0 °C, humidity dropped to 26 % and gusts hit 58 km/h. The fire danger index (FWI) reached 50, class Extreme.
- 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.
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 15 August 2026 to 25 August 2026. 54 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 (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.