Nightwatch
Intelligence archive
Historical intelligence

Situation Report

Archived operational intelligence briefing retained for historical analysis.

Intelligence brief / archived issue

Situation Update (UTC)

Key updates since last sitrep

  • Jet-powered UAV in northern Chernihiv Oblast at/past Ripky, south-west course: Air Force of the Armed Forces of Ukraine reported a jet-propelled UAV in the north of Chernihiv Oblast on a course at/past Ripky, heading south-west (01:28 UTC, Повітряні Сили ЗС України, MEDIUM for the alert; LOW for effect). No impact, interception or debris reported. A south-west heading from Ripky places the track on a general axis toward the Kyiv/Chernihiv rear rather than the earlier Dobryanka and Honcharivske vectors.
  • KAB launches by Russian tactical aviation against Zaporizhzhia Oblast and Donetsk Oblast: Air Force reported guided aerial bomb (KAB) launches by hostile tactical aviation against Zaporizhzhia Oblast and Donetsk Oblast (01:31 UTC, Повітряні Сили ЗС України, MEDIUM for the alert; LOW for effect). No impact locations, target types, munition variants, casualties or damage reported. This is the first KAB alert in this cycle covering both the Zaporizhzhia and Donetsk axes simultaneously, and it broadly aligns with the Dempster–Shafer belief mass of 0.28 assigned to "Use of guided aerial bombs by enemy."
  • No new Ukrainian General Staff, Khortytsia OSG, OVA or DSNS operational statement appeared in this cycle. All ground-line and strike-effect items remain as carried forward.
  • No new Russian massed one-way-attack UAV wave, no Russian long-range aviation activity, and no Russian MoD claim appear in this cycle.
  • The previous cycle's four jet-UAV tracks (Krasiatychi and Borodianka/Hostomel in Kyiv Oblast, Korosten in Zhytomyr Oblast, and central Odesa city) have produced no follow-on impact, interception or debris reporting. Outcomes remain unknown and must not be read as penetration or defeat.
  • Feed hygiene: A ТАСС post at 01:36 UTC on a bear entering a school in Palana, Kamchatka is off-topic Russian state content with no bearing on the war; disregarded as operational noise. This is the second such ТАСС item in two cycles (after the 01:17 UTC bear-population post).

