Belene fire, July 2026 Белене · Belene
The fire started on 28 July 2026 in Belene, Bulgaria, and satellites saw it burning for 1 day. Copernicus mapped a burnt perimeter of 159 hectares from satellite imagery, spread across a single municipality.
It is the 15th largest in Pleven since 2016 (of 23 with a page). Number 14 in Bulgaria in 2026, of 23.
- Burnt area
- 159ha
- Copernicus perimeter
- Duration
- 1day
- 28 Jul 2026 – 28 Jul 2026
- Municipalities hit
- 1
- municipalities
- Started on
- 28 Jul
- 2026
- Heat detections
- 21
- in a single hotspot: 145 MW
- Danger at start
- 33
- High · FWI index
- Energy released
- 1.3GW
- sum of detected power
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 5 days without rain (1 mm or more) when it started.
This area had burned before
No earlier perimeters overlap this fire since 2016, when the satellite record begins.
What happened to each town
-
159 ha reached on 28 Jul0.7 %
Burnt area inside each municipality, from crossing the official perimeter with administrative boundaries. The distance is from the town centre to the nearest fire: staying a kilometre away does not mean it reached the houses.
What burned
- Other natural land97 %
- Agricultural areas3.1 %
Natura 2000 protected area affected: 99 %
- LIC Persina BG0000396
- ZEPA Svishtovsko-Belenska nizina BG0002083
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.
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) |
|---|---|---|---|---|---|
| 28 Jul | 31.6 °C | 26 % | 41 km/h | 0.0 mm | High 33 |
| 29 Jul after | 30.8 °C | 35 % | 16 km/h | 0.0 mm | High 22 |
| 30 Jul after | 32.0 °C | 31 % | 21 km/h | 0.0 mm | High 24 |
| 31 Jul after | 31.6 °C | 31 % | 29 km/h | 0.0 mm | High 28 |
| 1 Aug after | 31.3 °C | 24 % | 35 km/h | 0.0 mm | High 30 |
| 2 Aug after | 32.5 °C | 23 % | 30 km/h | 0.0 mm | High 31 |
| 3 Aug after | 32.8 °C | 26 % | 21 km/h | 0.0 mm | High 28 |
| 4 Aug after | 34.4 °C | 25 % | 20 km/h | 0.0 mm | High 29 |
| 5 Aug after | 35.2 °C | 26 % | 26 km/h | 0.0 mm | High 32 |
| 6 Aug after | 35.5 °C | 27 % | 23 km/h | 0.1 mm | High 32 |
| 7 Aug after | 34.2 °C | 26 % | 16 km/h | 0.0 mm | High 29 |
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 30 July 2026 the air beside the fire reached 14 µ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 · 21Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
Frequently asked questions
- How long did the Belene fire last?
- Copernicus dates it between 28 July 2026 and 28 July 2026: 1 day between the first and last image with fire.
- How much area did it burn?
- The perimeter Copernicus measured from satellite imagery is 159 hectares (1.6 km²). Official national figures may differ.
- Which municipalities burned?
- The fire only entered Belene (159 ha, 0.7 %).
- Did the fire reach a town?
- The closest fire to a town centre came within 5.4 km of Belene. That is the distance to the perimeter or nearest hotspot; it does not mean it entered the houses.
- What was the weather like?
- During the fire the temperature reached 31.6 °C, humidity dropped to 26 % and gusts hit 41 km/h. The fire danger index (FWI) reached 33, 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
Satellite cross-check
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
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.