Burned area
satellite only5,090ha
Perimeter published by GWIS (Copernicus).
- Source
- GWIS (Copernicus)
- Date
- 4 Nov 2026 – 14 Nov 2026
+− cross-check
No official record is matched to this page to compare it with.
IN · India · –
Babai fire, November 2026 Babai, Budni
Dying down · last detection 14 Nov 2026, 08:26 UTC
The fire started on 4 November 2026 in Babai, India, and satellites saw it burning for 11 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 5,090 hectares from heat detections, spread across 2 municipalities.
Number 62 in India in 2026, of 63.
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.
The power measured by the satellite is low (15.5 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.
Use this data
Compare with…
Suggestions: Babai · 2025Babai · 2023Babai · 2020Babai · 2019
Use this data
Fire page data · version 2026-11-14matches 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 only11days
From 4 Nov 2026 to today: still being detected.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- last detection: 14 Nov 2026, 08:26 UTC
+− 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 only4 Nov 2026
First day with fire seen by the satellites or the perimeter.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- 4 Nov 2026
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
Hotspots
satellite only129
VIIRS detections at 375 m. Most intense hotspot: 15 MW.
- Source
- NASA FIRMS · VIIRS (NOAA-20)
- Date
- 4 Nov 2026 – 14 Nov 2026
+− cross-check
There is no official record to compare with. Each hotspot is a pixel detected in one satellite pass, not a separate fire.
The worst day
satellite only194MW
Total radiative power on 10 November 2026; hotspots that day: 32.
- Source
- NASA FIRMS · VIIRS (FRP)
- Date
- 10 Nov 2026
+− cross-check
Fire radiative power (FRP) measures the energy the fire gives off when the satellite passes. Added up by day, it compares intensity, not area.
Danger at the start
model25.9FWI · high
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 5.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 4 Nov 2026, local noon
- Model
- ECMWF IFS 0,25° · Open-Meteo.com · provisional
+− 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
model31.7°C · 28% RH
High of 31.7 °C and minimum humidity of 28% on 8 November 2026; gusts of 24 km/h on 5 November 2026.
- Source
- weather model at the fire’s grid cell
- Date
- 4 Nov 2026 – 14 Nov 2026
- Model
- ECMWF IFS 0,25° · Open-Meteo.com · provisional
+− 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 14 November 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
-
logPage published (5,090 ha).
-
· reconstructed weatherWeather and FWI computed from the forecast (provisional until ERA5 arrives)
What was saved on 14 November 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
- 5,090 ha
- Dates
- 4 Nov 2026 – ongoing
- Name
- Babai
- Official record
- —
Versioned permanent link
https://worldfires.org/en/fire/babai-2026-11?v=2026-11-14A 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 babai-2026-11.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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2026-11-04 | 1 | 2 | 30.4 | 19.6 | 36 | 9.5 | 23.8 | 0 | 25.9 | alto | 1 |
| 2026-11-05 | 0 | 0 | 30.5 | 17.3 | 28 | 11.1 | 24.5 | 0 | 30.5 | alto | 1 |
| 2026-11-06 | 3 | 10 | 31 | 17.5 | 30 | 8.1 | 19.8 | 0 | 27.1 | alto | 1 |
| 2026-11-07 | 4 | 36 | 31.5 | 18.3 | 30 | 5.5 | 18.4 | 0 | 25 | alto | 1 |
| 2026-11-08 | 5 | 44 | 31.7 | 18.7 | 28 | 9.2 | 21.6 | 0 | 26.1 | alto | 1 |
| 2026-11-09 | 29 | 175 | 31.3 | 17.8 | 30 | 6.2 | 18 | 0 | 27.9 | alto | 1 |
| 2026-11-10 | 32 | 194 | 30.8 | 17.7 | 32 | 5 | 19.1 | 0 | 28.7 | alto | 1 |
| 2026-11-11 | 8 | 30 | 30.3 | 17.7 | 31 | 7.4 | 20.2 | 0 | 28.5 | alto | 1 |
| 2026-11-12 | 13 | 64 | 29.4 | 16.7 | 32 | 8.9 | 20.9 | 0 | 31 | alto | 1 |
| 2026-11-13 | 16 | 57 | 30 | 16.4 | 35 | 7.9 | 17.6 | 0 | 27.9 | alto | 1 |
| 2026-11-14 | 18 | 95 | 30.6 | 17.8 | 30 | 6.3 | 17.3 | 0 | 28.6 | alto | 1 |
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: GWIS (Copernicus), NASA FIRMS (VIIRS), ECMWF IFS · Open-Meteo.com (CC BY 4.0). Open-Meteo.com · How we build fire pages: methodology
Is it still active?
No detections since 14 Nov 2026, 08:26 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.
- Burnt area
- 5,090ha
- GWIS perimeter (Copernicus)
- Duration
- 11days
- 4 Nov 2026 – 14 Nov 2026
- Municipalities hit
- 2
- subdistricts
- Started on
- 4 Nov
- 2026
- Heat detections
- 129
- in a single hotspot: 15 MW
- Danger at start
- 26
- High · FWI index
- Average daily power
- 70MW
- detected power per day, on average
Where it burned
HOTSPOTS BY DAY
4 Nov14 Nov
14 Nov 2026
How it evolved, day by day
4 Nov
7 Nov
10 Nov
13 Nov
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
32°high
24km/h · peak gust
28%lowest humidity
It had gone 5 days without rain (1 mm or more) when it started.
This area had burned before
100% of the perimeter overlaps earlier fires recorded since 2016: 2,911 ha in 2016, 2,057 ha in 2017, 1,975 ha in 2018, 3,812 ha in 2019, 4,435 ha in 2020, 5,001 ha in 2021, 2,623 ha in 2022, 4,482 ha in 2023, 3,532 ha in 2024, 4,638 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 5,093 ha that had burned before.
- 4,008 ha Babai fire, November 2025 10,153 ha in total; the hectares shown are those it shares with this fire
- 3,390 ha Babai fire, April 2023 6,770 ha in total; the hectares shown are those it shares with this fire
- 3,152 ha Babai fire, April 2020 59,045 ha in total; the hectares shown are those it shares with this fire
- 3,010 ha Babai fire, April 2019 7,152 ha in total; the hectares shown are those it shares with this fire
- 928 ha Babai fire, April 2021 21,633 ha in total; the hectares shown are those it shares with this fire
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
-
Babai where it started5,113 ha reached on 4 Nov8.2 %
-
3 ha0.0 %
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) |
|---|---|---|---|---|---|
| 4 Nov | 30.4 °C | 36 % | 24 km/h | 0.0 mm | High 26 |
| 5 Nov | 30.5 °C | 28 % | 24 km/h | 0.0 mm | High 30 |
| 6 Nov | 31.0 °C | 30 % | 20 km/h | 0.0 mm | High 27 |
| 7 Nov | 31.5 °C | 30 % | 18 km/h | 0.0 mm | High 25 |
| 8 Nov | 31.7 °C | 28 % | 22 km/h | 0.0 mm | High 26 |
| 9 Nov | 31.3 °C | 30 % | 18 km/h | 0.0 mm | High 28 |
| 10 Nov | 30.8 °C | 32 % | 19 km/h | 0.0 mm | High 29 |
| 11 Nov | 30.3 °C | 31 % | 20 km/h | 0.0 mm | High 28 |
| 12 Nov | 29.4 °C | 32 % | 21 km/h | 0.0 mm | High 31 |
| 13 Nov | 30.0 °C | 35 % | 18 km/h | 0.0 mm | High 28 |
| 14 Nov | 30.6 °C | 30 % | 17 km/h | 0.0 mm | High 29 |
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
↔
Before · 28 Oct 2026
After · 14 Nov 2026
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 8 November 2026 the air beside the fire reached 98 µg/m³ of PM2.5. That day averaged 56: 3.7 times the WHO daily guideline (15).
PM2.5 peak98 µg/m³
Days over the guideline12 days
PM10112 µg/m³
Optical depth0.75
WHO 15
2 Nov5 Nov8 Nov11 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)
Detections table · 129Every 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
Frequently asked questions
- How long did the Babai fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 4 November 2026 to 14 November 2026 (11 days). The perimeter dates it from 7 November 2026 to 13 November 2026.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 5,090 hectares (50.9 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Babai (5,113 ha, 8.2 %); Budni (3 ha, 0.0 %).
- Is the Babai fire still active?
- No fire detections since 14 Nov 2026, 08:26 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 28 % and gusts hit 24 km/h. The fire danger index (FWI) reached 31, class High.
- 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 · 1 Changes in area, dates, name, official record or merged pages, compared every night since 14 November 2026.
- Page published (5,090 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
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 7 November 2026 to 13 November 2026. 129 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.
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.