Burned area
satellite only81,742ha
Perimeter published by GWIS (Copernicus).
- Source
- GWIS (Copernicus)
- Date
- 17 Sept 2026 – 13 Oct 2026
+− cross-check
No official record is matched to this page to compare it with.
AU · Australia · –
Roper Gulf fire, 17 September 2026 Roper Gulf, Barkly
Out · last detection 13 Oct 2026, 16:45 UTC
The fire started on 17 September 2026 in Roper Gulf, Australia, and satellites saw it burning for 27 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 81,742 hectares from heat detections, spread across 2 municipalities.
This entry is probably a savanna fire in Australia’s tropical north, not a bushfire like those in the south of the country. Millions of hectares of northern savanna and grassland burn every year: much of it in burns lit on purpose early in the dry season (traditional fire management, parks and cattle stations), the rest in grass fires that return to the same ground every few years. This is our assumption, based on the location; it is not confirmed. That is why it is left out of the wildfire rankings.
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.
Use this data
Compare with…
Use this data
Fire page data · version 2026-10-25matches 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 only27days
17 Sept 2026 to 13 Oct 2026: first and last day with fire on the page.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- last detection: 13 Oct 2026, 16:45 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 only17 Sept 2026
First day with fire seen by the satellites or the perimeter.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- 17 Sept 2026
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
Hotspots
satellite only1,616
VIIRS detections at 375 m. Most intense hotspot: 262 MW.
- Source
- NASA FIRMS · VIIRS (Suomi NPP)
- Date
- 17 Sept 2026 – 13 Oct 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 only2,240MW
Total radiative power on 26 September 2026; hotspots that day: 209.
- Source
- NASA FIRMS · VIIRS (FRP)
- Date
- 26 Sept 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
model92.8FWI · very extreme
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 60.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 17 Sept 2026, local noon
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− 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
model39.3°C · 22% RH
High of 39.3 °C and minimum humidity of 22% on 12 October 2026; gusts of 49 km/h on 18 September 2026.
- Source
- weather model at the fire’s grid cell
- Date
- 17 Sept 2026 – 13 Oct 2026
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− 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 24 October 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
-
· reconstructed weatherWeather and FWI computed from the ERA5 reanalysis
-
· reconstructed GHSLPopulation and built-up area computed
-
logName: Barkly → Roper Gulf.
What was saved on 25 October 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
- 81,742 ha
- Dates
- 17 Sept 2026 – 13 Oct 2026
- Name
- Roper Gulf
- Official record
- —
Versioned permanent link
https://worldfires.org/en/fire/roper-gulf-2026-09-8?v=2026-10-25A 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 roper-gulf-2026-09-8.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-09-17 | 4 | 8 | 35.5 | 20 | 15 | 26.2 | 47.9 | 0 | 92.8 | muy_extremo | 1 |
| 2026-09-18 | 19 | 43 | 34.2 | 19.9 | 14 | 27.9 | 49.3 | 0 | 83.1 | muy_extremo | 1 |
| 2026-09-19 | 88 | 112 | 33.7 | 19.5 | 23 | 28.2 | 45.7 | 0 | 80.5 | muy_extremo | 1 |
| 2026-09-20 | 95 | 1,164 | 33.3 | 17.1 | 19 | 21.1 | 35.6 | 0 | 62.8 | extremo | 1 |
| 2026-09-21 | 107 | 1,101 | 33.5 | 18.3 | 17 | 22.1 | 33.8 | 0 | 68.2 | extremo | 1 |
| 2026-09-22 | 247 | 2,229 | 34.9 | 19 | 13 | 22.6 | 37.1 | 0 | 77.3 | muy_extremo | 1 |
| 2026-09-23 | 101 | 1,174 | 35.3 | 17.1 | 15 | 23.4 | 42.1 | 0 | 82.4 | muy_extremo | 1 |
| 2026-09-24 | 80 | 467 | 36.4 | 18.4 | 9 | 21.6 | 40.3 | 0 | 81.7 | muy_extremo | 1 |
| 2026-09-25 | 122 | 422 | 34.2 | 18.7 | 20 | 25.5 | 43.2 | 0 | 71.7 | muy_extremo | 1 |
| 2026-09-26 | 209 | 2,240 | 35.6 | 20.8 | 18 | 24 | 39.2 | 0 | 68.9 | extremo | 1 |
| 2026-09-27 | 48 | 138 | 35.5 | 19.5 | 19 | 19.9 | 39.2 | 0 | 68.6 | extremo | 1 |
| 2026-09-28 | 62 | 1,788 | 35.5 | 20.7 | 13 | 25.2 | 42.8 | 0 | 70.5 | muy_extremo | 1 |
| 2026-09-29 | 46 | 512 | 35.7 | 19.2 | 17 | 23.1 | 36.4 | 0 | 65.5 | extremo | 1 |
| 2026-09-30 | 47 | 471 | 32.6 | 21.4 | 32 | 22.1 | 37.1 | 0 | 52 | extremo | 1 |
| 2026-10-01 | 31 | 208 | 34.2 | 22.7 | 35 | 27 | 42.8 | 0.2 | 53.8 | extremo | 1 |
| 2026-10-02 | 38 | 346 | 35.2 | 20.7 | 20 | 22.2 | 42.8 | 0 | 75.5 | muy_extremo | 1 |
| 2026-10-03 | 25 | 40 | 36.4 | 19.9 | 16 | 22.3 | 39.6 | 0 | 74 | muy_extremo | 1 |
| 2026-10-04 | 79 | 1,218 | 35.6 | 18 | 17 | 21.9 | 40.7 | 0 | 69.2 | extremo | 1 |
| 2026-10-05 | 27 | 135 | 35.7 | 18.3 | 20 | 19.9 | 32.8 | 0 | 60 | extremo | 1 |
| 2026-10-06 | 34 | 257 | 37.8 | 19.6 | 18 | 23.7 | 38.5 | 0 | 60.2 | extremo | 1 |
| 2026-10-07 | 27 | 169 | 38.4 | 21.6 | 18 | 16.8 | 30.6 | 0 | 52 | extremo | 1 |
| 2026-10-08 | 16 | 50 | 37.7 | 23.2 | 19 | 16.9 | 30.6 | 0 | 54.5 | extremo | 1 |
| 2026-10-09 | 14 | 66 | 38.1 | 22.9 | 21 | 18.4 | 35.3 | 0 | 60 | extremo | 1 |
| 2026-10-10 | 1 | 2 | 35.8 | 25.4 | 30 | 20.5 | 35.6 | 0.1 | 44.7 | muy_alto | 1 |
| 2026-10-11 | 27 | 126 | 38.6 | 23.6 | 21 | 19.4 | 33.8 | 0 | 52.3 | extremo | 1 |
| 2026-10-12 | 22 | 202 | 39.3 | 23.5 | 22 | 23.3 | 40.3 | 0 | 48.9 | muy_alto | 1 |
| 2026-10-13 | 0 | 0 | 39.2 | 24 | 25 | 22.7 | 38.9 | 0 | 49.7 | muy_alto | 1 |
| 2026-10-14 | 0 | 0 | 35.7 | 26.1 | 38 | 15.1 | 28.8 | 1 | 38 | alto | 0 |
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), ERA5 (ECMWF/Copernicus C3S) · Open-Meteo.com (CC BY 4.0), GHSL (JRC). Open-Meteo.com · How we build fire pages: methodology
- Burnt area
- 81,742ha
- GWIS perimeter (Copernicus)
- Duration
- 27days
- 17 Sept 2026 – 13 Oct 2026
- Municipalities hit
- 2
- local government areas
- Started on
- 17 Sept
- 2026
- Heat detections
- 1,616
- in a single hotspot: 262 MW
- Danger at start
- 93
- Very extreme · FWI index
- Average daily power
- 565MW
- detected power per day, on average
Where it burned
HOTSPOTS BY DAY
17 Sept13 Oct
13 Oct 2026
How it evolved, day by day
17 Sept
26 Sept
5 Oct
11 Oct
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
49km/h · peak gust
9%lowest humidity
It had gone more than two months without rain (1 mm or more) when it started. Rain came after the fire: 1.0 mm on 14 Oct.
This area had burned before
49% of the perimeter overlaps earlier fires recorded since 2016: 971 ha in 2016, 5,075 ha in 2017, 5,984 ha in 2018, 748 ha in 2019, 1,443 ha in 2020, 5,849 ha in 2021, 11,247 ha in 2022, 9,895 ha in 2023, 9,306 ha in 2024, 1,712 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 40,134 ha that had burned before.
- 8,889 ha Roper Gulf fire, November 2022 13,266 ha in total; the hectares shown are those it shares with this fire
- 5,056 ha Roper Gulf fire, August 2018 29,238 ha in total; the hectares shown are those it shares with this fire
- 3,605 ha Barkly fire, November 2024 15,852 ha in total; the hectares shown are those it shares with this fire
- 3,024 ha Roper Gulf fire, August 2023 35,398 ha in total; the hectares shown are those it shares with this fire
- 620 ha Barkly fire, December 2017 9,125 ha in total; the hectares shown are those it shares with this fire
- 412 ha Barkly fire, November 2025 8,159 ha in total; the hectares shown are those it shares with this fire
- 79 ha Roper Gulf fire, August 2023 18,613 ha in total; the hectares shown are those it shares with this fire
- 38 ha Roper Gulf fire, August 2025 8,491 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
-
Roper Gulf where it started71,431 ha reached on 17 Sept0.4 %
-
11,186 ha reached on 18 Sept0.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.
People and buildings inside the perimeter
GHSL 2025Built-up area< 0.1 ha
Residents< 20
Inside 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)
Started with Extreme FWI: 43 % of the area in Australia 60 days without rain: 8.2 % of the area in Australia
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 17 Sept | 35.5 °C | 15 % | 48 km/h | 0.0 mm | Very extreme 93 |
| 18 Sept | 34.2 °C | 14 % | 49 km/h | 0.0 mm | Very extreme 83 |
| 19 Sept | 33.7 °C | 23 % | 46 km/h | 0.0 mm | Very extreme 80 |
| 20 Sept | 33.3 °C | 19 % | 36 km/h | 0.0 mm | Extreme 63 |
| 21 Sept | 33.5 °C | 17 % | 34 km/h | 0.0 mm | Extreme 68 |
| 22 Sept | 34.9 °C | 13 % | 37 km/h | 0.0 mm | Very extreme 77 |
| 23 Sept | 35.3 °C | 15 % | 42 km/h | 0.0 mm | Very extreme 82 |
| 24 Sept | 36.4 °C | 9 % | 40 km/h | 0.0 mm | Very extreme 82 |
| 25 Sept | 34.2 °C | 20 % | 43 km/h | 0.0 mm | Very extreme 72 |
| 26 Sept | 35.6 °C | 18 % | 39 km/h | 0.0 mm | Extreme 69 |
| 27 Sept | 35.5 °C | 19 % | 39 km/h | 0.0 mm | Extreme 69 |
| 28 Sept | 35.5 °C | 13 % | 43 km/h | 0.0 mm | Very extreme 70 |
| 29 Sept | 35.7 °C | 17 % | 36 km/h | 0.0 mm | Extreme 66 |
| 30 Sept | 32.6 °C | 32 % | 37 km/h | 0.0 mm | Extreme 52 |
| 1 Oct | 34.2 °C | 35 % | 43 km/h | 0.2 mm | Extreme 54 |
| 2 Oct | 35.2 °C | 20 % | 43 km/h | 0.0 mm | Very extreme 76 |
| 3 Oct | 36.4 °C | 16 % | 40 km/h | 0.0 mm | Very extreme 74 |
| 4 Oct | 35.6 °C | 17 % | 41 km/h | 0.0 mm | Extreme 69 |
| 5 Oct | 35.7 °C | 20 % | 33 km/h | 0.0 mm | Extreme 60 |
| 6 Oct | 37.8 °C | 18 % | 38 km/h | 0.0 mm | Extreme 60 |
| 7 Oct | 38.4 °C | 18 % | 31 km/h | 0.0 mm | Extreme 52 |
| 8 Oct | 37.7 °C | 19 % | 31 km/h | 0.0 mm | Extreme 54 |
| 9 Oct | 38.1 °C | 21 % | 35 km/h | 0.0 mm | Extreme 60 |
| 10 Oct | 35.8 °C | 30 % | 36 km/h | 0.1 mm | Very high 45 |
| 11 Oct | 38.6 °C | 21 % | 34 km/h | 0.0 mm | Extreme 52 |
| 12 Oct | 39.3 °C | 22 % | 40 km/h | 0.0 mm | Very high 49 |
| 13 Oct | 39.2 °C | 25 % | 39 km/h | 0.0 mm | Very high 50 |
| 14 Oct after | 35.7 °C | 38 % | 29 km/h | 1.0 mm | High 38 |
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
↔
Before · 10 Sept 2026
After · 20 Oct 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 19 September 2026 the air beside the fire reached 130 µg/m³ of PM2.5. That day averaged 69: 4.6 times the WHO daily guideline (15).
PM2.5 peak130 µg/m³
Days over the guideline7 days
PM10132 µg/m³
Optical depth1.77
WHO 15
16 Sept20 Sept24 Sept28 Sept2 Oct
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 · 1,616Every 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
- 29,238 haRoper Gulf30 August 2018 · 28 days · 12 km away
- 15,852 haBarkly13 November 2024 · 7 days · 19 km away
- 18,613 haRoper Gulf12 August 2023 · 19 days · 25 km away
- 22,878 haBarkly10 November 2024 · 8 days · 34 km away
- 19,525 haRoper Gulf14 November 2024 · 4 days · 37 km away
- 68,930 haRoper Gulf16 September 2026 · 9 days · 40 km away
Frequently asked questions
- How long did the Roper Gulf fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 17 September 2026 to 13 October 2026 (27 days). The perimeter dates it from 18 September 2026 to 13 October 2026.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 81,742 hectares (817.4 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Roper Gulf (71,431 ha, 0.4 %); Barkly (11,186 ha, 0.0 %).
- What was the weather like?
- During the fire the temperature reached 39.3 °C, humidity dropped to 9 % and gusts hit 49 km/h. The fire danger index (FWI) reached 93, class Very extreme.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Australia (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: 000 · 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 24 October 2026.
- Name: Barkly → Roper Gulf.
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 18 September 2026 to 13 October 2026. 1,616 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.
- Probably a vegetation burn: not counted in the totals.
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 (Creative Commons Attribution 4.0 International (CC BY 4.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.