Skip to content
worldfires
JP · Japan · →

Gotenba fire, February 2026 御殿場市 · Gotenba, Susono

Out · last detection 1 Feb 2026, 04:02 UTC

The fire started on 1 February 2026 in Gotenba, Japan, and satellites saw it burning for 1 day. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,487 hectares from heat detections, spread across 2 municipalities.

It is the largest fire in Shizuoka since 2016 (of 23 with a page). Number 5 in Japan in 2026, of 59.

Compare with…
Burnt area
1,487ha
GWIS perimeter (Copernicus)
Duration
1day
1 Feb 2026 – 1 Feb 2026
Municipalities hit
2
municipalities
Started on
1 Feb
2026
Heat detections
15
in a single hotspot: 114 MW
Danger at start
0
Very low · FWI index
Average daily power
449MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 1 Feb1 Feb

How it evolved, day by day

1 Feb 2026 · 449 MW · 15

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

The weather it burned in

6°high
26km/h · peak gust
33%lowest humidity

It had gone 2 days without rain (1 mm or more) when it started. Rain came after the fire: 14.4 mm on 7 Feb.

This area had burned before

93% of the perimeter overlaps earlier fires recorded since 2016: 1,266 ha in 2016, 127 ha in 2018, 717 ha in 2019, 612 ha in 2020, 484 ha in 2021, 700 ha in 2022, 422 ha in 2023, 567 ha in 2024. Part of it burned more than once, so the yearly figures add up to more than the 1,390 ha that had burned before.

How big is it?

10 km
It burned the equivalent of 0.9% of the area of London (15 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. Gotenba 御殿場市 where it started
    1,418 ha
    7.3 %
  2. Susono 裾野市
    73 ha
    0.5 %

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 2025
Built-up area0.10 ha
Residents< 20

Inside the perimeter there were about 0.10 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)
1 Feb 6.0 °C 33 % 26 km/h 0.0 mm Very low 0
2 Feb after 6.1 °C 32 % 34 km/h 0.0 mm Very low 1
3 Feb after 5.1 °C 35 % 23 km/h 0.0 mm Very low 1
4 Feb after 7.0 °C 41 % 30 km/h 0.0 mm Very low 1
5 Feb after 9.0 °C 36 % 30 km/h 0.0 mm Very low 1
6 Feb after 11.8 °C 33 % 34 km/h 0.0 mm Very low 2
7 Feb after 0.9 °C 74 % 34 km/h 14.4 mm Very low 0

Before and after, from space

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

Before · 25 Jan 2026
After · 8 Feb 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 4 February 2026 the air beside the fire reached 20 µg/m³ of PM2.5, but no daily average passed the WHO guideline (15).

PM2.5 peak20 µg/m³
Days over the guideline0 days
PM1021 µg/m³
Optical depth0.21
30311234
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 · 15Every 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 Japan ›

Frequently asked questions

How long did the Gotenba fire last?
GWIS (Copernicus) dates it between 1 February 2026 and 1 February 2026: 1 day 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 1,487 hectares (14.9 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Gotenba (1,418 ha, 7.3 %); Susono (73 ha, 0.5 %).
What was the weather like?
During the fire the temperature reached 6.0 °C, humidity dropped to 33 % and gusts hit 26 km/h. The fire danger index (FWI) reached 0, class Very low.
Where does this data come from?
From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Japan (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: 119 · 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.

RSS Changes to this page

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

How we know this
  • Perimeter: GWIS (Copernicus), rebuilt from heat detections rather than mapped on imagery.
  • Dates from the perimeter: the VIIRS detections inside it did not change them. 15 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.

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 ADM2 (Creative Commons Attribution-ShareAlike 2.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.