Marvdasht fire, 23 September 2025 Eqlid, Marvdasht
The fire started on 23 September 2025 in Marvdasht, Iran, and satellites saw it burning for 4 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,202 hectares from heat detections, spread across 2 municipalities.
It is the 27th largest in Fars since 2016 (of 38 with a page). Number 16 in Iran in 2025, of 23.
Compare with…
Suggestions: Eqlid · 2025Marvdasht · 2025
- Burnt area
- 1,202ha
- GWIS perimeter (Copernicus)
- Duration
- 4days
- 23 Sept 2025 – 26 Sept 2025
- Municipalities hit
- 2
- counties
- Started on
- 23 Sept
- 2025
- Heat detections
- 19
- in a single hotspot: 157 MW
- Danger at start
- 53
- Extreme · FWI index
- Average daily power
- 124MW
- detected power per day, on average
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 more than two months without rain (1 mm or more) when it started.
This area had burned before
45% of the perimeter overlaps earlier fires recorded since 2016: 22 ha in 2016, 200 ha in 2017, 400 ha in 2021. Part of it burned more than once, so the yearly figures add up to more than the 536 ha that had burned before.
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
-
873 ha reached on 23 Sept0.1 %
-
Marvdasht where it started332 ha reached on 23 Sept0.1 %
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 2025Inside the perimeter there was no noticeable built-up land and almost nobody lived there (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
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) |
|---|---|---|---|---|---|
| 23 Sept | 24.1 °C | 6 % | 52 km/h | 0.0 mm | Extreme 53 |
| 24 Sept | 25.5 °C | 3 % | 33 km/h | 0.0 mm | Extreme 51 |
| 25 Sept | 24.8 °C | 5 % | 39 km/h | 0.0 mm | Extreme 52 |
| 26 Sept | 25.3 °C | 9 % | 38 km/h | 0.0 mm | Extreme 52 |
| 27 Sept after | 24.7 °C | 13 % | 48 km/h | 0.0 mm | Extreme 52 |
| 28 Sept after | 24.6 °C | 11 % | 41 km/h | 0.0 mm | Very high 49 |
| 29 Sept after | 25.7 °C | 9 % | 27 km/h | 0.0 mm | Very high 43 |
| 30 Sept after | 26.0 °C | 9 % | 33 km/h | 0.0 mm | Very high 46 |
| 1 Oct after | 25.3 °C | 10 % | 43 km/h | 0.0 mm | Very high 50 |
| 2 Oct after | 24.7 °C | 9 % | 47 km/h | 0.0 mm | Extreme 51 |
| 3 Oct after | 24.4 °C | 10 % | 39 km/h | 0.0 mm | Very high 48 |
| 4 Oct after | 25.6 °C | 9 % | 32 km/h | 0.0 mm | Very high 46 |
| 5 Oct after | 25.0 °C | 9 % | 22 km/h | 0.0 mm | Very high 43 |
| 6 Oct after | 25.4 °C | 11 % | 24 km/h | 0.0 mm | Very high 44 |
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 24 September 2025 the air beside the fire reached 24 µg/m³ of PM2.5. That day averaged 18: 1.2 times the WHO daily 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 · 19Every 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 Marvdasht fire last?
- GWIS (Copernicus) dates it between 23 September 2025 and 26 September 2025: 4 days between the first and last heat detection of the perimeter.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 1,202 hectares (12.0 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Eqlid (873 ha, 0.1 %); Marvdasht (332 ha, 0.1 %).
- What was the weather like?
- During the fire the temperature reached 25.5 °C, humidity dropped to 3 % and gusts hit 52 km/h. The fire danger index (FWI) reached 53, class Extreme.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Iran (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: 125 · 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: GWIS (Copernicus), rebuilt from heat detections rather than mapped on imagery.
- Dates from the perimeter: the VIIRS detections inside it did not change them. 19 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 2025, 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 (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 from each country’s official figure.