Skip to content
worldfires
IN · India · –

Bhander fire, November 2026 Seondha, Bhander, Lahar

Dying down · last detection 17 Nov 2026, 08:13 UTC

The fire started on 2 November 2026 in Bhander, India, and satellites saw it burning for 16 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 11,251 hectares from heat detections, spread across 4 municipalities.

Number 14 in India in 2026, of 64.

GWIS near-real-time perimeter, from the layer that changed in October 2025: this fire is not compared with fires from earlier years, because since then the GWIS layer gives more and larger perimeters.

Compare with…

Suggestions: Bhander · 2025

Is it still active?

No detections since 17 Nov 2026, 08:13 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.

Wind, humidity and rain for the next 72 h

Burnt area
11,251ha
GWIS perimeter (Copernicus)
Duration
16days
2 Nov 2026 – 17 Nov 2026
Municipalities hit
4
subdistricts
Started on
2 Nov
2026
Heat detections
326
in a single hotspot: 37 MW
Danger at start
23
High · FWI index
Average daily power
121MW
detected power per day, on average

The next 72 hours

The wind is blowing from the north-east and pushing to the south-west; no sharp shifts are expected until Sat 21, 01:00.

ECMWF IFS 0.25° at the centre of the fire · computed 17 Nov 2026, 20:25 UTC

No sharp changes in the next 72 h

No strong wind shifts and no dry nights. No warnings does not mean the fire will go out: in this weather it can carry on as it is.

Checked, no warning: no wind shifts of more than 60° nights recover humidity (peaks of 73 % or more) no useful rain expected (0.0 mm in 72 h)

Hour by hour, local time

Tap the strip to see each hour

Mean wind Gusts where it blows to Relative humidity Night (8 pm to 8 am) Rain (mm) · chance in %

Where is it blowing? The next 48 h

geoBoundaries/Pathways Data Pvt. Ltd., lgdirectory.gov.in (Open Data Commons Open Database License 1.0)

At this hour