Operational picture (by sector)

  • Kupiansk (Kharkiv Oblast): No significant change.
  • Kharkiv / Vovchansk / South Slobozhansky direction (Kharkiv Oblast): No significant change on the ground line. The carried-forward Russian occupation-administration claim of ~500 Ukrainian personnel "liquidated" inside the "Vovchansk cauldron" (ТАСС, carrying Evgeny Lisnyak) remains UNCONFIRMED with no Ukrainian acknowledgement, imagery or BDA. The carried-forward KAB alert toward Kharkiv Oblast stands with no reported impact.
  • Izium (Kharkiv Oblast, operational rear): No significant change. The single-source Russian-affiliated claim of a precision strike on the 3rd Separate Assault Brigade command post killing Major Levenets remains UNCONFIRMED.
  • Lyman / Krasnyi Liman / northern Donetsk (Donetsk Oblast): No significant change. Carried-forward Ukrainian 3rd Army Corps (commander Andriy Biletsky) Operation Vivaldi claims — clearance at Novoselivka, Yarova, Korovyi Yar and Oleksandrivka, Ukrainian control of Serednie, ~75 km² cleared and ~10 km² deoccupied — remain single-source and unverified.
  • Nevske / Yevrobologovka (Luhansk Oblast, Lyman–Kreminna approaches): No significant change. Prior-cycle partisan claim of Russian forces ceding ground remains UNCONFIRMED.
  • Siversk (Donetsk Oblast): No significant change.
  • Chasiv Yar (Donetsk Oblast): No significant change in the line of contact. The prior-cycle Colonelcassad claim regarding the death of the Russian 4th Brigade commander Grunis remains without Russian MoD confirmation or a named successor.
  • Toretsk (Donetsk Oblast): No significant change.
  • Kostiantynivka / Kramatorsk / Sloviansk (Donetsk Oblast): Line of contact unchanged and assessed as contested. Carried-forward: the unevidenced "Kostiantynivka was taken very quickly" claim and the Russian-affiliated Kramatorsk blackout claim remain UNCONFIRMED.
  • Debaltseve–Donetsk highway corridor (Donetsk Oblast): No significant change. Prior-cycle dashcam explosion remains MEDIUM for the event, LOW for attribution.
  • Pokrovsk / Dobropillya / southern Donetsk (Donetsk Oblast): No significant change on the ground line. Baseline repelled-assault reporting remains current; the sector remains assessed as exposed to KAB and FPV pressure, and the 01:31 UTC KAB alert explicitly covers Donetsk Oblast with no reported impact.
  • Druzhkivka / "Druzkovskoe" direction (Donetsk Oblast): No significant change.
  • Olexandrivka (Donetsk Oblast): No significant change.
  • Novopavlivka axis (Dnipropetrovsk Oblast): No significant change.
  • Huliaipole (Zaporizhzhia Oblast): No significant change. Carried-forward unverified Russian-source annotated map claiming regained control west of Rybne and the ~800 m Novoselivka–Kopani claim remain UNCONFIRMED.
  • Orikhiv / Mala Tokmachka / Zaporizhzhia front (Zaporizhzhia Oblast): Updated — the 01:31 UTC KAB launch alert covers Zaporizhzhia Oblast; no impact location, target type, munition variant or damage reported. Ground line of contact otherwise unchanged. The carried-forward "Vostok" grouping / Separate Battalion of Unmanned Systems "Berkut" thermal-strike footage remains MEDIUM for footage, LOW for target ID and damage.
  • Kherson direction (Kherson Oblast): No significant change in the ground line. Carried-forward Air Force reporting of strike UAVs launching from Kherson Oblast toward Mykolaiv Oblast indicates the occupied-bank launch belt remains active.
  • Mykolaiv direction (Mykolaiv Oblast): No significant change this cycle. The carried-forward jet-UAV track toward Mykolaiv Oblast from Black Sea waters (00:34 UTC) stands with no impact, interception or debris. The unverified "several vessels" strike claim and the Snihurivka strike-UAV track remain unconfirmed.
  • Odesa direction (Odesa Oblast): No significant change this cycle. The overflight of Odesa city by a jet-powered UAV reported at 01:16 UTC in the previous cycle has produced no impact, interception or debris reporting; the carried-forward unverified "several vessels" strike claim also remains unconfirmed.
  • Poltava / Cherkasy rear (Poltava and Cherkasy Oblasts): No significant change this cycle. Carried-forward jet-UAV tracks at Tsvitkove, Cherkasy Oblast (toward Kyiv Oblast) and the strike UAV at Komyshnia, Poltava Oblast stand with no reported outcome.
  • Kirovohrad Oblast (central Ukraine rear): No significant change. Carried-forward jet-powered UAV track toward Ustynivka and Bobrynets stands with no impact, interception or debris.
  • Chernihiv direction (Chernihiv Oblast): Updated — a jet-powered UAV was reported in northern Chernihiv Oblast at/past Ripky on a south-west course (01:28 UTC); no impact, interception or debris reported. The carried-forward Dobryanka (south-west) and Honcharivske (toward Kyiv Oblast) jet-UAV tracks stand with no reported outcome. Chernihiv Oblast has now carried jet-UAV tracks across multiple consecutive cycles, indicating a persistent northern transit belt rather than a single transit.
  • Kyiv / Kyiv Oblast (rear air-defense and political sector): No new tracks this cycle. The carried-forward tracks past Krasiatychi, Kyiv Oblast (south-west, 00:54 UTC) and in Kyiv Oblast toward Borodianka/Hostomel (01:03 UTC) stand with no impact, interception or debris. Together with the carried Chernihiv (Honcharivske, Ripky) and Cherkasy (Tsvitkove) capital-oriented tracks, the Kyiv axis remains under sustained multi-vector stand-off transit. The carried-forward Boryspil track and Kyiv warehouse/Nova Poshta claims remain unverified.
  • Zhytomyr direction (Zhytomyr Oblast): No new tracks this cycle. The carried-forward jet-powered UAV track in Zhytomyr Oblast toward Korosten (00:59 UTC) stands with no impact, interception or debris — currently the westernmost deep-rear jet-UAV track in the recent cycle, on the Korosten rail axis.
  • Sumy direction (Sumy Oblast): No significant change. Carried-forward Air Force alerts for a one-way-attack UAV near Buryn heading south and KABs toward Sumy Oblast stand without reported impacts.
  • Kursk / North Slobozhansky border (Kursk Oblast, Russia / Sumy Oblast): No significant change.
  • Belgorod / border rear areas (Belgorod Oblast, Russia): No significant change; prior unverified casualty claim stands unconfirmed.
  • Dnipropetrovsk rear / Nikopol–Synelnykove (Dnipropetrovsk Oblast): No significant change.
  • Zaporizhzhia city / oblast (Zaporizhzhia Oblast): No significant change; prior unverified 150/10 kV substation strike claim stands unconfirmed. The 01:31 UTC KAB alert covers the oblast with no reported impact.
  • Volyn / western rail rear (Volyn Oblast): No significant change. The DSNS-confirmed Ukrzaliznytsia locomotive fire remains the only corroborated item.
  • Russian rear — Samara Oblast (Syzran) / Rostov (Taganrog) / Volgograd: No significant change beyond the carried-forward Russian-official confirmation of a massed UAV attack on Syzran overnight 15 September.
  • Russian rear — energy, logistics and fuel (Voronezh Oblast; Leningrad Oblast / St Petersburg): No significant change; carried-forward items stand as reported.
  • Belarus / northern flank; Baltic / NATO eastern flank: No significant change in observed force posture.
  • Svatove / Luhansk reference area (Luhansk Oblast); border checkpoints / air-alert procedures: No significant change.

