How long did the Adobe Mtn fire last?

According to the heat detections seen by satellite inside the perimeter, it burned from 2 August 2025 to 4 August 2025 (3 days). The perimeter dates it from 2 August 2025 to 2 August 2025.

How much area did it burn?

The official perimeter published by United States agencies (MTBS / NIFC) is 4,317 hectares (43.2 km²). Other tallies, such as daily incident reports, may give slightly different figures.

Which counties burned?

The fire only entered Elko (4,332 ha, 0.1 %).

What was the weather like?

During the fire the temperature reached 29.2 °C, humidity dropped to 13 % and gusts hit 48 km/h. The fire danger index (FWI) reached 52, class Extreme.

Where does this data come from?

From the official burnt perimeter of United States agencies (MTBS / NIFC, public domain), NASA FIRMS VIIRS hotspots and the administrative boundaries of United States. It is not an official report.

US · United States · 2025-08-02 → 2025-08-04

Adobe Mtn Fire, August 2025 Elko

Out · last detection 4 Aug 2025, 09:25 UTC

The fire started on 2 August 2025 in Elko, United States, and satellites saw it burning for 3 days. United States agencies (MTBS / NIFC) mapped an official burnt perimeter of 4,317 hectares, spread across a single county.

It is the 66th largest in Nevada since 2016 (of 237 with a page). Number 86 in United States in 2025, of 327.

Compare with…

Suggestions: Coal · 2017 Gance · 2018 Stag · 2018 Pole Creek · 2017

Burnt area: 4,317ha; official perimeter (MTBS / NIFC)
Duration: 3days; 2 Aug 2025 – 4 Aug 2025
Municipalities hit: 1; counties
Started on: 2 Aug; 2025
Heat detections: 92; in a single hotspot: 356 MW
Danger at start: 37; High · FWI index
Average daily power: 1.7GW; detected power per day, on average

HOTSPOTS BY DAY 2 Aug4 Aug

Play back 4 Aug 2025

How it evolved, day by day

2 Aug 3 Aug 4 Aug

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

The weather it burned in

29°high

48km/h · peak gust

13%lowest humidity

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

This area had burned before

No earlier perimeters overlap this fire since 2016, when the satellite record begins.

How big is it?

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

Elko where it started

4,332 ha reached on 2 Aug

0.1 %

Burnt area inside each county, from crossing the official 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)
2 Aug	27.9 °C	19 %	30 km/h	0.1 mm	High 37
3 Aug	29.2 °C	13 %	39 km/h	0.0 mm	Very high 47
4 Aug	27.1 °C	15 %	48 km/h	0.0 mm	Extreme 52
5 Aug after	29.3 °C	11 %	32 km/h	0.0 mm	Very high 44
6 Aug after	30.6 °C	11 %	43 km/h	0.0 mm	Extreme 54
7 Aug after	28.2 °C	13 %	54 km/h	0.0 mm	Extreme 58
8 Aug after	25.8 °C	9 %	36 km/h	0.0 mm	Very high 50
9 Aug after	26.4 °C	13 %	35 km/h	0.0 mm	Very high 48
10 Aug after	28.8 °C	16 %	36 km/h	0.0 mm	Very high 49
11 Aug after	30.9 °C	15 %	36 km/h	0.0 mm	Very high 47
12 Aug after	33.1 °C	13 %	29 km/h	0.0 mm	Very high 45
13 Aug after	33.2 °C	12 %	47 km/h	0.0 mm	Extreme 56
14 Aug after	30.9 °C	12 %	38 km/h	0.0 mm	Very high 50

Before and after, from space

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

↔

Before · 26 Jul 2025

After · 11 Aug 2025

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 5 August 2025 the air beside the fire reached 32 µg/m³ of PM2.5. That day averaged 18: 1.2 times the WHO daily guideline (15).

PM2.5 peak32 µg/m³

Days over the guideline1 day

PM1034 µg/m³

Optical depth0.63

WHO 15

3112345

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 · 92Every 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 United States ›

Frequently asked questions

How long did the Adobe Mtn fire last?: According to the heat detections seen by satellite inside the perimeter, it burned from 2 August 2025 to 4 August 2025 (3 days). The perimeter dates it from 2 August 2025 to 2 August 2025.
How much area did it burn?: The official perimeter published by United States agencies (MTBS / NIFC) is 4,317 hectares (43.2 km²). Other tallies, such as daily incident reports, may give slightly different figures.
Which counties burned?: The fire only entered Elko (4,332 ha, 0.1 %).
What was the weather like?: During the fire the temperature reached 29.2 °C, humidity dropped to 13 % and gusts hit 48 km/h. The fire danger index (FWI) reached 52, class Extreme.
Where does this data come from?: From the official burnt perimeter of United States agencies (MTBS / NIFC, public domain), NASA FIRMS VIIRS hotspots and the administrative boundaries of United States. 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: 911

Satellite cross-check

NASA FIRMS ↗
NIFC · Fire maps ↗

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

How we know this

Perimeter: NIFC WFIGS (United States), official.
Dates adjusted with the VIIRS detections inside the perimeter, which said 2 August 2025 to 2 August 2025. 92 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 is official and in the public domain. For past years it comes from MTBS (Monitoring Trends in Burn Severity), run by the U.S. Geological Survey and the USDA Forest Service, which map it on Landsat and Sentinel-2 imagery. For the current and last year it comes from WFIGS at the National Interagency Fire Center (NIFC): incident perimeters mapped by fire crews, aircraft and imagery. Heat detections come from the VIIRS sensors aboard Suomi-NPP and NOAA-20, distributed by NASA FIRMS at 375 m resolution. County boundaries come from geoBoundaries ADM2 (Public Domain). The area per county is computed by WorldFires by crossing the perimeter with those boundaries, so it may differ slightly from official figures.

Where it burned