Places the fan reaches

    Is it heading my way?

    We compare your point with the fan for each hour. Your location never leaves your device.

    or tap the map

    This is not an official warning. It is a global model forecast with cells of about 25 km, at the centre of the fire: it cannot see valley winds or the winds the fire itself creates. The fan shows where the wind blows, not where the fire will spread. If in doubt, follow what the authorities say.

    Emergencies · India 112 Emergency number and official warnings

    Forecast: ECMWF IFS 0.25° (European Centre for Medium-Range Weather Forecasts), served by our own Open-Meteo instance; the chance of rain comes from the ECMWF ensemble. Variables: wind and gusts at 10 m, wind at 850 hPa, relative humidity and temperature at 2 m, rain. Open-Meteo.com (CC BY 4.0).

    Fire: GWIS / Copernicus (reconstructed from VIIRS) (CC BY 4.0); hotspots from the last 24 h: VIIRS from NASA FIRMS. Boundaries: geoBoundaries/Pathways Data Pvt. Ltd., lgdirectory.gov.in (Open Data Commons Open Database License 1.0).

    How it is worked out: wind shift = a change of more than 60° in 6 h or less, with at least 15 km/h before and after; no overnight recovery = peak humidity between 8 pm and 8 am stays below 55 %; useful rain = 2 mm or more in 6 h. The fan opens 18° plus however much the wind varies within ±3 h and reaches 25 km beyond the edge of the fire: one model cell, not a rate of spread. Methodology

    Where it burned

    HOTSPOTS BY DAY 2 Nov17 Nov
    17 Nov 2026

    How it evolved, day by day

    2 Nov 2026 · 0 MW · 0 3 Nov 2026 · 8 MW · 2 4 Nov 2026 · 22 MW · 5 5 Nov 2026 · 59 MW · 10 6 Nov 2026 · 81 MW · 15 7 Nov 2026 · 102 MW · 17 8 Nov 2026 · 51 MW · 13 9 Nov 2026 · 221 MW · 34 10 Nov 2026 · 118 MW · 28 11 Nov 2026 · 55 MW · 11 12 Nov 2026 · 130 MW · 15 13 Nov 2026 · 165 MW · 25 14 Nov 2026 · 189 MW · 33 15 Nov 2026 · 241 MW · 41 16 Nov 2026 · 217 MW · 45 17 Nov 2026 · 152 MW · 32
    2 Nov 6 Nov 10 Nov 15 Nov

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

    Fire front film How it spread from one satellite pass to the next (35 passes) and with what wind. Watch the film

    The weather it burned in

    32°high
    26km/h · peak gust
    25%lowest humidity

    It had gone 2 days without rain (1 mm or more) when it started.

    This area had burned before

    55% of the perimeter overlaps earlier fires recorded since 2016: 860 ha in 2016, 1,623 ha in 2017, 1,079 ha in 2018, 2,408 ha in 2019, 3,767 ha in 2020, 3,735 ha in 2021, 3,505 ha in 2022, 2,222 ha in 2023, 4,111 ha in 2024, 6,881 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 6,133 ha that had burned before.

    How big is it?

    10 km
    It burned the equivalent of 7.1% of the area of London (113 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

    1. 10,026 ha reached on 2 Nov
      22 %
    2. Bhander where it started
      969 ha reached on 5 Nov
      1.5 %
    3. 225 ha reached on 3 Nov
      0.4 %
    4. 73 ha reached on 9 Nov
      0.2 %

    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.

    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)
    2 Nov 30.2 °C 40 % 19 km/h 0.0 mm High 23
    3 Nov 30.8 °C 30 % 23 km/h 0.0 mm High 32
    4 Nov 31.4 °C 28 % 22 km/h 0.0 mm High 32
    5 Nov 31.5 °C 30 % 26 km/h 0.0 mm High 34
    6 Nov 31.5 °C 36 % 22 km/h 0.0 mm High 33
    7 Nov 31.5 °C 29 % 21 km/h 0.0 mm High 32
    8 Nov 31.4 °C 31 % 15 km/h 0.0 mm High 28
    9 Nov 30.3 °C 36 % 18 km/h 0.0 mm High 27
    10 Nov 29.8 °C 34 % 22 km/h 0.0 mm High 32
    11 Nov 29.8 °C 30 % 14 km/h 0.0 mm High 28
    12 Nov 30.4 °C 30 % 19 km/h 0.0 mm High 31
    13 Nov 31.7 °C 30 % 20 km/h 0.0 mm High 34
    14 Nov 31.6 °C 30 % 22 km/h 0.0 mm High 35
    15 Nov 31.3 °C 30 % 24 km/h 0.0 mm High 37
    16 Nov 29.6 °C 25 % 26 km/h 0.0 mm Very high 45
    17 Nov 28.4 °C 29 % 18 km/h 0.0 mm High 33

    Before and after, from space

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

    Before · 26 Oct 2026
    After · 16 Nov 2026

    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 6 November 2026 the air beside the fire reached 120 µg/m³ of PM2.5. That day averaged 102: 6.8 times the WHO daily guideline (15).

    PM2.5 peak120 µg/m³
    Days over the guideline14 days
    PM10248 µg/m³
    Optical depth0.94
    31 Oct3 Nov6 Nov9 Nov12 Nov
    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)

    Cities with smoke from this fire

    According to the CAMS forecast and the wind at 850 hPa, this fire is today the most likely main source of smoke in:

    1. 58 µg Smoke today in Jalaun ×3.8 the WHO guideline today · 38 % of the upwind weight · 63 km away
    2. 52 µg Smoke today in Lahar ×3.4 the WHO guideline today · 37 % of the upwind weight · 13 km away

    An estimate without a dispersion model, based on a model forecast: not a measurement.

    Detections table · 326Every 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 timeSatelliteFRP (MW)LatLon

    Other fires nearby

    All fires in India

    Frequently asked questions

    How long did the Bhander fire last?
    According to the heat detections seen by satellite inside the perimeter, it burned from 2 November 2026 to 17 November 2026 (16 days). The perimeter dates it from 4 November 2026 to 16 November 2026.
    How much area did it burn?
    The perimeter GWIS (Copernicus) rebuilt from heat detections is 11,251 hectares (112.5 km²). It is an estimate: official national figures may differ.
    Which municipalities burned?
    The fire entered 4 municipalities: Seondha (10,026 ha, 22 %); Bhander (969 ha, 1.5 %); Lahar (225 ha, 0.4 %); Indergarh (73 ha, 0.2 %).
    Is the Bhander fire still active?
    No fire detections since 17 Nov 2026, 08:13 UTC. A lack of detections is not an official extinction.
    What was the weather like?
    During the fire the temperature reached 31.7 °C, humidity dropped to 25 % and gusts hit 26 km/h. The fire danger index (FWI) reached 45, class Very high.
    What weather is expected at the fire over the next 72 hours?
    The wind is blowing from the north-east and pushing to the south-west; no sharp shifts are expected until Sat 21, 01:00. No strong wind shifts, dry nights or useful rain are expected. Times are local time at the fire. ECMWF IFS forecast (Open-Meteo) computed 17 Nov 2026, 20:25 UTC; this is not an official warning.
    Where does this data come from?
    From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of India (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 · Emergency number and official warnings

    Satellite cross-check

    History of this page · 5 Changes in area, dates, name, official record or merged pages, compared every night since 14 November 2026.
    1. Area: 8,971 → 11,251 ha.
    2. Name: Seondha → Bhander.
    3. Area: 7,148 → 8,971 ha.
    4. Area: 6,133 → 7,148 ha.
    5. Page published (6,133 ha).

    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
    What do you think is wrong?

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

    How we know this
    • Perimeter: GWIS (Copernicus), rebuilt from heat detections rather than mapped on imagery.
    • Dates adjusted with the VIIRS detections inside the perimeter, which said 4 November 2026 to 16 November 2026. 326 Suomi-NPP VIIRS detections on those dates.
    • We have not matched this page with any official record.
    • Weather: ECMWF IFS model, provisional until the ERA5 reanalysis arrives.

    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.