Skip to content
worldfires
HU · Hungary · –

SajTszentp fire, August 2026 SajTszentp, SajSkjpolna, Sajibdbony

Out · last detection 11 Aug 2026, 01:30 UTC

The fire started on 10 August 2026 in SajTszentp, Hungary, and satellites saw it burning for 2 days. Copernicus mapped a burnt perimeter of 356 hectares from satellite imagery, spread across 3 municipalities.

It is the 2th largest in Borsod-Abaúj-Zemplén since 2016 (of 15 with a page). The largest in Hungary in 2026, of 6.

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

Burnt area
356ha
Copernicus perimeter
Duration
≈ 2days
10 Aug 2026 – 11 Aug 2026
Municipalities hit
3
municipalities
Started on
10 Aug
2026
Heat detections
7
in a single hotspot: 2 MW
Danger at start
35
High · FWI index
Average daily power
4MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 10 Aug11 Aug
11 Aug 2026

How it evolved, day by day

10 Aug 2026 · 5 MW · 5 11 Aug 2026 · 3 MW · 2
10 Aug 11 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

34°high
39km/h · peak gust
22%lowest humidity

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

This area had burned before

68% of the perimeter overlaps earlier fires recorded since 2016: 241 ha in 2022.

What happened to each town

  1. SajTszentp where it started
    270 ha reached on 10 Aug
    7.7 %
  2. 44 ha
    4.1 %
  3. 42 ha
    3.1 %

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

  • Agricultural areas83 %
  • Other natural land17 %

Land cover inside the perimeter according to Corine Land Cover, as reported by Copernicus.

People and buildings inside the perimeter

GHSL 2025
Built-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)

Day High Min. humidity Peak gust Rain Danger (FWI)
10 Aug 33.9 °C 22 % 24 km/h 0.0 mm High 35
11 Aug 32.5 °C 32 % 39 km/h 0.7 mm High 37
12 Aug after 26.6 °C 26 % 45 km/h 0.0 mm High 38
13 Aug after 28.2 °C 21 % 36 km/h 0.0 mm High 37
14 Aug after 29.5 °C 27 % 30 km/h 0.0 mm High 35
15 Aug after 31.8 °C 22 % 22 km/h 0.0 mm High 34
16 Aug after 33.3 °C 22 % 30 km/h 0.0 mm Very high 39
17 Aug after 27.1 °C 42 % 36 km/h 0.7 mm High 25
18 Aug after 24.1 °C 37 % 34 km/h 2.0 mm Moderate 12

Its twins: fires that started in the same weather

It started with an FWI of 34.8, a minimum humidity of 22% and 2 days without rain. Fires in the area that started in weather like this since 2017: 14.

FWI at the start 34.8
Minimum humidity 22 %
Days without rain 2
this fire chosen twins rest of the area
Almost identicalSimilar

Outlines of the closest twins

D fire, July 2022
155 ha 1 day FWI 34.6 Min. humidity 24 % 124 km away, in 2022

First rain (1 mm or more) after it ended: 11.0 mm on 30 Jul.

What happened to them

Fires in the area that started in similar weather: 14. With fewer than 15 we give no figures: they would be more noise than signal.

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

2.0 mmfirst rain
18 Aug7 days after it ended
39km/h · max. gust

It was considered over on 11 Aug, and on 18 Aug 2.0 mm fell. We do not know whether the rain or the firefighters put it out.

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 2017.
  • 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 Aug 2026
After · 18 Aug 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 August 2026 the air beside the fire reached 11 µg/m³ of PM2.5, but no daily average passed the WHO guideline (15).

PM2.5 peak11 µg/m³
Days over the guideline0 days
PM1019 µg/m³
Optical depth0.26
8 Aug10 Aug12 Aug14 Aug
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 · 7Every 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 Hungary

Frequently asked questions

How long did the SajTszentp fire last?
The official perimeter only gives the start date (10 August 2026). The end comes from the heat detections inside the perimeter: it burned until 11 August 2026 (2 days from 10 August 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 356 hectares (3.6 km²). Official national figures may differ.
Which municipalities burned?
The fire entered 3 municipalities: SajTszentp (270 ha, 7.7 %); SajSkjpolna (44 ha, 4.1 %); Sajibdbony (42 ha, 3.1 %).
What was the weather like?
During the fire the temperature reached 33.9 °C, humidity dropped to 22 % and gusts hit 39 km/h. The fire danger index (FWI) reached 37, class High.
Where does this data come from?
From the EFFIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Hungary (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: 112 · 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.
  1. Last day with fire: 10 August 2026 → 11 August 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 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. 7 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 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 ADM3 (Open Data Commons Open Database License 1.0). 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.