Burned area
satellite only5,249ha
Perimeter published by GWIS (Copernicus).
- Source
- GWIS (Copernicus)
- Date
- 6 Apr 2016 – 28 Apr 2016
+− cross-check
No official record is matched to this page to compare it with.
KH · Cambodia · –
Kampong Svay fire, 6 April 2016 Kampong Svay, Kampong Leaeng
Out · last detection 28 Apr 2016, 06:35 UTC
The fire started on 6 April 2016 in Kampong Svay, Cambodia, and satellites saw it burning for 23 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 5,249 hectares from heat detections, spread across 2 municipalities.
It is the 5th largest in Kampong Thom since 2016 (of 28 with a page). Number 16 in Cambodia in 2016, of 113.
Use this data
Compare with…
Use this data
Fire page data · version 2026-10-27matches 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 only23days
6 Apr 2016 to 28 Apr 2016: first and last day with fire on the page.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- last detection: 28 Apr 2016, 06:35 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 only6 Apr 2016
First day with fire seen by the satellites or the perimeter.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- 6 Apr 2016
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
Hotspots
satellite only448
VIIRS detections at 375 m. Most intense hotspot: 210 MW.
- Source
- NASA FIRMS · VIIRS (Suomi NPP)
- Date
- 6 Apr 2016 – 28 Apr 2016
+− 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 only1,379MW
Total radiative power on 19 April 2016; hotspots that day: 51.
- Source
- NASA FIRMS · VIIRS (FRP)
- Date
- 19 Apr 2016
+− 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
model32.7FWI · high
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 10.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 6 Apr 2016, 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
model40.6°C · 38% RH
High of 40.6 °C and minimum humidity of 38% on 26 April 2016; gusts of 36 km/h on 19 April 2016.
- Source
- weather model at the fire’s grid cell
- Date
- 6 Apr 2016 – 28 Apr 2016
- 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.
Living inside
model≈ 1,200people
Estimated residents inside the perimeter and 0.55 ha of built-up area (100 m grid, epoch 2015).
- Source
- GHSL R2023A · JRC
- Date
- calculated on 24 October 2026
+− cross-check
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.
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 weatherWeather and FWI computed from the ERA5 reanalysis
-
logStart date: 13 April 2016 → 6 April 2016.
-
· reconstructed GHSLPopulation and built-up area computed
What was saved on 27 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
- 5,249 ha
- Dates
- 6 Apr 2016 – 28 Apr 2016
- Name
- Kampong Svay
- Official record
- —
Versioned permanent link
https://worldfires.org/en/fire/kampong-svay-2016-04-2?v=2026-10-27A 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 kampong-svay-2016-04-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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2016-04-06 | 7 | 69 | 38.4 | 27.3 | 38 | 15.5 | 27.4 | 0 | 32.7 | alto | 1 |
| 2016-04-07 | 3 | 29 | 37.8 | 28.1 | 45 | 10.9 | 25.2 | 0 | 29.5 | alto | 1 |
| 2016-04-08 | 4 | 103 | 38.2 | 28 | 44 | 13.1 | 31.3 | 0 | 31.4 | alto | 1 |
| 2016-04-09 | 4 | 7 | 38 | 28.4 | 46 | 12.8 | 23.8 | 0 | 31.1 | alto | 1 |
| 2016-04-10 | 2 | 11 | 37.9 | 28.9 | 46 | 12.2 | 20.2 | 0 | 30.6 | alto | 1 |
| 2016-04-11 | 13 | 47 | 38.7 | 28.9 | 43 | 14.9 | 27.7 | 0 | 33 | alto | 1 |
| 2016-04-12 | 4 | 42 | 39.9 | 28.6 | 38 | 15 | 28.1 | 0 | 33.5 | alto | 1 |
| 2016-04-13 | 12 | 85 | 39.5 | 27.4 | 33 | 14.4 | 26.6 | 0 | 35.7 | alto | 1 |
| 2016-04-14 | 16 | 259 | 39.5 | 27.4 | 35 | 13.7 | 23 | 0 | 35.4 | alto | 1 |
| 2016-04-15 | 40 | 395 | 40.3 | 27.8 | 34 | 14.1 | 24.5 | 0 | 36 | alto | 1 |
| 2016-04-16 | 39 | 991 | 40 | 28.4 | 35 | 13.9 | 24.1 | 0 | 36.1 | alto | 1 |
| 2016-04-17 | 14 | 151 | 40 | 29.3 | 37 | 13.9 | 29.5 | 0 | 36.3 | alto | 1 |
| 2016-04-18 | 41 | 725 | 40.3 | 29.7 | 39 | 11.8 | 22 | 0 | 34.7 | alto | 1 |
| 2016-04-19 | 51 | 1,379 | 37.7 | 29.2 | 45 | 15.8 | 35.6 | 0.4 | 34.9 | alto | 1 |
| 2016-04-20 | 8 | 140 | 38.9 | 30.2 | 36 | 10.5 | 24.5 | 0 | 31.1 | alto | 1 |
| 2016-04-21 | 28 | 437 | 38.6 | 28.3 | 36 | 8.3 | 22.3 | 0.7 | 28 | alto | 1 |
| 2016-04-22 | 10 | 160 | 37.5 | 29.8 | 42 | 11.5 | 25.2 | 0.2 | 30.5 | alto | 1 |
| 2016-04-23 | 36 | 530 | 39.1 | 30.2 | 33 | 14 | 28.4 | 0 | 35.8 | alto | 1 |
| 2016-04-24 | 30 | 461 | 39.3 | 28.9 | 34 | 13.9 | 27.7 | 0 | 35.9 | alto | 1 |
| 2016-04-25 | 34 | 500 | 39.2 | 29.1 | 39 | 10.4 | 22.7 | 0.1 | 33.2 | alto | 1 |
| 2016-04-26 | 8 | 64 | 40.6 | 30.8 | 38 | 14.5 | 28.4 | 0 | 36.9 | alto | 1 |
| 2016-04-27 | 19 | 199 | 40.4 | 29.9 | 33 | 11.3 | 22.3 | 0 | 34.6 | alto | 1 |
| 2016-04-28 | 25 | 353 | 40.5 | 29.8 | 37 | 11.8 | 26.6 | 0 | 35.2 | alto | 1 |
| 2016-04-29 | 0 | 0 | 36.3 | 29.6 | 52 | 11.8 | 28.8 | 3.7 | 9.1 | bajo | 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
- 5,249ha
- GWIS perimeter (Copernicus)
- Duration
- 23days
- 6 Apr 2016 – 28 Apr 2016
- Municipalities hit
- 2
- districts
- Started on
- 6 Apr
- 2016
- Heat detections
- 448
- in a single hotspot: 210 MW
- Danger at start
- 33
- High · FWI index
- Average daily power
- 310MW
- detected power per day, on average
Where it burned
HOTSPOTS BY DAY
6 Apr28 Apr
28 Apr 2016
How it evolved, day by day
6 Apr
11 Apr
19 Apr
26 Apr
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
41°high
36km/h · peak gust
33%lowest humidity
It had gone 10 days without rain (1 mm or more) when it started. Rain came after the fire: 3.7 mm on 29 Apr.
This area had burned before
No earlier perimeters overlap this fire since 2016, when the satellite record begins.
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
-
Kampong Svay where it started4,979 ha reached on 6 Apr3.6 %
-
265 ha reached on 6 Apr0.3 %
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 2015Built-up area0.55 ha
Residents≈ 1,200
Inside the perimeter there were about 0.55 hectares of built-up land and about 1,200 residents (GHSL 2015, 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.
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) |
|---|---|---|---|---|---|
| 6 Apr | 38.4 °C | 38 % | 27 km/h | 0.0 mm | High 33 |
| 7 Apr | 37.8 °C | 45 % | 25 km/h | 0.0 mm | High 30 |
| 8 Apr | 38.2 °C | 44 % | 31 km/h | 0.0 mm | High 31 |
| 9 Apr | 38.0 °C | 46 % | 24 km/h | 0.0 mm | High 31 |
| 10 Apr | 37.9 °C | 46 % | 20 km/h | 0.0 mm | High 31 |
| 11 Apr | 38.7 °C | 43 % | 28 km/h | 0.0 mm | High 33 |
| 12 Apr | 39.9 °C | 38 % | 28 km/h | 0.0 mm | High 34 |
| 13 Apr | 39.5 °C | 33 % | 27 km/h | 0.0 mm | High 36 |
| 14 Apr | 39.5 °C | 35 % | 23 km/h | 0.0 mm | High 35 |
| 15 Apr | 40.3 °C | 34 % | 24 km/h | 0.0 mm | High 36 |
| 16 Apr | 40.0 °C | 35 % | 24 km/h | 0.0 mm | High 36 |
| 17 Apr | 40.0 °C | 37 % | 30 km/h | 0.0 mm | High 36 |
| 18 Apr | 40.3 °C | 39 % | 22 km/h | 0.0 mm | High 35 |
| 19 Apr | 37.7 °C | 45 % | 36 km/h | 0.4 mm | High 35 |
| 20 Apr | 38.9 °C | 36 % | 24 km/h | 0.0 mm | High 31 |
| 21 Apr | 38.6 °C | 36 % | 22 km/h | 0.7 mm | High 28 |
| 22 Apr | 37.5 °C | 42 % | 25 km/h | 0.2 mm | High 30 |
| 23 Apr | 39.1 °C | 33 % | 28 km/h | 0.0 mm | High 36 |
| 24 Apr | 39.3 °C | 34 % | 28 km/h | 0.0 mm | High 36 |
| 25 Apr | 39.2 °C | 39 % | 23 km/h | 0.1 mm | High 33 |
| 26 Apr | 40.6 °C | 38 % | 28 km/h | 0.0 mm | High 37 |
| 27 Apr | 40.4 °C | 33 % | 22 km/h | 0.0 mm | High 35 |
| 28 Apr | 40.5 °C | 37 % | 27 km/h | 0.0 mm | High 35 |
| 29 Apr after | 36.3 °C | 52 % | 29 km/h | 3.7 mm | Low 9 |
Its twins: fires that started in the same weather
It started with an FWI of 32.7, a minimum humidity of 38% and 10 days without rain. Fires in the area that started in weather like this since 2016: 19.
FWI at the start
32.7
Minimum humidity
38 %
Days without rain
10
this fire
chosen twins
rest of the area
Almost identicalSimilar
Outlines of the closest twins
This fire · Kampong Svay fire, 6 April 2016
5,249 ha
23 days
FWI 32.7
Min. humidity 38 %
Chhaeb fire, February 2024
4,805 ha
33 days
FWI 30.3
Min. humidity 39 %
154 km away, in 2024
First rain (1 mm or more) after it ended: 1.6 mm on 26 Mar.
Chhaeb fire, February 2024
6,194 ha
40 days
FWI 28.9
Min. humidity 38 %
165 km away, in 2024
First rain (1 mm or more) after it ended: 1.6 mm on 26 Mar.
Thala Barivat fire, January 2019
3,433 ha
34 days
FWI 33.7
Min. humidity 35 %
170 km away, in 2019
First rain (1 mm or more) after it ended: none in the following ten days.
Moung Ruessei fire, April 2024
12,407 ha
30 days
FWI 29.8
Min. humidity 37 %
106 km away, in 2024
First rain (1 mm or more) after it ended: 7.7 mm on 13 May.
Mongkol Borei fire, March 2019
2,032 ha
17 days
FWI 31.4
Min. humidity 36 %
165 km away, in 2019
First rain (1 mm or more) after it ended: 51.2 mm on 24 Mar.
What happened to them
- 24 days
- median duration
- 3,433 ha
- median area
- 11 %
- went past 10,000 ha
- 2.2 mm
- rain at the end (median; 15 of 19 had it)
It was 1.5 times larger than the median of its twins and lasted 23 days, against 24 days.
Only 5 of its 19 twins burned more. The weather on the first day does not explain everything: the wind in the following days, the fuel and the firefighting also count. In 4 of 19, not even 1 mm fell in the ten days after the end: they went out without rain. In the rest, the first rainy day brought a median of 2.2 mm.
This is a bank of analogues: it shows what usually happens, not what will happen. With fewer than 15 twins we give no figures. How we calculate it
How it ended
3.7 mmfirst rain
29 Aprthe day after it ended
36km/h · max. gust
It was considered over on 28 Apr, and on 29 Apr 3.7 mm fell. We do not know whether the rain or the firefighters put it out. Twins with rain when they ended: 15 of 19, with a median of 2.2 mm.
Weather on this page: Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)
How a twin is chosen
- Same area: fires that have already ended, less than 250 km from this one, since 2016.
- Same start: we compare the FWI on the first day, the minimum humidity that day and the run of days without rain before it. The slider sets how much they may differ.
- Only pages with final weather data (ERA5 reanalysis) calculated in the same way as this fire’s; agricultural and grass burns and pages with data under review are left out.
- Fires burning at the same time as this one (a week before or after) are left out: they share the same spell of weather and do not count as a precedent.
- They are sorted by similarity, and the outlines of the first five are drawn.
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
↔
Before · 30 Mar 2016
After · 5 May 2016
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.
Detections table · 448Every 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
Frequently asked questions
- How long did the Kampong Svay fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 6 April 2016 to 28 April 2016 (23 days). The perimeter dates it from 13 April 2016 to 28 April 2016.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 5,249 hectares (52.5 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Kampong Svay (4,979 ha, 3.6 %); Kampong Leaeng (265 ha, 0.3 %).
- What was the weather like?
- During the fire the temperature reached 40.6 °C, humidity dropped to 33 % and gusts hit 36 km/h. The fire danger index (FWI) reached 37, 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.
- How did the fires that started in similar weather in this area end?
- Fires less than 250 km away that started since 2016 with a similar FWI, humidity and dry spell: 19. Their median duration was 24 days and their median area 3,433 ha; 11 % went past 10,000 ha. Only 5 of its 19 twins burned more. The weather on the first day does not explain everything: the wind in the following days, the fuel and the firefighting also count. In 4 of 19, not even 1 mm fell in the ten days after the end: they went out without rain. In the rest, the first rainy day brought a median of 2.2 mm.
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 · 1 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
- Start date: 13 April 2016 → 6 April 2016.
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 13 April 2016 to 28 April 2016. 448 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 2015, 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.