Deep strikes & air defense

  • New — KAB launch against Zaporizhzhia Oblast and Donetsk Oblast: Reported 01:31 UTC by Air Force of the Armed Forces of Ukraine. Guided aerial bombs released by hostile tactical aviation; no impacts, target types, munition variants, casualties or damage reported. MEDIUM for the alert; LOW for effect. (Повітряні Сили ЗС України)
  • New — jet-powered UAV, northern Chernihiv Oblast, at/past Ripky, south-west course: Reported 01:28 UTC. Transit/alert only — no impact, interception or debris. MEDIUM for the alert; LOW for effect. (Повітряні Сили ЗС України)
  • No new Russian massed one-way-attack UAV wave and no Russian long-range aviation activity appear in this cycle.
  • Carried forward, unchanged: jet-UAV over Odesa city (01:16); jet-UAV in Kyiv Oblast toward Borodianka/Hostomel (01:03); jet-UAV past Krasiatychi, Kyiv Oblast, south-west (00:54); jet-UAV in Zhytomyr Oblast toward Korosten (00:59); jet-UAV track toward Mykolaiv Oblast from Black Sea waters (00:34); Chernihiv tracks at Dobryanka (00:31) and Honcharivske (00:47, toward Kyiv Oblast); KAB alert toward Kharkiv Oblast; jet-powered UAV toward Ustynivka/Bobrynets, Kirovohrad Oblast; strike UAV at Komyshnia, Poltava Oblast; jet-powered UAV at Tsvitkove, Cherkasy Oblast; Syzran massed UAV attack; Donetsk-wide and Sumy KAB alerts; Buryn (Sumy Oblast) UAV track; Kherson→Snihurivka strike-UAV track; Orikhiv front FPV strike on a claimed Ukrainian antenna. All MEDIUM alert / LOW effect unless otherwise noted.
  • Threat picture unchanged: Russian regional air defense continues to rely on mobile fire groups layered with fixed SAMs; Ukrainian air defense continues to report hostile tracks without publishing outcomes.

