Translation in progress — showing English pivot content.

Satellite

Where the measurements are

Drawn server-side from the public event read model. Every mark is a measurement: nothing here is interpolated, smoothed or inferred.

-7.8°-7.7°-7.6°-7.5°-7.4°-7.3°41.7°41.8°modelled track · NOAA21 · 14:27 UTC10 kmChavesSanta CruzVidagoBoticasMontalegre

What each mark means

Footprint at this scaleVIIRS (NASA) 375 mMeteosat (EUMETSAT) ≈2 km · not drawn

  • VIIRS (NASA)375 m

    Measured positions. Drawn at true footprint scale, brightest layer.

  • Meteosat (EUMETSAT)≈2 km28 min ago

    Measures how much energy the fire radiates, which is what sizes the glow. Its individual pixel positions are not stored, so no Meteosat footprint is drawn — inferring one from the sharper layer would put a fire pixel on ground nobody measured.

  • True geographic scale, corrected for latitude. Frame is about 48 km across.
  • The glow means “an event, roughly here”. Its area follows the measured power and its radius is capped, because an uncapped one would assert a burnt extent nobody measured. The number carries the magnitude.
  • Grey is what a later pass has superseded. Colour means the most recent sharp measurement, and it never fades with the clock — only newer knowledge demotes it.
  • Coastline, lakes and borders come from a generalised map with about 1,7 km between vertices, so treat every line as the shape of the geography and not as a surveyed boundary. It is drawn under the data and never over it.
  • Place names sit at their own coordinates from an offline index of populated places. They say what is near the measurements — not that any named place is burning, and not how far the fire reaches.
  • The dashed line is a modelled satellite ground track through the pass that produced the coloured detections — real published orbital parameters, measured pass time, modelled geometry. The swath is 3060 km wide, so where the satellite actually looked from inside it is unknown.

Satellite

Current facts

No satellite detection does not mean an area is safe. Cloud, sensor timing and heat below a sensor’s threshold can hide activity.

First seen30/07/2026, 13:00 UTC
Last observation30/07/2026, 22:40 UTC
Observed stateMeasurable thermal activity
Like-for-like trendNot enough comparable observations
Latest measured power17,4 MW · Meteosat
OfficialNo official source is linked to this event yet.

MTG · VIIRS · Official

Verification ladder

  • SeenObserved

    A satellite observed a thermal anomaly here. Repetition belongs at this step: seeing the same thing many times separates noise from signal, but it does not separate heat from bright ground. Observed by: Meteosat (EUMETSAT).

  • ConfirmedObserved

    The anomaly carries measured energy or a 375 m position — the calibrated Meteosat fire product, or a VIIRS detection. Persistence alone never lights this step, because sunlit dry ground is persistent by nature.

  • Quantified by VIIRSNot yet observed

    VIIRS (NASA) passed overhead and measured radiated power at a 375 m footprint. Between passes it says nothing.

  • Linked to an official sourceNot yet observed

    An official update has been matched to this event. Official information outranks everything above it.

When each sensor looked

Meteosat looks every ten minutes; VIIRS passes a few times a day. The contrast is the point — between sharp passes there is no new sharp knowledge, only the ten-minute layer.

Meteosat (EUMETSAT)VIIRS (NASA)no observations on this rail07-30 13:00 UTC07-30 22:40 UTC · 28 min ago

VIIRS · Meteosat

Observation history

Day and night observations stay labelled. REYKR does not compare unlike times of day.

  1. Meteosat1 detections · average 17,4 MW · peak 17,4 MWDay
  2. Meteosat3 detections · average 7,4 MW · peak 8 MWDay
  3. Meteosat2 detections · average 10,4 MW · peak 11,7 MWDay
  4. Meteosat3 detections · average 11,5 MW · peak 21,4 MWDay
  5. Meteosat1 detections · average 6,1 MW · peak 6,1 MWDay
  6. Meteosat4 detections · average 12,3 MW · peak 28,3 MWDay
  7. Meteosat3 detections · average 18,1 MW · peak 36,2 MWDay
  8. Meteosat3 detections · average 22,2 MW · peak 43,9 MWDay
  9. Meteosat4 detections · average 33,4 MW · peak 78,9 MWDay
  10. Meteosat6 detections · average 31,1 MW · peak 81,4 MWDay
  11. Meteosat6 detections · average 59,7 MW · peak 117,9 MWDay
  12. Meteosat5 detections · average 52,8 MW · peak 103,9 MWDay
  13. Meteosat4 detections · average 26,9 MW · peak 83,2 MWDay
  14. Meteosat5 detections · average 43,3 MW · peak 120,1 MWDay
  15. Meteosat5 detections · average 23,3 MW · peak 61,8 MWDay
  16. Meteosat3 detections · average 52,8 MW · peak 75,6 MWDay

Official

Official source record

Official information is shown separately and takes precedence over satellite interpretation.

No official source is linked to this event yet.