Skip to content
worldfires
BG · Bulgaria · –

Elhovo fire, July 2025 Елхово · Elhovo, Topolovgrad, Svilengrad

Out · last detection 29 Jul 2025, 10:52 UTC

The fire started on 26 July 2025 in Elhovo, Bulgaria, and satellites saw it burning for 6 days. Copernicus mapped a burnt perimeter of 7,848 hectares from satellite imagery, spread across 3 municipalities.

It is the largest fire in Yambol since 2016 (of 17 with a page). The largest in Bulgaria in 2025, of 44.

Burnt area
7,848ha
Copernicus perimeter
Duration
6days
26 Jul 2025 – 31 Jul 2025
Municipalities hit
3
municipalities
Started on
26 Jul
2025
Heat detections
147
in a single hotspot: 100 MW
Danger at start
41
Very high · FWI index
Average daily power
493MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 26 Jul31 Jul
29 Jul 2025

How it evolved, day by day

27 Jul 2025 · 1,186 MW · 86 28 Jul 2025 · 77 MW · 22 29 Jul 2025 · 215 MW · 39
27 Jul 28 Jul 29 Jul

Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.

The weather it burned in

37°high
41km/h · peak gust
27%lowest humidity

It had gone 24 days without rain (1 mm or more) when it started. Rain came after the fire: 1.1 mm on 1 Aug.

This area had burned before

27% of the perimeter overlaps earlier fires recorded since 2016: 556 ha in 2016, 1,542 ha in 2020, 30 ha in 2024.

How big is it?

10 km
It burned the equivalent of 5% of the area of London (78 km² against 1,583 km²).

London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).

This compares size, not location: both shapes are at the same scale, north up, centred on each other.

What happened to each town

  1. Elhovo Елхово 12,450 inhabitants · 13.3 km from the centre where it started
    3,953 ha reached on 27 Jul
    5.3 %
  2. Topolovgrad Тополовград 8,260 inhabitants · 15.7 km from the centre
    3,346 ha reached on 27 Jul
    4.7 %
  3. Svilengrad Свиленград 19,993 inhabitants · 27.5 km from the centre
    400 ha reached on 27 Jul
    0.6 %

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

  • Agricultural areas42 %
  • Other natural land27 %
  • Scrub and transitional woodland20 %
  • Broadleaved forest5.6 %
  • Mixed forest4.1 %
  • Artificial surfaces0.9 %
  • Other land cover0.8 %

Natura 2000 protected area affected: 100 %

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 2025
Built-up area4.2 ha
Residents≈ 150

Inside the perimeter there were about 4.2 hectares of built-up land and about 150 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

Checked against the press

Checked on 29 September 2026

We checked this page against 4 sources published once the fire was out. This is what they add:

Also known as
Пожарът край Лесово · Пожарът в Сакар · Пожарът в Тополовградско
According to the sources, several fires that ended up merging:
  • Lesovo 26 July 2025
  • Radovets / Vladimirovo / Studena (Topolovgrad y Svilengrad, prov. Haskovo) 27 July 2025 6,000 ha
  • Srem / Ustrem / Granitovo / Melnitsa 28 July 2025
  • Bakadzhik (prov. Yambol, junto a la frontera turca) 27 July 2025 600 ha
Official area reported: 9,000 ha (the satellite measured 7,848 ha)
Declared under control (not yet extinguished): 31 July 2025

Sources

Official figures are measured differently from satellite ones and sometimes cover only part of the fire.

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 37.1 °C 27 % 36 km/h 0.0 mm Very high 41
27 Jul 34.7 °C 37 % 41 km/h 0.0 mm Extreme 55
28 Jul 36.0 °C 34 % 28 km/h 0.0 mm High 33
29 Jul 34.2 °C 32 % 38 km/h 0.0 mm Very high 38
30 Jul 32.2 °C 37 % 34 km/h 0.0 mm High 37
31 Jul 29.2 °C 50 % 38 km/h 1.2 mm High 36
1 Aug after 30.2 °C 42 % 43 km/h 1.1 mm High 25

Its twins: fires that started in the same weather

It started with an FWI of 41.4, a minimum humidity of 27% and 24 days without rain. Fires in the area that started in weather like this since 2016: 17.

FWI at the start 41.4
Minimum humidity 27 %
Days without rain 24
this fire chosen twins rest of the area
Almost identicalSimilar

Outlines of the closest twins

Harmanli fire, August 2016
217 ha 1 day FWI 43.1 Min. humidity 27 % 44 km away, in 2016

First rain (1 mm or more) after it ended: 4.4 mm on 12 Aug.

What happened to them

2 days
median duration
254 ha
median area
6 %
went past 1,000 ha
3.6 mm
rain at the end (median; 9 of 17 had it)

It was 30.9 times larger than the median of its twins and lasted 6 days, against 2 days.

None of its 17 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 8 of 17, 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 3.6 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

1.1 mmfirst rain
1 Augthe day after it ended
41km/h · max. gust

It was considered over on 31 Jul, and on 1 Aug 1.1 mm fell. We do not know whether the rain or the firefighters put it out. Twins with rain when they ended: 9 of 17, with a median of 3.6 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.

How we calculate it

Before and after, from space

Drag the line to compare the same ground before the fire and after it.

Before · 19 Jul 2025
After · 7 Aug 2025

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 · Copernicus

On 29 July 2025 the air beside the fire reached 25 µg/m³ of PM2.5. That day averaged 16: 1.1 times the WHO daily guideline (15).

PM2.5 peak25 µg/m³
Days over the guideline1 day
PM1031 µg/m³
Optical depth0.62
24 Jul27 Jul30 Jul2 Aug
Good Fair Moderate Poor Very poor Extremely poor

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 · 147Every 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 timeSatelliteFRP (MW)LatLon

Other fires nearby

All fires in Bulgaria

Frequently asked questions

How long did the Elhovo fire last?
Copernicus dates it between 26 July 2025 and 31 July 2025: 6 days between the first and last image with fire.
How much area did it burn?
The perimeter Copernicus measured from satellite imagery is 7,848 hectares (78.5 km²). Official national figures may differ.
Which municipalities burned?
The fire entered 3 municipalities: Elhovo (3,953 ha, 5.3 %); Topolovgrad (3,346 ha, 4.7 %); Svilengrad (400 ha, 0.6 %).
Did the fire reach a town?
The fire started in Elhovo and came within 13.3 km of its centre. 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 37.1 °C, humidity dropped to 27 % and gusts hit 41 km/h. The fire danger index (FWI) reached 55, class Extreme.
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.
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: 17. Their median duration was 2 days and their median area 254 ha; 6 % went past 1,000 ha. None of its 17 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 8 of 17, 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 3.6 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.

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.

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
What do you think is wrong?

We will only use your email to reply about this report. Privacy. This is not an emergency service: if there is a fire now, call 112.

How we know this
  • Perimeter: EFFIS (Copernicus), mapped on satellite imagery.
  • Dates from the perimeter: the VIIRS detections inside it did not change them. 147 Suomi-NPP VIIRS detections on those dates.
  • We have not matched this page with any official record.
  • Checked against news and agencies: 4 confirmed sources.
  • 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.

How we build fire pages: methodology

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.