Enemy activity / threat assessment

  • The two new items split the hostile air effort between a northern deep-rear transit (Chernihiv) and a southern/north-eastern tactical-air KAB release covering two oblasts. Across recent cycles, jet-UAV tracks have been reported into Sumy, Mykolaiv, Poltava, Kirovohrad, Cherkasy, Chernihiv (now three vectors: Dobryanka, Honcharivske, Ripky), the Black Sea–Mykolaiv axis, Kyiv Oblast (×2), Zhytomyr Oblast and Odesa city. Assessed likely intent remains dispersed, multi-axis stand-off pressure — attrition, rear-area interdiction and air-defense probing — rather than a massed operational-level air campaign. MEDIUM.
  • The Ripky track's south-west heading is consistent with the Chernihiv–Kyiv transit corridor already identified via Honcharivske. Combined with the carried Krasiatychi, Borodianka/Hostomel and Tsvitkove tracks, the northern and north-eastern approaches to the capital remain the most heavily transited belt. This implies either a deep-rear target set (energy, rail, logistics, airfields) or a deliberate air-defense-drawing manoeuvre. No interception or debris reported, so outcomes are unknown. LOW.
  • The simultaneous KAB alert covering Zaporizhzhia and Donetsk Oblasts indicates continued tactical-aviation glide-bomb employment against widely separated axes. With no impact reporting, this is assessed as a launch alert only; the pattern is consistent with cumulative KAB/UMPK attrition on fixed settlements and front-line positions rather than a single concentrated package. LOW–MEDIUM for pattern; LOW for any specific effect.
  • Assessed likely Russian COA (next 6–12h): Continued jet-powered and one-way-attack UAV transits from northern/north-eastern and southern launch belts into the Chernihiv, Kyiv, Zhytomyr, Poltava, Kirovohrad, Mykolaiv and Odesa directions; continued KAB/UMPK employment against Zaporizhzhia, Donetsk, Kharkiv and Sumy Oblasts; continued FPV and KAB attrition on the Donetsk and Zaporizhzhia axes; continued counter-C2 and counter-communications targeting in the Kharkiv–Donetsk rear. MEDIUM for pattern; LOW for verified effects.
  • Assessed most dangerous Russian COA: A jet-UAV or Shahed salvo reaching a Chernihiv, Kyiv, Zhytomyr or Odesa energy, rail or port node with cumulative infrastructure effect; a concentrated KAB/UMPK package against a populated Zaporizhzhia, Donetsk, Kharkiv or Sumy settlement producing mass casualties; a verified strike degrading 3rd Army Corps / 3rd Assault Brigade C2. LOW confidence pending corroboration.

Friendly activity (UAF)

  • Air defense and early-warning reporting was again the principal UAF output this cycle: a jet-powered UAV at/past Ripky, Chernihiv Oblast, south-west course (01:28 UTC) and a KAB-launch alert covering Zaporizhzhia and Donetsk Oblasts (01:31 UTC). No interceptions, impacts or debris were reported, so the outcome of each track is unknown. (Повітряні Сили ЗС України)
  • No new Ukrainian ground-force or General Staff operational statement appeared in this cycle. Operation Vivaldi figures, front-line repelled-assault reporting and the Izium C2 situation remain as carried forward. There is likewise no Ukrainian acknowledgement or denial of the Russian "Vovchansk cauldron" casualty claim.
  • Sustainment and C2 hardening: The standing requirement for UAF C2 hardening across the Kharkiv–Donetsk operational rear remains relevant given the unresolved Izium command-post claim, and the KAB/UMPK threat to the Zaporizhzhia–Donetsk line sustains the requirement for dispersal and hardened sheltering forward of the contact line.

Information environment / disinformation

  • ТАСС bear-at-school post (01:36 UTC): A bear entering a school in Palana, Kamchatka, subsequently destroyed, reported by the district administration. Entirely off-topic Russian state content with no war relevance; noted only as feed noise and disregarded operationally.
  • Carried-forward disinformation items unchanged, all UNCONFIRMED unless noted: the "Vovchansk cauldron" ~500-personnel casualty claim; the Izium command-post strike and Major Levenets' death; Vivaldi counter-claims by Russian-affiliated channels; "Kostiantynivka taken very quickly"; the Kramatorsk blackout claim; Rybar deep-strike claims; the Воин DV "Vostok"/"Berkut" Zaporizhzhia strike clip; the Rubicon/LOSTARMOUR "300 SPGs" dashboard; the Slovak MEP vs. Kallas exchange via ТАСС; the US indictment of Russian nationals carried by ASTRA and РБК-Україна (no named defendants, case number or DoJ filing; attached image is a generic stock hooded gunman with no evidentiary value); and the US House procedural vote on the Lindsey O. Graham Sanctioning Russia and Iran Act of 2026 (214–211, MEDIUM as reported, LOW for the unexplained "the late" reference to Senator Graham).
  • The continuing appearance of off-topic Russian state content in the feed should be treated as noise and not aggregated into any operational inference.

