Sesan fire, 16 January 2025 Sesan
The fire started on 16 January 2025 in Sesan, Cambodia, and satellites saw it burning for 24 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 4,486 hectares from heat detections, spread across a single municipality.
It is the 36th largest in Stung Treng since 2016 (of 130 with a page). Number 6 in Cambodia in 2025, of 28.
Compare with…
Suggestions: Sesan · 2021Sesan · 2024Sesan · 2019Sesan · 2016
- Burnt area
- 4,486ha
- GWIS perimeter (Copernicus)
- Duration
- 24days
- 16 Jan 2025 – 8 Feb 2025
- Municipalities hit
- 1
- districts
- Started on
- 16 Jan
- 2025
- Heat detections
- 303
- in a single hotspot: 103 MW
- Danger at start
- 19
- Moderate · FWI index
- Average daily power
- 76MW
- 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 36 days without rain (1 mm or more) when it started.
This area had burned before
100% of the perimeter overlaps earlier fires recorded since 2016: 1,566 ha in 2016, 1,174 ha in 2017, 1,951 ha in 2019, 1,196 ha in 2020, 4,490 ha in 2021, 2,618 ha in 2022, 2,839 ha in 2024. Part of it burned more than once, so the yearly figures add up to more than the 4,491 ha that had burned before.
- 2,966 ha Sesan fire, January 2021 16,629 ha in total; the hectares shown are those it shares with this fire
- 2,839 ha Sesan fire, January 2024 6,102 ha in total; the hectares shown are those it shares with this fire
- 1,859 ha Sesan fire, December 2019 13,216 ha in total; the hectares shown are those it shares with this fire
- 1,566 ha Sesan fire, January 2016 6,998 ha in total; the hectares shown are those it shares with this fire
- 1,506 ha Sesan fire, January 2022 11,364 ha in total; the hectares shown are those it shares with this fire
- 288 ha Sesan fire, January 2017 17,221 ha in total; the hectares shown are those it shares with this fire
- 78 ha Sesan fire, December 2018 4,901 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
-
Sesan where it started4,514 ha reached on 16 Jan1.7 %
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) |
|---|---|---|---|---|---|
| 19 Jan | 31.3 °C | 41 % | 26 km/h | 0.0 mm | Moderate 19 |
| 20 Jan | 30.7 °C | 44 % | 23 km/h | 0.0 mm | Moderate 20 |
| 21 Jan | 31.1 °C | 41 % | 28 km/h | 0.0 mm | Moderate 20 |
| 22 Jan | 32.2 °C | 38 % | 21 km/h | 0.0 mm | Moderate 20 |
| 23 Jan | 32.9 °C | 37 % | 22 km/h | 0.0 mm | Moderate 20 |
| 24 Jan | 34.1 °C | 35 % | 20 km/h | 0.0 mm | High 22 |
| 25 Jan | 34.6 °C | 34 % | 19 km/h | 0.0 mm | High 22 |
| 26 Jan | 34.4 °C | 39 % | 31 km/h | 0.0 mm | High 28 |
| 27 Jan | 31.3 °C | 37 % | 37 km/h | 0.0 mm | High 27 |
| 28 Jan | 30.3 °C | 37 % | 31 km/h | 0.0 mm | High 26 |
| 29 Jan | 30.7 °C | 39 % | 33 km/h | 0.0 mm | High 26 |
| 30 Jan | 30.9 °C | 32 % | 24 km/h | 0.0 mm | High 25 |
| 31 Jan | 32.1 °C | 34 % | 23 km/h | 0.0 mm | High 25 |
| 1 Feb | 33.6 °C | 32 % | 17 km/h | 0.0 mm | High 24 |
| 2 Feb | 34.4 °C | 36 % | 22 km/h | 0.0 mm | High 25 |
| 3 Feb | 34.1 °C | 36 % | 36 km/h | 0.0 mm | High 32 |
| 4 Feb | 32.2 °C | 41 % | 36 km/h | 0.0 mm | High 30 |
| 5 Feb | 32.5 °C | 37 % | 32 km/h | 0.0 mm | High 29 |
| 6 Feb | 33.5 °C | 37 % | 30 km/h | 0.0 mm | High 28 |
| 7 Feb | 33.6 °C | 35 % | 27 km/h | 0.0 mm | High 30 |
| 8 Feb | 33.5 °C | 33 % | 33 km/h | 0.0 mm | High 31 |
| 9 Feb after | 31.4 °C | 37 % | 29 km/h | 0.0 mm | High 30 |
| 10 Feb after | 32.2 °C | 38 % | 26 km/h | 0.0 mm | High 30 |
| 11 Feb after | 33.2 °C | 43 % | 20 km/h | 0.0 mm | High 27 |
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 25 January 2025 the air beside the fire reached 93 µg/m³ of PM2.5. That day averaged 46: 3.1 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 · 303Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 11,364 haSesan6 January 2022 · 45 days · 2 km away
- 30,976 haSesanDecember 2025 · 71 days · 5 km away
- 13,216 haSesanDecember 2019 · 51 days · 7 km away
- 16,629 haSesan15 January 2021 · 31 days · 8 km away
- 17,221 haSesan29 January 2017 · 52 days · 9 km away
- 22,903 haSiem Pang26 January 2026 · 60 days · 21 km away
Frequently asked questions
- How long did the Sesan fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 16 January 2025 to 8 February 2025 (24 days). The perimeter dates it from 19 January 2025 to 1 February 2025.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 4,486 hectares (44.9 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Sesan (4,514 ha, 1.7 %).
- What was the weather like?
- During the fire the temperature reached 34.6 °C, humidity dropped to 32 % and gusts hit 37 km/h. The fire danger index (FWI) reached 28, 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 adjusted with the VIIRS detections inside the perimeter, which said 19 January 2025 to 1 February 2025. 303 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.