Skip to content
worldfires
ID · Indonesia · →

Bima fire, July 2026 Bima

Out · last measured on 7 Jul 2026

The fire started on 5 July 2026 in Bima, Indonesia, and satellites saw it burning for 3 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,509 hectares from heat detections, spread across a single municipality.

It is the 28th largest in West Nusa Tenggara since 2016 (of 29 with a page). Number 974 in Indonesia in 2026, of 988.

We have the GWIS perimeter for this fire, but not yet its hotspots: NASA publishes the yearly hotspot archive only once the year closes. The page picks them up automatically when they are available.

Burnt area
1,509ha
GWIS perimeter (Copernicus)
Duration
3days
5 Jul 2026 – 7 Jul 2026
Municipalities hit
1
regencies
Started on
5 Jul
2026
Danger at start
9
Low · FWI index

Where it burned

The weather it burned in

21°high
34km/h · peak gust
55%lowest humidity

It had gone 3 days without rain (1 mm or more) when it started. Rain came after the fire: 1.4 mm on 9 Jul.

This area had burned before

71% of the perimeter overlaps earlier fires recorded since 2016: 12 ha in 2017, 677 ha in 2018, 282 ha in 2019, 167 ha in 2021, 390 ha in 2023, 232 ha in 2024. Part of it burned more than once, so the yearly figures add up to more than the 1,075 ha that had burned before.

What happened to each town

  1. Bima where it started
    1,518 ha
    0.4 %

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)
5 Jul 20.8 °C 56 % 25 km/h 0.0 mm Low 9
6 Jul 20.9 °C 57 % 31 km/h 2.0 mm Very low 3
7 Jul 20.4 °C 55 % 34 km/h 1.0 mm Very low 4
8 Jul after 20.5 °C 50 % 34 km/h 0.7 mm Low 7
9 Jul after 20.6 °C 50 % 33 km/h 1.4 mm Very low 5

Before and after, from space

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

Before · 28 Jun 2026
After · 14 Jul 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 3 July 2026 the air beside the fire reached 17 µg/m³ of PM2.5, but no daily average passed the WHO guideline (15).

PM2.5 peak17 µg/m³
Days over the guideline0 days
PM1020 µg/m³
Optical depth0.17
345678910
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)

Other fires nearby

All fires in Indonesia ›

Frequently asked questions

How long did the Bima fire last?
GWIS (Copernicus) dates it between 5 July 2026 and 7 July 2026: 3 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 1,509 hectares (15.1 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Bima (1,518 ha, 0.4 %).
What was the weather like?
During the fire the temperature reached 20.9 °C, humidity dropped to 55 % and gusts hit 34 km/h. The fire danger index (FWI) reached 9, class 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

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.