Outlook (next 6–12h)

  • Weather, as of 01:45 UTC (Open-Meteo, UTC; HIGH for numeric values): Vovchansk 11.8 °C, overcast, wind 2.8 m/s, cloud 99%, 0.0 mm; Svatove 13.1 °C, light rain, wind 2.7 m/s, cloud 100%, 0.0 mm; Pokrovsk 11.7 °C, overcast, wind 2.4 m/s, cloud 99%, 0.0 mm; Orikhiv 13.3 °C, overcast, wind 2.6 m/s, cloud 98%, 0.0 mm; Kherson 13.5 °C, mainly clear, wind 1.3 m/s, cloud 42%, 0.0 mm. Daily forecast for 16 September: Vovchansk min/max 10.1/16.9 °C, light rain, precipSum 0.8 mm, windMax 3.2 m/s; Svatove 12.9/16.1 °C, light rain, precipSum 0.3 mm, windMax 3.6 m/s; Pokrovsk 11.6/15.6 °C, overcast, 0.0 mm, windMax 3.4 m/s; Orikhiv 11.6/20.2 °C, overcast, 0.0 mm, windMax 4.8 m/s; Kherson 12.7/22.4 °C, overcast, 0.0 mm, windMax 2.5 m/s. Assessed: near-total cloud cover at Vovchansk and Svatove limits optical reconnaissance and can reduce laser designation and some guided-bomb accuracy there; light rain at both may locally disrupt FPV/UAV operations overnight. Pokrovsk, Orikhiv and Kherson remain drier; the low cloud ceilings at Pokrovsk and Orikhiv are permissive for UAV operations but do not preclude KAB release, and the clearer, low-wind conditions at Kherson remain permissive for the southern maritime launch belt.
  • KAB alert (Zaporizhzhia and Donetsk Oblasts): Watch for impact locations, target types, release platform, munition variant (UMPK-fitted FAB-250/500/1500), and OVA/DSNS casualty and damage reporting. MEDIUM for alert; LOW for effect.
  • Chernihiv jet-UAV track (Ripky): Watch for impact, interception or debris reporting, airframe identification (jet-powered Shahed variant vs. other), any extension of the air alert toward Kyiv Oblast, and any Chernihiv OVA statement. MEDIUM for track; LOW for effect.
  • Carried jet-UAV tracks (Kyiv Oblast ×2, Zhytomyr/Korosten, Odesa city, Mykolaiv, Kirovohrad, Poltava, Cherkasy): Watch for late impact/interception/debris reporting, air-alert expansion, and any strike effects on energy, rail, port or logistics nodes. MEDIUM for tracks; LOW for effect.
  • Vovchansk cauldron narrative: Watch for any Ukrainian General Staff or Khortytsia OSG response, geolocated imagery around Vovchansk, independent casualty reporting, and whether the figure is repeated or revised by Russian MoD channels. LOW.
  • Northern Donetsk / Vivaldi and Izium C2: Watch for updated DeepState layers, geolocated imagery at Serednie, Novoselivka, Yarova, Korovyi Yar and Oleksandrivka, Ukrainian acknowledgement of Major Levenets' status, and Russian milblogger counter-claims. LOW–MEDIUM.
  • US indictment and sanctions bill: Watch for a DoJ press release or court filing (case number, defendants, charges), and the House Clerk roll-call record for the 214–211 procedural vote and scheduling of the final vote. LOW for the indictment; MEDIUM for the sanctions bill.

