How long did the Kamoke fire last?

GWIS (Copernicus) dates it between 7 May 2026 and 10 May 2026: 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,067 hectares (10.7 km²). It is an estimate: official national figures may differ.

Which municipalities burned?

The fire only entered Kamoke (1,071 ha, 1.6 %).

What was the weather like?

During the fire the temperature reached 38.7 °C, humidity dropped to 27 % and gusts hit 29 km/h. The fire danger index (FWI) reached 28, class High.

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.

PK · Pakistan · 2026-05-07 → 2026-05-10

Kamoke fire, May 2026 Kamoke

Out · last detection 10 May 2026, 08:49 UTC

The fire started on 7 May 2026 in Kamoke, Pakistan, and satellites saw it burning for 4 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,067 hectares from heat detections, spread across a single municipality.

It is the 42th largest in Punjab since 2016 (of 49 with a page). Number 9 in Pakistan in 2026, of 10.

The power measured by the satellite is low (22.5 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: Kamoke · 2017 Gujranwala · 2026 Muridke · 2019

Burnt area: 1,067ha; GWIS perimeter (Copernicus)
Duration: 4days; 7 May 2026 – 10 May 2026
Municipalities hit: 1; subdistricts
Started on: 7 May; 2026
Heat detections: 15; in a single hotspot: 23 MW
Danger at start: 23; High · FWI index
Average daily power: 29MW; detected power per day, on average

HOTSPOTS BY DAY 7 May10 May

Play back 10 May 2026

How it evolved, day by day

7 May 9 May 10 May

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

The weather it burned in

39°high

29km/h · peak gust

27%lowest humidity

It had gone one day without rain (1 mm or more) when it started. Rain came after the fire: 2.3 mm on 11 May.

This area had burned before

87% of the perimeter overlaps earlier fires recorded since 2016: 818 ha in 2017, 268 ha in 2018, 226 ha in 2019, 550 ha in 2020, 68 ha in 2022, 255 ha in 2023, 186 ha in 2024. Part of it burned more than once, so the yearly figures add up to more than the 932 ha that had burned before.

745 ha Kamoke fire, May 2017 1,168 ha in total; the hectares shown are those it shares with this fire

How big is it?

It burned the equivalent of 0.7% of the area of London (11 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

Kamoke where it started

1,071 ha reached on 7 May

1.6 %

Burnt area inside each municipality, from crossing the GWIS 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.

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)
7 May	36.3 °C	29 %	29 km/h	0.0 mm	High 23
8 May	35.3 °C	32 %	27 km/h	0.0 mm	High 24
9 May	37.7 °C	29 %	20 km/h	0.0 mm	High 23
10 May	38.7 °C	27 %	24 km/h	0.0 mm	High 28
11 May after	33.6 °C	44 %	27 km/h	2.3 mm	Low 10

Before and after, from space

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

↔

Before · 30 Apr 2026

After · 17 May 2026

Before After

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 10 May 2026 the air beside the fire reached 98 µg/m³ of PM2.5. That day averaged 75: 5.0 times the WHO daily guideline (15).

PM2.5 peak98 µg/m³

Days over the guideline9 days

PM10465 µg/m³

Optical depth1.24

WHO 15

5678910111213

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 · 15Every 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 time	Satellite	FRP (MW)	Lat	Lon

Other fires nearby

All fires in Pakistan ›

Frequently asked questions

How long did the Kamoke fire last?: GWIS (Copernicus) dates it between 7 May 2026 and 10 May 2026: 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,067 hectares (10.7 km²). It is an estimate: official national figures may differ.
Which municipalities burned?: The fire only entered Kamoke (1,071 ha, 1.6 %).
What was the weather like?: During the fire the temperature reached 38.7 °C, humidity dropped to 27 % and gusts hit 29 km/h. The fire danger index (FWI) reached 28, class High.
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

Satellite cross-check

NASA FIRMS ↗
GWIS · Copernicus ↗

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?

Dates or duration Place or towns Burned area Name It was not a wildfire Same fire as another page Something else

What really happened?

Your connection to the fire (optional) Email (optional)

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 1122 · 16.

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. 15 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.

How we build fire pages: methodology ›

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.

Where it burned