Depalpur fire, 25 October 2026 Depalpur, Chunian
Satellites first detected fire on 25 October 2026 in Depalpur, Pakistan. It has been active for 10 days, with 133 heat detections and an area with fire of about 1,736 hectares rebuilt from them, spread across 2 municipalities.
The power measured by the satellite is low (25.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…
Suggestions: Depalpur · 2026Fazilka · 2017Fazilka · 2021
GWIS (Copernicus) has not yet published the perimeter of this fire. It rebuilds it from hotspots, which can take several days, and it does not always arrive. For now the area is the one rebuilt from heat detections (about 14 hectares per pixel). If the perimeter arrives, this page picks it up on its own and keeps the same address.
Is it still active?
No detections since 3 Nov 2026, 08:34 UTC. That usually means no flame is visible from space any more, although hotspots may remain. 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.
- Area with fire
- ≈ 1,736ha
- rebuilt from hotspots, no official perimeter yet
- Duration
- 10days
- 25 Oct 2026 – 3 Nov 2026
- Municipalities hit
- 2
- subdistricts
- Started on
- 25 Oct
- 2026
- Heat detections
- 133
- in a single hotspot: 25 MW
- Danger at start
- 16
- Moderate · FWI index
- Average daily power
- 90MW
- 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 0 days without rain (1 mm or more) when it started.
What happened to each town
-
Depalpur where it started1,694 ha reached on 25 Oct0.7 %
-
42 ha reached on 29 Oct0.0 %
Area with fire inside each municipality, rebuilt from heat detections (about 14 hectares per VIIRS pixel). An estimate until the official perimeter arrives. 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.
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) · forecast models, provisional until the ERA5 reanalysis arrives
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 24 Oct | 30.3 °C | 30 % | 32 km/h | 0.6 mm | Moderate 16 |
| 25 Oct | 27.8 °C | 42 % | 22 km/h | 0.0 mm | Moderate 14 |
| 26 Oct | 28.5 °C | 41 % | 18 km/h | 0.0 mm | Moderate 14 |
| 27 Oct | 29.1 °C | 39 % | 16 km/h | 0.0 mm | Moderate 14 |
| 28 Oct | 29.0 °C | 39 % | 19 km/h | 0.0 mm | Moderate 15 |
| 29 Oct | 29.3 °C | 29 % | 18 km/h | 0.0 mm | Moderate 18 |
| 30 Oct | 27.3 °C | 51 % | 23 km/h | 0.1 mm | Moderate 15 |
| 31 Oct | 29.1 °C | 40 % | 17 km/h | 0.0 mm | Moderate 14 |
| 1 Nov | 28.5 °C | 43 % | 15 km/h | 0.0 mm | Moderate 14 |
| 2 Nov | 29.2 °C | 45 % | 16 km/h | 0.0 mm | Moderate 16 |
| 3 Nov | 29.0 °C | 43 % | 18 km/h | 0.0 mm | Moderate 16 |
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 10 October 2026 the air beside the fire reached 162 µg/m³ of PM2.5. That day averaged 105: 7.0 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 · 133Every 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 Depalpur fire last?
- According to the heat detections seen by satellite, it burned from 25 October 2026 to 3 November 2026 (10 days between the first and the last detection). There is no perimeter yet to date it.
- How much area did it burn?
- There is no perimeter yet. Heat detections rebuild about 1,736 hectares with fire (17.4 km²), a rough figure; GWIS will give its own when it publishes the perimeter, which can take several days.
- Which municipalities burned?
- The fire entered 2 municipalities: Depalpur (1,694 ha, 0.7 %); Chunian (42 ha, 0.0 %).
- Is the Depalpur fire still active?
- No fire detections since 3 Nov 2026, 08:34 UTC. A lack of detections is not an official extinction.
- What was the weather like?
- During the fire the temperature reached 30.3 °C, humidity dropped to 29 % and gusts hit 32 km/h. The fire danger index (FWI) reached 18, class Moderate.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Pakistan (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: 1122 · 16 · Emergency number and official warnings ›
Satellite cross-check
History of this page · 28 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
- Area: ≈ 2,646 → ≈ 1,792 ha.
- Start date: 23 October 2026 → 24 October 2026.
- Area: ≈ 3,304 → ≈ 2,646 ha.
- Start date: 22 October 2026 → 23 October 2026.
- Area: ≈ 2,296 → ≈ 3,304 ha.
- Start date: 21 October 2026 → 22 October 2026.
- The page “Depalpur, 19 October 2026” has been merged into this one: it was the same fire.
- Area: ≈ 2,184 → ≈ 2,296 ha.
- Start date: 20 October 2026 → 21 October 2026.
- Last day with fire: 24 October 2026 → 28 October 2026.
- Area: ≈ 1,904 → ≈ 2,184 ha.
- Start date: 19 October 2026 → 20 October 2026.
- Area: ≈ 1,400 → ≈ 1,904 ha.
- Start date: 18 October 2026 → 19 October 2026.
- Area: ≈ 1,092 → ≈ 1,148 ha.
- Start date: 18 October 2026 → 19 October 2026.
- Area: ≈ 1,484 → ≈ 1,400 ha.
- Start date: 17 October 2026 → 18 October 2026.
- Area: ≈ 1,246 → ≈ 1,092 ha.
- Start date: 17 October 2026 → 18 October 2026.
- Area: ≈ 1,358 → ≈ 1,484 ha.
- Start date: 16 October 2026 → 17 October 2026.
- Area: ≈ 1,204 → ≈ 1,246 ha.
- Start date: 16 October 2026 → 17 October 2026.
- Area: ≈ 1,302 → ≈ 1,358 ha.
- Start date: 15 October 2026 → 16 October 2026.
- Area: ≈ 1,148 → ≈ 1,204 ha.
- Start date: 15 October 2026 → 16 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
- No perimeter yet: the area (≈ 1,736 ha) is estimated by counting VIIRS pixels with fire, about 14 ha each.
- Dates of the first and last VIIRS detection of the cluster. 133 Suomi-NPP VIIRS detections on those dates.
- Weather: ECMWF IFS model, provisional until the ERA5 reanalysis arrives.
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 ADM3 (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.