Burned area
satellite only313ha
Perimeter published by EFFIS (Copernicus).
- Source
- EFFIS (Copernicus)
- Date
- perimeter revised on 26 January 2022
+− cross-check
No official record is matched to this page to compare it with.
TR · Türkiye · –
Bolvadin fire, 27 January 2020 Bolvadin
Out · last measured on 30 Jan 2020
The fire started on 27 January 2020 in Bolvadin, Türkiye, and satellites saw it burning for 4 days. Copernicus mapped a burnt perimeter of 313 hectares from satellite imagery, spread across a single municipality.
It is the 12th largest in Afyonkarahisar since 2016 (of 41 with a page). Number 78 in Türkiye in 2020, of 212.
Use this data
Compare with…
Use this data
Fire page data · version 2026-10-24matches 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 only4days
27 Jan 2020 to 30 Jan 2020: first and last day with fire on the page.
- Source
- EFFIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- 27 Jan 2020 – 30 Jan 2020
+− 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 only27 Jan 2020
First day with fire seen by the satellites or the perimeter.
- Source
- EFFIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- 27 Jan 2020
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
Danger at the start
model0.8FWI · very low
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 17.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 27 Jan 2020, 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
model10.4°C · 44% RH
High of 10.4 °C and minimum humidity of 44% on 27 January 2020; gusts of 52 km/h on 30 January 2020.
- Source
- weather model at the fire’s grid cell
- Date
- 27 Jan 2020 – 30 Jan 2020
- 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.
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 GHSLPopulation and built-up area computed
-
· reconstructed weatherWeather and FWI computed from the ERA5 reanalysis
-
· reconstructed perimeterEFFIS (Copernicus) revises the perimeter
What was saved on 24 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
- 313 ha
- Dates
- 27 Jan 2020 – 30 Jan 2020
- Name
- Bolvadin
- Official record
- —
Versioned permanent link
https://worldfires.org/en/fire/bolvadin-2020-01-2?v=2026-10-24A 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 bolvadin-2020-01-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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2020-01-27 | 0 | 0 | 10.4 | 0 | 44 | 8.3 | 18.7 | 0 | 0.8 | muy_bajo | 1 |
| 2020-01-28 | 0 | 0 | 7.8 | 1.9 | 74 | 8.4 | 27 | 1.6 | 0.2 | muy_bajo | 1 |
| 2020-01-29 | 0 | 0 | 10.3 | 2 | 51 | 19.3 | 41.4 | 0 | 0.5 | muy_bajo | 1 |
| 2020-01-30 | 0 | 0 | 9 | 1.9 | 76 | 16.6 | 51.8 | 9.3 | 0 | muy_bajo | 1 |
| 2020-01-31 | 0 | 0 | 4.4 | -0.7 | 50 | 18.3 | 40.3 | 0 | 0.1 | muy_bajo | 0 |
| 2020-02-01 | 0 | 0 | 8 | 0.2 | 66 | 12.3 | 29.2 | 0 | 0.2 | muy_bajo | 0 |
| 2020-02-02 | 0 | 0 | 12.8 | 2.3 | 47 | 10.7 | 24.5 | 0 | 0.3 | muy_bajo | 0 |
| 2020-02-03 | 0 | 0 | 12.8 | 2.9 | 49 | 22.1 | 50 | 0 | 0.9 | muy_bajo | 0 |
| 2020-02-04 | 0 | 0 | 13 | 7.1 | 54 | 18.6 | 41.4 | 0 | 1 | muy_bajo | 0 |
| 2020-02-05 | 0 | 0 | 15.1 | 8.2 | 51 | 34.3 | 75.2 | 0.1 | 4.1 | muy_bajo | 0 |
| 2020-02-06 | 0 | 0 | 10.3 | 2.1 | 70 | 23.6 | 80.6 | 26.8 | 0 | muy_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: EFFIS (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
We have the Copernicus perimeter for this fire, but the VIIRS sensors did not capture it in enough detail: no day-by-day evolution, but the split by municipality is there.
- Burnt area
- 313ha
- Copernicus perimeter
- Duration
- 4days
- 27 Jan 2020 – 30 Jan 2020
- Municipalities hit
- 1
- districts
- Started on
- 27 Jan
- 2020
- Danger at start
- 1
- Very low · FWI index
Where it burned
The weather it burned in
10°high
52km/h · peak gust
44%lowest humidity
It had gone 17 days without rain (1 mm or more) when it started. Rain came after the fire: 26.8 mm on 6 Feb.
This area had burned before
28% of the perimeter overlaps earlier fires recorded since 2016: 87 ha in 2017, 27 ha in 2018. Part of it burned more than once, so the yearly figures add up to more than the 87 ha that had burned before.
What happened to each town
-
313 ha reached on 21 Jan0.3 %
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
- Other land cover98 %
- Other natural land1.6 %
Land cover inside the perimeter according to Corine Land Cover, as reported by Copernicus.
People and buildings inside the perimeter
GHSL 2020Built-up area< 0.1 ha
Residents< 20
Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2020, 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) |
|---|---|---|---|---|---|
| 27 Jan | 10.4 °C | 44 % | 19 km/h | 0.0 mm | Very low 1 |
| 28 Jan | 7.8 °C | 74 % | 27 km/h | 1.6 mm | Very low 0 |
| 29 Jan | 10.3 °C | 51 % | 41 km/h | 0.0 mm | Very low 0 |
| 30 Jan | 9.0 °C | 76 % | 52 km/h | 9.3 mm | Very low 0 |
| 31 Jan after | 4.4 °C | 50 % | 40 km/h | 0.0 mm | Very low 0 |
| 1 Feb after | 8.0 °C | 66 % | 29 km/h | 0.0 mm | Very low 0 |
| 2 Feb after | 12.8 °C | 47 % | 24 km/h | 0.0 mm | Very low 0 |
| 3 Feb after | 12.8 °C | 49 % | 50 km/h | 0.0 mm | Very low 1 |
| 4 Feb after | 13.0 °C | 54 % | 41 km/h | 0.0 mm | Very low 1 |
| 5 Feb after | 15.1 °C | 51 % | 75 km/h | 0.1 mm | Very low 4 |
| 6 Feb after | 10.3 °C | 70 % | 81 km/h | 26.8 mm | Very low 0 |
Its twins: fires that started in the same weather
It started with an FWI of 0.8, a minimum humidity of 44% and 17 days without rain. Fires in the area that started in weather like this since 2016: 18.
FWI at the start
0.8
Minimum humidity
44 %
Days without rain
17
this fire
chosen twins
rest of the area
Almost identicalSimilar
Outlines of the closest twins
This fire · Bolvadin fire, 27 January 2020
313 ha
4 days
FWI 0.8
Min. humidity 44 %
Çay fire, March 2018
219 ha
1 day
FWI 1.8
Min. humidity 45 %
8 km away, in 2018
First rain (1 mm or more) after it ended: 3.6 mm on 8 Mar.
Bolvadin fire, February 2024
311 ha
1 day
FWI 2.9
Min. humidity 39 %
4 km away, in 2024
First rain (1 mm or more) after it ended: 6.4 mm on 5 Mar.
Sivrihisar fire, March 2026
142 ha
2 days
FWI 0.8
Min. humidity 39 %
68 km away, in 2026
First rain (1 mm or more) after it ended: none in the following ten days.
Eskil fire, October 2022
106 ha
2 days
FWI 7.0
Min. humidity 44 %
194 km away, in 2022
First rain (1 mm or more) after it ended: none in the following ten days.
Akşehir fire, December 2023
328 ha
1 day
FWI 1.9
Min. humidity 50 %
32 km away, in 2023
First rain (1 mm or more) after it ended: 3.5 mm on 2 Jan.
What happened to them
- 1 day
- median duration
- 186 ha
- median area
- 0 %
- went past 1,000 ha
- 6.2 mm
- rain at the end (median; 14 of 18 had it)
It was 1.7 times larger than the median of its twins and lasted 4 days, against 1 day.
Only 4 of its 18 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 18, 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 6.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
26.8 mmfirst rain
6 Feb7 days after it ended
52km/h · max. gust
It was considered over on 30 Jan, and on 6 Feb 26.8 mm fell. We do not know whether the rain or the firefighters put it out. Twins with rain when they ended: 14 of 18, with a median of 6.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 · 20 Jan 2020
After · 6 Feb 2020
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.
The smoke
CAMS · CopernicusOn 27 January 2020 the air beside the fire reached 25 µg/m³ of PM2.5. That day averaged 23: 1.5 times the WHO daily guideline (15).
PM2.5 peak25 µg/m³
Days over the guideline2 days
PM1039 µg/m³
WHO 15
25 Jan27 Jan29 Jan31 Jan2 Feb
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)
Other fires nearby
Frequently asked questions
- How long did the Bolvadin fire last?
- Copernicus dates it between 27 January 2020 and 30 January 2020: 4 days between the first and last image with fire.
- How much area did it burn?
- The perimeter Copernicus measured from satellite imagery is 313 hectares (3.1 km²). Official national figures may differ.
- Which municipalities burned?
- The fire only entered Bolvadin (313 ha, 0.3 %).
- Did the fire reach a town?
- The fire started in Bolvadin and came within 8.7 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 10.4 °C, humidity dropped to 44 % and gusts hit 52 km/h. The fire danger index (FWI) reached 1, class Very low.
- Where does this data come from?
- From the EFFIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Türkiye (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: 18. Their median duration was 1 day and their median area 186 ha; 0 % went past 1,000 ha. Only 4 of its 18 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 18, 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 6.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.
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.
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: EFFIS (Copernicus), mapped on satellite imagery.
- Dates from the perimeter: the VIIRS detections inside it did not change them. No 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 2020, 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 (Open Data Commons Open Database License 1.0). 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.