Skip to content
worldfires
ME · Montenegro ·

Danilovgrad Municipality fire, 28 January 2024 Danilovgrad Municipality

Out · last detection

The fire started on in Danilovgrad Municipality, Montenegro, and satellites saw it burning for 1 day. Copernicus mapped a burnt perimeter of 103 hectares from satellite imagery, spread across a single municipality.

Number 43 in Montenegro in 2024, of 46.

The power measured by the satellite is low (0.3 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
103ha
Copernicus perimeter
Duration
1day
28 Jan 2024 – 28 Jan 2024
Municipalities hit
1
municipalities
Started on
28 Jan
2024
Heat detections
1
in a single hotspot: 0 MW
Danger at start
2
Very low · FWI index

Where it burned

HOTSPOTS BY DAY 28 Jan28 Jan

How it evolved, day by day

28 Jan 2024 · 0 MW · 1

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

The weather it burned in

5°high
34km/h · peak gust
45%lowest humidity

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

This area had burned before

100% of the perimeter overlaps earlier fires recorded since 2016: 103 ha in 2017, 1 ha in 2021.

What happened to each town

  1. Danilovgrad Municipality where it started
    103 ha reached on 28 Jan
    0.2 %

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 land100 %

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)
28 Jan 5.3 °C 45 % 34 km/h 0.0 mm Very low 2
29 Jan after 5.8 °C 38 % 24 km/h 0.0 mm Very low 2
30 Jan after 7.0 °C 31 % 28 km/h 0.0 mm Very low 2
31 Jan after 9.2 °C 23 % 25 km/h 0.0 mm Very low 3
1 Feb after 8.5 °C 37 % 18 km/h 0.0 mm Very low 3
2 Feb after 7.8 °C 38 % 36 km/h 0.0 mm Very low 4
3 Feb after 10.3 °C 45 % 28 km/h 0.0 mm Very low 3
4 Feb after 11.8 °C 50 % 21 km/h 0.0 mm Very low 3
5 Feb after 10.6 °C 56 % 17 km/h 0.0 mm Very low 3
6 Feb after 10.5 °C 60 % 19 km/h 0.0 mm Very low 3
7 Feb after 9.1 °C 83 % 25 km/h 2.7 mm Very low 0

Its twins: fires that started in the same weather

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

FWI at the start 1.5
Minimum humidity 45 %
Days without rain 7
this fire chosen twins rest of the area
Almost identicalSimilar

Outlines of the closest twins

Gacko fire, December 2025
695 ha 3 days FWI 0.7 Min. humidity 45 % 70 km away, in 2025

First rain (1 mm or more) after it ended: 2.5 mm on 17 Dec.

What happened to them

2 days
median duration
177 ha
median area
0 %
went past 1,000 ha
3.7 mm
rain at the end (median; 21 of 25 had it)

It stayed below its twins: 103 ha against a median of 177 ha. It lasted 1 day, against 2 days.

In 4 of 25, 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.7 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

2.7 mmfirst rain
7 Feb10 days after it ended
34km/h · max. gust

It was considered over on 28 Jan, and on 7 Feb 2.7 mm fell. We do not know whether the rain or the firefighters put it out. Twins with rain when they ended: 21 of 25, with a median of 3.7 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 · 21 Jan 2024
After · 4 Feb 2024

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 31 January 2024 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.07
26 Jan28 Jan30 Jan
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 · 1Every 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 Montenegro

Frequently asked questions

How long did the Danilovgrad Municipality fire last?
Copernicus dates it between 28 January 2024 and 28 January 2024: 1 day between the first and last image with fire.
How much area did it burn?
The perimeter Copernicus measured from satellite imagery is 103 hectares (1.0 km²). Official national figures may differ.
Which municipalities burned?
The fire only entered Danilovgrad Municipality (103 ha, 0.2 %).
What was the weather like?
During the fire the temperature reached 5.3 °C, humidity dropped to 45 % and gusts hit 34 km/h. The fire danger index (FWI) reached 2, class Very low.
Where does this data come from?
From the EFFIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Montenegro (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: 25. Their median duration was 2 days and their median area 177 ha; 0 % went past 1,000 ha. In 4 of 25, 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.7 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: 112 · 123 · 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.

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 · 123.

How we know this
  • Perimeter: EFFIS (Copernicus), mapped on satellite imagery.
  • Dates from the perimeter: the VIIRS detections inside it did not change them. One Suomi-NPP VIIRS detection 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 ADM1 (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.