Intelligence gaps & collection requirements

  • KAB employment — Zaporizhzhia and Donetsk Oblasts (new): Need impact locations, target types, release platform and base airfield if identifiable, munition variant (UMPK FAB-250/500/1500), casualty and damage reports, OVA/DSNS statements, and geolocated imagery; determine whether this was a single dual-axis sortie package or separate releases.
  • Chernihiv jet-UAV track at/past Ripky (new): Need impact/interception/debris location, airframe identification, launch-site attribution, course continuation, and any Chernihiv OVA or Air Force follow-up notice.
  • Kyiv Oblast jet-UAV tracks (carried): Need impact/interception/debris location at Krasiatychi and in the Borodianka/Hostomel area, airframe identification, launch-site attribution, and any Kyiv OVA statement.
  • Zhytomyr/Korosten jet-UAV track (carried): Need impact/interception/debris location, munition/airframe identification, launch-site attribution, and any Zhytomyr OVA or Air Force follow-up notice.
  • Odesa city jet-UAV overflight (carried): Need impact/interception/debris location, airframe identification, launch-platform attribution (sea-based vs. occupied coast), any Odesa OVA/DSNS reporting, and port-area damage assessment.
  • Black Sea → Mykolaiv jet-UAV track (carried): Need launch-platform attribution, impact/interception/debris location, and any Air Force follow-up notice.
  • Jet-powered UAV toward Ustynivka/Bobrynets, Kirovohrad Oblast; strike UAV at Komyshnia, Poltava Oblast; jet-UAV at Tsvitkove, Cherkasy Oblast (carried): Need impact/interception/debris location, munition type and airframe identification, and any Air Force follow-up notice.
  • Vovchansk "cauldron" casualty claim (carried): Need Ukrainian General Staff/Khortytsia OSG statement, geolocated imagery of the claimed encirclement area, independent casualty reporting, and the Russian MoD/Sever Group figure against Lisnyak's ~500 — reconcile with the previously cited "up to 1,700 personnel affected."
  • Izium command-post strike and Major Levenets (carried): Need Russian MoD/official confirmation; Ukrainian acknowledgement or denial; confirmation of name, rank and command position; DSNS/OVA Izium reporting; geolocation of the claimed "command and storage objects"; munition identification; and any successor appointment for the 3rd Separate Assault Brigade.
  • Operation Vivaldi geolocation (carried): Need time-series satellite imagery (Sentinel-2/SAR) over Serednie, Novoselivka, Yarova, Korovyi Yar and Oleksandrivka; updated DeepState and General Staff LOC layers; identification and disposition of the Russian units claimed affected (20th and 25th Combined Arms Armies); independent verification of the ~1,500 personnel and >12,000 UAV figures.
  • Воин DV "Berkut" Zaporizhzhia strike (carried): Need geolocation of the wooded area, confirmation of Ukrainian equipment loss, identification of the "Berkut" unit's parent structure within the "Vostok" grouping, and evidence of communications or UAV degradation in the Orikhiv sector.
  • US indictment of Russian nationals (carried): Need the DoJ press release or New York court filing (case number, named defendants, charge sheet), corroboration of the ABC News and РБК-Україна reporting, and reverse-image verification of the hooded-gunman stock photo.
  • US House Russia sanctions bill (carried): Need the bill number, the 214–211 procedural roll-call record, the confirmed date of the final House vote and the Senate pathway; require the congressional record or a roll-call source. Also establish whether any credible basis exists for the post's reference to Senator Graham as "the late."
  • Voronezh Oblast fuel relocation (carried): Need satellite/FIRMS evidence of new fuel storage or pipeline withdrawal in Voronezh Oblast and any Russian logistics reporting.
  • Energy truce claim (carried): Need the primary RBC-Ukraine article, a Ukrainian presidential transcript, the actual US statement of 14 September (with year) and any Kremlin readout; need scope, duration and monitoring mechanism.
  • Grunis death and the Russian 4th Brigade (carried): Need Russian MoD confirmation or award-decree verification, funeral/memorial notices and a successor appointment.
  • Rybne / Huliaipole control change (carried): Need the original video at 0:33/0:52, geolocation of both aerial insets, time-series satellite imagery over 47.81728, 36.30943 and 47.80644, 36.31123, and identification of the Russian units involved.
  • Syzran strike (Samara Oblast) (carried): Need target identity, munition type and count, BDA, and reconciliation of the governor's "around 20 UAVs downed" with any Ukrainian launch figure.
  • Nevske / Yevrobologovka (carried): Need geolocated imagery and Ukrainian/DeepState corroboration of any control change.
  • Lyman line of contact (carried): Need geolocated imagery at Novoselivka, Yarova, Oleksandrivka and Serednie; status of Kolodezi, Terny and Yampolivka; confirmation of the "wedge cut" and Zherebets River DRG activity.
  • Debaltseve–Donetsk highway strike (carried): Need identification of the struck vehicle, munition type and corroborating footage showing markings.
  • Zaporizhzhia "NSU antenna" strike (carried): Need geolocation of the tree line, target identification and evidence of Ukrainian communications degradation in the Orikhiv sector.
  • Burluk axis (carried): Need geolocation of the claimed Olkhovatka "liberation" and the ~325 km² cauldron graphic; identification of Russian units inside it.
  • Kyiv-region warehouse strike (carried): Need geolocation of the «Міжнародна логістична компанія» facility, operating company, function and a Ukrainian OVA/DSNS statement.
  • Rybar digest deep-strike claims (carried): Need Ukrainian and Russian official corroboration for Odesa-area vessel strikes, the Zaporizhzhia substation strike, the Zatoka FAB/UMPK strike, the Volyn locomotive identity (M62m-1225-2) and the Taganrog and Volgograd Oblast strikes.
  • Russian regional fuel distribution (carried): Need refinery restart status and regional fuel-stock data to determine whether the Leningrad Oblast/St Petersburg shortfall is contained or spreading.