Fire near Chetaïbi (DZ)

36.98°N, 7.39°E · first detected on 26 August at 13:34

What the satellites measured

This fire was tracked from 26 August at 13:34 to 28 August at 14:55, that is 2 days, through 358 satellite detections. The detected extent reaches 4,465 ha.

Detected extent
4,465 ha
Cumulative power
26,842 MW
Peak power, one pixel
1,726 MW
VIIRS and MODIS detections
358

These four figures cover the polar orbits alone, the ones that measure an area. The pass table below also counts geostationary detections, more frequent but too coarse for geometry, and its power column sums a whole pass where the peak above is that of a single pixel.

“Detected extent” is not “burned area”: it is the union of the ground footprints of the satellite pixels, and a 375 m pixel counts in full even when only a forest edge is burning. Compared with press figures it is in practice one and a half to three times the area reported. Detections taken at the edge of the scan swath, too coarse to measure anything at all, are excluded. These figures come from thermal detection and are not an official assessment: only the emergency services and the competent authorities are authoritative.

Replay how the fire spread

The map is framed on this fire and loads only its detections. The timeline below covers the whole known life of the fire, from the first trace, satellite or report, to the last announcement from emergency services, and the ticks on the bar mark those announcements. Detections often stop before containment: a fire stops radiating once it stops spreading, which is exactly when it is declared contained. “1 h” shows what is burning within an hour of the chosen moment : the map then follows the power curve below and empties when it falls. “12 h” stacks twelve hours , as the home map does, where stacking avoids an empty screen between two satellite passes. Both are true, but they say different things.

The detected extent

Outline of the burned area near Chetaïbi (DZ), drawn over satellite imagery
The outline is the union of the ground footprints of every satellite detection of this fire, from the first pass to the last. The background is the EOX cloudless Sentinel-2 mosaic, 2024 vintage: it shows the landscape BEFORE these fires, not the burn scar.

How the radiative power evolved

One point per satellite pass: the sum of the fire radiative power measured over the fire. This is the curve that says whether the fire eased off or picked up again, which no cumulative figure shows. The window covers 5 days; beyond that, clustering would merge two successive fires in the same place.

Fire dynamics

Loading history…

Satellite passes in detail

PassPower summed over the passDetectionsSensor
28 August at 14:5581 MW2N20
28 August at 14:006 MW1N21
28 August at 05:0441 MW2Aqua
28 August at 04:19229 MW8N21
28 August at 03:3432 MW10N20
28 August at 03:1549 MW10N
28 August at 02:399 MW5N21
27 August at 17:072,112 MW8Aqua
27 August at 15:141,945 MW53N20
27 August at 14:551,976 MW45N
27 August at 14:174,307 MW61N21
27 August at 13:343,547 MW55N20
27 August at 11:22453 MW4Terra
27 August at 02:585 MW1N21
26 August at 16:298,925 MW18Aqua
26 August at 15:33914 MW18N20
26 August at 15:1464 MW9N
26 August at 14:381,676 MW31N21
26 August at 13:51205 MW8N20
26 August at 13:34265 MW9N

Follow live

The map shows active fires in 3D, with smoke plumes, forecast wind, drop zones and the live position of water bombers tracked by ADS-B, anywhere in the world.

Open the fire map

Get the alert instead of looking for it

GISFire Pro watches the zones you draw, anywhere in the world, and warns you by email, SMS or webhook from the first satellite detection: fire in the zone, fire closing in, smoke announced before it arrives, lightning nearby. A GeoJSON and CSV API, exports and history come with it.

From €8.25 a month, 14-day trial, no commitment. The public map stays free.

Discover GISFire Pro

© 2026 SARO · Gistin. All rights reserved. The interface, its presentation and the contents of GISFire are protected; reproducing or imitating them requires written permission. The source data remain the property of their respective producers, see the credits.

Legal notice · Privacy policy