Svilengrad fire, 25 August 2017 Свиленград · Svilengrad, Topolovgrad
The fire started on 25 August 2017 in Svilengrad, Bulgaria, and satellites saw it burning for 1 day. Copernicus mapped a burnt perimeter of 148 hectares from satellite imagery, spread across 2 municipalities.
It is the 39th largest in Haskovo since 2016 (of 46 with a page). Number 9 in Bulgaria in 2017, of 10.
The power measured by the satellite is low (12.0 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.
Compare with…
- Burnt area
- 148ha
- Copernicus perimeter
- Duration
- 1day
- 25 Aug 2017 – 25 Aug 2017
- Municipalities hit
- 2
- municipalities
- Started on
- 25 Aug
- 2017
- Heat detections
- 3
- in a single hotspot: 12 MW
- Danger at start
- 31
- High · FWI index
- Average daily power
- 30MW
- detected power per day, on average
Where it burned
How it evolved, day by day
25 Aug 2017 · 30 MW · 3
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 2 days without rain (1 mm or more) when it started. Rain came after the fire: 5.5 mm on 29 Aug.
This area had burned before
No earlier perimeters overlap this fire since 2016, when the satellite record begins.
What happened to each town
-
76 ha reached on 25 Aug0.1 %
-
72 ha reached on 25 Aug0.1 %
Burnt area inside each municipality, from crossing the official 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.
What burned
- Scrub and transitional woodland54 %
- Other natural land25 %
- Agricultural areas21 %
Natura 2000 protected area affected: 100 %
- ZEPA + LIC Sakar BG0000212 · BG0002021
Natura 2000 sites (European Environment Agency, 2024 release) crossed by the perimeter.
Land cover inside the perimeter according to Corine Land Cover, as reported by Copernicus.
People and buildings inside the perimeter
GHSL 2015Inside the perimeter there was no noticeable built-up land and almost nobody lived there (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) |
|---|---|---|---|---|---|
| 25 Aug | 29.1 °C | 29 % | 38 km/h | 0.0 mm | High 31 |
| 26 Aug after | 30.1 °C | 30 % | 41 km/h | 0.0 mm | High 33 |
| 27 Aug after | 30.8 °C | 31 % | 40 km/h | 0.0 mm | High 34 |
| 28 Aug after | 33.8 °C | 26 % | 30 km/h | 0.0 mm | High 29 |
| 29 Aug after | 23.9 °C | 45 % | 42 km/h | 5.5 mm | Low 6 |
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 23 August 2017 the air beside the fire reached 18 µ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 · 3Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 2,202 haTopolovgrad ТополовградAugust 2020 · 3 days · 4 km away
- 1,968 haTopolovgrad ТополовградSeptember 2023 · 2 days · 5 km away
- 7,848 haElhovo ЕлховоJuly 2025 · 6 days · 9 km away
- 8,124 haSvilengrad Свиленград13 July 2024 · 6 days · 15 km away
- 1,446 haHarmanli ХарманлиJune 2024 · 2 days · 28 km away
- 2,719 haHarmanli ХарманлиAugust 2025 · 5 days · 35 km away
Frequently asked questions
- How long did the Svilengrad fire last?
- Copernicus dates it between 25 August 2017 and 25 August 2017: 1 day between the first and last image with fire.
- How much area did it burn?
- The perimeter Copernicus measured from satellite imagery is 148 hectares (1.5 km²). Official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Svilengrad (76 ha, 0.1 %); Topolovgrad (72 ha, 0.1 %).
- Did the fire reach a town?
- The fire came within 23.2 km of the centre of Topolovgrad, the closest of the areas it touched. That is the distance from the perimeter, or the nearest hotspot, to the point marking the centre; it does not mean it entered the houses.
- What was the weather like?
- During the fire the temperature reached 29.1 °C, humidity dropped to 29 % and gusts hit 38 km/h. The fire danger index (FWI) reached 31, class High.
- Where does this data come from?
- From the EFFIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Bulgaria (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 · Emergency number and official warnings ›
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: EFFIS (Copernicus), mapped on satellite imagery.
- Dates from the perimeter: the VIIRS detections inside it did not change them. 3 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 and land cover come from the Copernicus European Forest Fire Information System (EFFIS), measured on MODIS and Sentinel-2 imagery and published under CC BY 4.0. 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 (Public Domain). The area per municipality is computed by WorldFires by crossing the perimeter with those boundaries, so it may differ slightly from each country’s official figure.