Operational failure
Refinery
Ryazan refinery 2025–2026
Russia
54.6200, 39.7500
Preparing your incident map…Loading the basemap and incident layers
What happened Repeated attacks, fires, equipment damage and processing stoppages were reported by Reuters and industry sources.
When cited sources give different casualty, damage or spill figures for this event, they’re reported side by side above rather than merged into one number. See how confidence levels work .
Russian airport-restriction cross-check (unofficial, approximate) Airport restriction reported Multiple central Russian airports (regional NOTAM wave)
The warning began 0 minutes before the recorded incident time and was still active when the incident occurred.
Restriction began 24/01/2025, 0:00:00 GMT+3
Incident time 24/01/2025, 0:00:00 GMT+3 (approximate)
Match confidence moderate The incident id covers a broad 2025-2026 range of Ryazan refinery strikes (distinct from the separately-matched 29 July 2026 and 13 March 2024 records); this cross-check corresponds specifically to the 24 January 2025 refinery fire and same-day wave of Russian airport closures reported by RBC-Ukraine and Kyiv Post. No single-airport NOTAM number was found, so this is a regional/multi-airport closure report rather than an airport-specific NOTAM.
Unlike the Ukrainian air-alert cross-check, Russia has no public, timestamped, settlement-level alert dataset to match against. This reflects Rosaviatsia airport-closure NOTAMs or wire-reported regional notices instead, which are coarser and do not independently prove the weapon, target or attribution. Browse the Ukraine and Russia alert timeline →
GPS-interference reference (link-out only, not a verified reading) Ryazan, Russia
View GPSJam.org's dated map for 2025-01-24
This links to GPSJam's dated public map centered on the incident area rather than a quantified reading: GPSJam renders its hexagon interference levels client-side from ADS-B Exchange aircraft data, and this project has no way to programmatically extract a specific percentage or color for that date/region, so no interference level is asserted here. GPSJam's own methodology also aggregates 24 hours per hexagon from aircraft-altitude data (not ground level) and can have data gaps, so even a visual reading would only be suggestive context, not proof of jamming tied to this specific strike.
This is a link to an external, independently-run map, not a claim made by this project about interference levels on this date.
Evidence Documented
Confidence High
Infrastructure Refinery
Weather context Loading…
Latitude 54.6200°
Longitude 39.7500° Reading the record
How individual claims are labelled These labels describe individual statements, not the incident as a whole. Significant allegations may be preserved, including false-flag claims, but their label reflects the evidence available rather than how often they are repeated.
Confirmed Established by primary evidence or strong, independent corroboration.
Reported Published by an identified, credible source, but not yet fully established.
Claimed An assertion by a named party with an interest in the event.
Disputed A material claim that another identified source directly contests.
Unverified Relevant information that currently lacks enough evidence to authenticate.
Conjecture An interpretation or proposed explanation rather than an established fact.
Internet chatter A notable online claim without credible sourcing or supporting evidence. Attribution Attributed to Ukraine 🇺🇦