Roper Gulf fire, 6 June 2025 Roper Gulf
The fire started on 6 June 2025 in Roper Gulf, Australia, and satellites saw it burning for 14 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 31,688 hectares from heat detections, spread across a single municipality.
It is the 340th largest in Northern Territory since 2016 (of 3517 with a page). Number 118 in Australia in 2025, of 1124.
Compare with…
- Burnt area
- 31,688ha
- GWIS perimeter (Copernicus)
- Duration
- 14days
- 6 Jun 2025 – 19 Jun 2025
- Municipalities hit
- 1
- local government areas
- Started on
- 6 Jun
- 2025
- Heat detections
- 1,058
- in a single hotspot: 125 MW
- Danger at start
- 36
- High · FWI index
- Average daily power
- 671MW
- 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 33 days without rain (1 mm or more) when it started.
This area had burned before
68% of the perimeter overlaps earlier fires recorded since 2016: 86 ha in 2017, 14,641 ha in 2018, 627 ha in 2019, 10,993 ha in 2021, 473 ha in 2022, 1,505 ha in 2023, 1,829 ha in 2024. Part of it burned more than once, so the yearly figures add up to more than the 21,651 ha that had burned before.
- 6,770 ha Roper Gulf fire, November 2021 25,859 ha in total; the hectares shown are those it shares with this fire
- 4,818 ha Roper Gulf fire, October 2018 5,787 ha in total; the hectares shown are those it shares with this fire
- 494 ha Roper Gulf fire, October 2018 10,136 ha in total; the hectares shown are those it shares with this fire
- 243 ha Roper Gulf fire, October 2018 11,928 ha in total; the hectares shown are those it shares with this fire
- 66 ha Roper Gulf fire, May 2024 11,700 ha in total; the hectares shown are those it shares with this fire
- 22 ha Roper Gulf fire, October 2024 7,802 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 started31,837 ha reached on 6 Jun0.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.
People and buildings inside the perimeter
GHSL 2025Inside the perimeter there were about 0.74 hectares of 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)
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 6 Jun | 30.7 °C | 27 % | 29 km/h | 0.0 mm | High 36 |
| 7 Jun | 30.7 °C | 34 % | 37 km/h | 0.0 mm | High 35 |
| 8 Jun | 28.9 °C | 24 % | 40 km/h | 0.0 mm | Very high 39 |
| 9 Jun | 26.9 °C | 23 % | 39 km/h | 0.0 mm | Very high 39 |
| 10 Jun | 26.6 °C | 26 % | 39 km/h | 0.0 mm | Very high 39 |
| 11 Jun | 27.0 °C | 22 % | 35 km/h | 0.0 mm | High 37 |
| 12 Jun | 27.7 °C | 16 % | 37 km/h | 0.0 mm | Very high 42 |
| 13 Jun | 27.5 °C | 18 % | 42 km/h | 0.0 mm | Very high 45 |
| 14 Jun | 27.9 °C | 17 % | 35 km/h | 0.0 mm | Very high 41 |
| 15 Jun | 28.8 °C | 21 % | 30 km/h | 0.0 mm | Very high 41 |
| 16 Jun | 30.1 °C | 28 % | 32 km/h | 0.0 mm | Very high 40 |
| 17 Jun | 29.0 °C | 30 % | 36 km/h | 0.0 mm | Very high 40 |
| 18 Jun | 28.1 °C | 38 % | 40 km/h | 0.0 mm | High 36 |
| 19 Jun | 29.9 °C | 33 % | 35 km/h | 0.0 mm | High 34 |
| 20 Jun after | 30.5 °C | 32 % | 41 km/h | 0.0 mm | High 38 |
| 21 Jun after | 30.1 °C | 32 % | 40 km/h | 0.0 mm | High 38 |
| 22 Jun after | 29.8 °C | 45 % | 40 km/h | 0.0 mm | High 34 |
| 23 Jun after | 30.4 °C | 33 % | 37 km/h | 0.0 mm | High 32 |
| 24 Jun after | 31.1 °C | 40 % | 30 km/h | 0.0 mm | High 30 |
| 25 Jun after | 30.9 °C | 28 % | 45 km/h | 0.0 mm | Very high 40 |
| 26 Jun after | 29.0 °C | 21 % | 39 km/h | 0.0 mm | Very high 43 |
| 27 Jun after | 28.9 °C | 22 % | 38 km/h | 0.0 mm | Very high 42 |
| 28 Jun after | 28.0 °C | 25 % | 35 km/h | 0.0 mm | Very high 41 |
| 29 Jun after | 26.1 °C | 27 % | 41 km/h | 0.0 mm | Very high 43 |
| 30 Jun after | 27.5 °C | 32 % | 42 km/h | 0.0 mm | Very high 42 |
| 1 Jul after | 27.6 °C | 24 % | 41 km/h | 0.0 mm | Very high 41 |
| 2 Jul after | 27.4 °C | 23 % | 39 km/h | 0.0 mm | Very high 39 |
| 3 Jul after | 27.4 °C | 21 % | 32 km/h | 0.0 mm | High 37 |
| 4 Jul after | 28.7 °C | 32 % | 31 km/h | 0.0 mm | High 36 |
| 5 Jul after | 31.4 °C | 32 % | 27 km/h | 0.0 mm | High 36 |
| 6 Jul after | 31.9 °C | 33 % | 38 km/h | 0.0 mm | Very high 38 |
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 11 June 2025 the air beside the fire reached 28 µg/m³ of PM2.5. That day averaged 15: 1.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 · 1,058Every 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 Roper Gulf fire last?
- GWIS (Copernicus) dates it between 6 June 2025 and 19 June 2025: 14 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 31,688 hectares (316.9 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Roper Gulf (31,837 ha, 0.2 %).
- What was the weather like?
- During the fire the temperature reached 31.1 °C, humidity dropped to 16 % and gusts hit 45 km/h. The fire danger index (FWI) reached 45, class Very high.
- 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 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
No changes since 24 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
- Perimeter: GWIS (Copernicus), rebuilt from heat detections rather than mapped on imagery; 2 polygons grouped in this page.
- Dates from the perimeter: the VIIRS detections inside it did not change them. 1,058 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.
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.