Rompin fire, 19 July 2025 Rompin, Pekan
The fire started on 19 July 2025 in Rompin, Malaysia, and satellites saw it burning for 13 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 825 hectares from heat detections, spread across 2 municipalities.
It is the 45th largest in Pahang since 2016 (of 107 with a page). Number 5 in Malaysia in 2025, of 10.
Compare with…
Suggestions: Pekan · 2024Rompin · 2021Rompin · 2017Pekan · 2019
- Burnt area
- 825ha
- GWIS perimeter (Copernicus)
- Duration
- 13days
- 19 Jul 2025 – 31 Jul 2025
- Municipalities hit
- 2
- districts
- Started on
- 19 Jul
- 2025
- Heat detections
- 84
- in a single hotspot: 106 MW
- Danger at start
- 0
- Very low · FWI index
- Average daily power
- 222MW
- 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 0 days without rain (1 mm or more) when it started. Rain came after the fire: 10.7 mm on 1 Aug.
This area had burned before
86% of the perimeter overlaps earlier fires recorded since 2016: 556 ha in 2017, 29 ha in 2019, 393 ha in 2021, 786 ha in 2024. Part of it burned more than once, so the yearly figures add up to more than the 712 ha that had burned before.
- 514 ha Pekan fire, March 2024 4,458 ha in total; the hectares shown are those it shares with this fire
- 393 ha Rompin fire, March 2021 1,037 ha in total; the hectares shown are those it shares with this fire
- 334 ha Rompin fire, June 2017 584 ha in total; the hectares shown are those it shares with this fire
- 29 ha Pekan fire, March 2019 1,365 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).
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
-
Rompin where it started714 ha reached on 19 Jul0.1 %
-
117 ha reached on 27 Jul0.0 %
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 2025Inside 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) |
|---|---|---|---|---|---|
| 26 Jul | 31.9 °C | 69 % | 23 km/h | 7.4 mm | Very low 0 |
| 27 Jul | 33.0 °C | 62 % | 22 km/h | 1.3 mm | Very low 1 |
| 28 Jul | 32.8 °C | 60 % | 25 km/h | 0.0 mm | Very low 4 |
| 29 Jul | 33.0 °C | 65 % | 28 km/h | 1.0 mm | Very low 4 |
| 30 Jul | 32.3 °C | 65 % | 25 km/h | 6.9 mm | Very low 1 |
| 31 Jul | 32.8 °C | 60 % | 19 km/h | 0.1 mm | Very low 3 |
| 1 Aug after | 31.6 °C | 67 % | 24 km/h | 10.7 mm | Very low 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 24 July 2025 the air beside the fire reached 38 µg/m³ of PM2.5. That day averaged 28: 1.9 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 · 84Every 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 Rompin fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 19 July 2025 to 31 July 2025 (13 days). The perimeter dates it from 26 July 2025 to 31 July 2025.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 825 hectares (8.2 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Rompin (714 ha, 0.1 %); Pekan (117 ha, 0.0 %).
- What was the weather like?
- During the fire the temperature reached 33.0 °C, humidity dropped to 60 % and gusts hit 28 km/h. The fire danger index (FWI) reached 4, class Very low.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Malaysia (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: 999 · Emergency number and official warnings ›
Satellite cross-check
History of this page · 1 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
- Start date: 26 July 2025 → 19 July 2025.
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 26 July 2025 to 31 July 2025. 84 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 License). 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.