Kaev Seima fire, 1 January 2025 Kaev Seima
The fire started on 1 January 2025 in Kaev Seima, Cambodia, and satellites saw it burning for 12 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 4,608 hectares from heat detections, spread across a single municipality.
It is the 29th largest in Mondulkiri since 2016 (of 112 with a page). Number 6 in Cambodia in 2025, of 31.
Compare with…
- Burnt area
- 4,608ha
- GWIS perimeter (Copernicus)
- Duration
- 12days
- 1 Jan 2025 – 12 Jan 2025
- Municipalities hit
- 1
- districts
- Started on
- 1 Jan
- 2025
- Heat detections
- 141
- in a single hotspot: 47 MW
- Danger at start
- 14
- Moderate · FWI index
- Average daily power
- 94MW
- 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 6 days without rain (1 mm or more) when it started.
This area had burned before
95% of the perimeter overlaps earlier fires recorded since 2016: 2,123 ha in 2016, 654 ha in 2017, 796 ha in 2018, 611 ha in 2019, 2,191 ha in 2020, 2,433 ha in 2021, 372 ha in 2022, 741 ha in 2023, 3,088 ha in 2024. Part of it burned more than once, so the yearly figures add up to more than the 4,359 ha that had burned before.
- 2,433 ha Kaev Seima fire, January 2024 3,113 ha in total; the hectares shown are those it shares with this fire
- 2,075 ha Snuol fire, January 2016 36,542 ha in total; the hectares shown are those it shares with this fire
- 1,347 ha Kaev Seima fire, January 2020 2,692 ha in total; the hectares shown are those it shares with this fire
- 796 ha Kaev Seima fire, January 2021 2,036 ha in total; the hectares shown are those it shares with this fire
- 741 ha Kaev Seima fire, January 2023 3,181 ha in total; the hectares shown are those it shares with this fire
- 128 ha Kaev Seima fire, February 2017 5,287 ha in total; the hectares shown are those it shares with this fire
- 81 ha Kaev Seima fire, January 2024 2,439 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
-
Kaev Seima where it started4,636 ha1.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 2025Inside the perimeter there were about 0.69 hectares of built-up land and about 1,600 residents (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) |
|---|---|---|---|---|---|
| 1 Jan | 29.4 °C | 53 % | 46 km/h | 0.0 mm | Moderate 14 |
| 2 Jan | 31.9 °C | 48 % | 42 km/h | 0.0 mm | Moderate 13 |
| 3 Jan | 31.2 °C | 48 % | 51 km/h | 0.0 mm | Moderate 16 |
| 4 Jan | 30.7 °C | 42 % | 51 km/h | 0.0 mm | Moderate 16 |
| 5 Jan | 31.3 °C | 40 % | 46 km/h | 0.0 mm | Moderate 17 |
| 6 Jan | 31.7 °C | 38 % | 48 km/h | 0.0 mm | Moderate 18 |
| 7 Jan | 33.0 °C | 37 % | 33 km/h | 0.0 mm | Moderate 17 |
| 8 Jan | 32.7 °C | 30 % | 38 km/h | 0.0 mm | High 22 |
| 9 Jan | 32.6 °C | 37 % | 46 km/h | 0.0 mm | High 24 |
| 10 Jan | 30.9 °C | 41 % | 67 km/h | 0.0 mm | High 30 |
| 11 Jan | 29.1 °C | 43 % | 70 km/h | 0.0 mm | High 28 |
| 12 Jan | 28.4 °C | 39 % | 65 km/h | 0.0 mm | High 28 |
| 13 Jan after | 30.1 °C | 44 % | 54 km/h | 0.0 mm | High 24 |
| 14 Jan after | 32.7 °C | 47 % | 45 km/h | 0.0 mm | High 22 |
| 15 Jan after | 31.7 °C | 53 % | 51 km/h | 0.3 mm | High 22 |
| 16 Jan after | 31.5 °C | 45 % | 65 km/h | 0.0 mm | High 27 |
| 17 Jan after | 30.6 °C | 42 % | 61 km/h | 0.0 mm | High 26 |
| 18 Jan after | 31.5 °C | 43 % | 44 km/h | 0.0 mm | High 22 |
| 19 Jan after | 33.0 °C | 35 % | 38 km/h | 0.0 mm | High 23 |
| 20 Jan after | 32.2 °C | 29 % | 30 km/h | 0.0 mm | High 24 |
| 21 Jan after | 32.4 °C | 28 % | 32 km/h | 0.0 mm | High 24 |
| 22 Jan after | 33.6 °C | 30 % | 31 km/h | 0.0 mm | High 24 |
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 13 January 2025 the air beside the fire reached 28 µg/m³ of PM2.5, but no daily average passed the WHO 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 · 141Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 36,542 haSnuol21 January 2016 · 73 days · 2 km away
- 5,287 haKaev Seima25 February 2017 · 10 days · 8 km away
- 15,165 haKaev Seima17 January 2026 · 19 days · 11 km away
- 6,236 haKaev Seima6 February 2017 · 13 days · 11 km away
- 6,507 haKaev Seima17 January 2026 · 13 days · 13 km away
- 6,724 haKaev Seima20 January 2026 · 10 days · 29 km away
Frequently asked questions
- How long did the Kaev Seima fire last?
- GWIS (Copernicus) dates it between 1 January 2025 and 12 January 2025: 12 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 4,608 hectares (46.1 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Kaev Seima (4,636 ha, 1.6 %).
- What was the weather like?
- During the fire the temperature reached 33.0 °C, humidity dropped to 30 % and gusts hit 70 km/h. The fire danger index (FWI) reached 30, class High.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Cambodia (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.
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.
- Dates from the perimeter: the VIIRS detections inside it did not change them. 141 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 4.0 International (CC BY 4.0)). 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.