Skip to content
worldfires
en
UA · Ukraine ·

Sorokyne fire, July 2026 Sorokyne

Out · last detection 10 Jul 2026, 11:17 UTC

The fire started on 10 July 2026 in Sorokyne, Ukraine, and satellites saw it burning for 1 day. Copernicus mapped a burnt perimeter of 799 hectares from satellite imagery, spread across a single municipality.

It is the 89th largest in Luhansk Oblast since 2016 (of 909 with a page). Number 66 in Ukraine in 2026, of 984.

The power measured by the satellite is low (15.8 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.

Compare with…

Suggestions: Lutuhyne · 2022Lutuhyne · 2024Sorokyne · 2023Dovzhansk · 2024

Burnt area
799ha
Copernicus perimeter
Duration
≈ 1day
10 Jul 2026 – 10 Jul 2026
Municipalities hit
1
districts
Started on
10 Jul
2026
Heat detections
8
in a single hotspot: 16 MW
Danger at start
54
Extreme · FWI index
Average daily power
64MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 10 Jul10 Jul

How it evolved, day by day

10 Jul 2026 · 64 MW · 8

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

The weather it burned in

33°high
49km/h · peak gust
25%lowest humidity

It had gone 4 days without rain (1 mm or more) when it started. Rain came after the fire: 1.6 mm on 14 Jul.

This area had burned before

20% of the perimeter overlaps earlier fires recorded since 2016: 68 ha in 2023, 94 ha in 2024.

How big is it?

10 km
It burned the equivalent of 0.5% of the area of London (8 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. Sorokyne where it started
    797 ha reached on 10 Jul
    0.6 %

Burnt area inside each municipality, from crossing the official 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.

What burned

  • Other natural land50 %
  • Agricultural areas50 %

Land cover inside the perimeter as reported by Copernicus EFFIS (outside the Corine Land Cover area).

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: 28 % of the area in Ukraine

Day High Min. humidity Peak gust Rain Danger (FWI)
10 Jul 32.8 °C 25 % 49 km/h 1.0 mm Extreme 54
11 Jul after 27.3 °C 29 % 38 km/h 0.0 mm Very high 41
12 Jul after 27.8 °C 33 % 54 km/h 0.5 mm Extreme 59
13 Jul after 29.0 °C 28 % 48 km/h 0.0 mm Extreme 57
14 Jul after 28.9 °C 44 % 31 km/h 1.6 mm High 35

Its twins: fires that started in the same weather

It started with an FWI of 53.5, a minimum humidity of 25% and 4 days without rain. Fires in the area that started in weather like this since 2016: 67.

FWI at the start 53.5
Minimum humidity 25 %
Days without rain 4
this fire chosen twins rest of the area
Almost identicalSimilar

Outlines of the closest twins

Lutuhyne fire, August 2022
768 ha 2 days FWI 53.8 Min. humidity 26 % 41 km away, in 2022

First rain (1 mm or more) after it ended: 5.1 mm on 18 Aug.

See its page Compare with this fire

What happened to them

2 days
median duration
191 ha
median area
7 %
went past 1,000 ha
3.1 mm
rain at the end (median; 43 of 67 had it)

It was 4.2 times larger than the median of its twins and lasted 1 day, against 2 days.

Only 5 of its 67 twins burned more. The weather on the first day does not explain everything: the wind in the following days, the fuel and the firefighting also count. In 24 of 67, not even 1 mm fell in the ten days after the end: they went out without rain. In the rest, the first rainy day brought a median of 3.1 mm.

This is a bank of analogues: it shows what usually happens, not what will happen. With fewer than 15 twins we give no figures. How we calculate it

How it ended

1.6 mmfirst rain
14 Jul4 days after it ended
49km/h · max. gust

It was considered over on 10 Jul, and on 14 Jul 1.6 mm fell. We do not know whether the rain or the firefighters put it out. Twins with rain when they ended: 43 of 67, with a median of 3.1 mm.

Weather on this page: Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)

How a twin is chosen

  • Same area: fires that have already ended, less than 250 km from this one, since 2016.
  • Same start: we compare the FWI on the first day, the minimum humidity that day and the run of days without rain before it. The slider sets how much they may differ.
  • Only pages with final weather data (ERA5 reanalysis) calculated in the same way as this fire’s; agricultural and grass burns and pages with data under review are left out.
  • Fires burning at the same time as this one (a week before or after) are left out: they share the same spell of weather and do not count as a precedent.
  • They are sorted by similarity, and the outlines of the first five are drawn.

How we calculate it

Before and after, from space

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

Before · 3 Jul 2026
After · 17 Jul 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 11 July 2026 the air beside the fire reached 12 µg/m³ of PM2.5, but no daily average passed the WHO guideline (15).

PM2.5 peak12 µg/m³
Days over the guideline0 days
PM1013 µg/m³
Optical depth0.48
8 Jul10 Jul12 Jul
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 · 8Every 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 Ukraine

Frequently asked questions

How long did the Sorokyne fire last?
The official perimeter only gives the start date (10 July 2026). The end comes from the heat detections inside the perimeter: it burned until 10 July 2026 (1 day from 10 July 2026), the last day with detections before more than 10 days in a row without any, so it is approximate.
How much area did it burn?
The perimeter Copernicus measured from satellite imagery is 799 hectares (8.0 km²). Official national figures may differ.
Which municipalities burned?
The fire only entered Sorokyne (797 ha, 0.6 %).
What was the weather like?
During the fire the temperature reached 32.8 °C, humidity dropped to 25 % and gusts hit 49 km/h. The fire danger index (FWI) reached 54, class Extreme.
Where does this data come from?
From the EFFIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Ukraine (geoBoundaries). It is not an official report.
How did the fires that started in similar weather in this area end?
Fires less than 250 km away that started since 2016 with a similar FWI, humidity and dry spell: 67. Their median duration was 2 days and their median area 191 ha; 7 % went past 1,000 ha. Only 5 of its 67 twins burned more. The weather on the first day does not explain everything: the wind in the following days, the fuel and the firefighting also count. In 24 of 67, not even 1 mm fell in the ten days after the end: they went out without rain. In the rest, the first rainy day brought a median of 3.1 mm.

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: 101 · 112 · 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 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
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 101 · 112.

How we know this
  • Perimeter: EFFIS (Copernicus), mapped on satellite imagery.
  • The official perimeter has no end date: the end is the last day with VIIRS detections inside the perimeter before a gap of more than 10 days (150 days at most), so it is approximate. 8 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 and land cover come from the Copernicus European Forest Fire Information System (EFFIS), measured on MODIS and Sentinel-2 imagery and published under CC BY 4.0. 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 (Public Domain). The area per municipality is computed by WorldFires by crossing the perimeter with those boundaries, so it may differ slightly from each country’s official figure.