Strike Operations & Targets

This chapter spans from mid-2023 through February 28, 2026, and its contents are artifacts of our collection methodology, not meaningful precursors. Items from @auroraintel reference 2023 Syrian airstrikes; @bbcarabic entries discuss Gaza; @medvedev_telegram posts address Ukraine. These are stray keyword matches — 'airstrike,' 'missile,' 'target' — caught by the thread's regex patterns in channels that were already in our monitoring corpus.

The sole item of any relevance is @alhadath at 05:24 UTC on February 28, reporting strikes on southern Lebanon and Israel 'attacking Hezbollah' — which, given its timestamp just 46 minutes before the first Iran strikes, likely captures the opening of the broader operation's Lebanese front rather than a true precursor signal.

Saturday morning, February 28 (06:00–10:00 UTC) — the first four hours after strikes began at ~06:10 UTC. The information environment ignited with extraordinary speed, but the ecosystem composition is revealing: Western sources (16 items) and Russian channels (13) dominated, with OSINT (5) filling gaps. Iranian state media was virtually silent.

The Russian milblog ecosystem moved fastest. By 07:01 UTC — barely fifty minutes after the first strikes — @readovkanews was reporting Khamenei's relocation to a secure location (274,000 views). At 07:13, @rybar published a tactical assessment naming Tehran, Qom, and Isfahan as strike zones, using the sardonic headline 'Saturday Shield of the Jews' — framing the operation through an explicitly civilizational lens from the first hour. BBC Persian, the primary Western-adjacent Farsi source, began carrying Trump's address to the Iranian people at 08:27 UTC and US embassy shelter orders from Qatar and Bahrain by 08:32. The first Arab source (@alhadath, 09:33) carried the first reports of a US base in Bahrain being struck and a missile intercepted over Kuwait — the retaliatory dimension emerging.

@cnalatest's 09:45 UTC post — 'Trump says the US is carrying out major combat operations in Iran and vows to annihilate their navy and raze Tehran' — carried 80,500 views and marked the moment the operation's maximalist scope entered the English-language information space.

Saturday February 28 (10:00–22:00 UTC) — hours four through sixteen. This twelve-hour window saw the information environment's center of gravity shift dramatically as Iranian sources entered at scale, producing 138 items. But Russian channels still led overall with 400 items, now joined by 161 OSINT posts performing real-time verification.

The Iranian entry was not gradual — it was orchestrated. At 10:30 UTC, @middle_east_spectator carried IRIB's announcement that Iran's Armed Forces would 'strike at multiple arenas simultaneously.' By 10:54, the Khatam Al-Anbiyaa Central Command issued its first formal statement. The framing was immediate and deliberate: this was not a defensive response but a multi-theater offensive. BBC Persian at 11:08 carried the first civilian damage footage — an explosion near Shariyati Street in Tehran — introducing the human cost dimension.

The thread's geographic scope expanded rapidly through this window. Kuwait's Foreign Ministry responded to Iranian strikes on its territory (10:56 UTC). The Houthi dimension activated, with @rybar_mena noting at 10:04 that 'the Houthis are waking up.' By midafternoon, the thread encompassed strikes in six Iranian cities and retaliatory hits against targets in Israel, Bahrain, Kuwait, and the UAE — a geographic footprint that would only continue to grow.

Saturday night into Sunday morning (Feb 28, 22:00 UTC – Mar 1, 10:00 UTC) — the conflict's first overnight period. Russian channels maintained their relay function (143 items), but the most notable shift was the dramatic rise of Arab-language sources (89 items) and Chinese outlets entering the thread (47 items, up from 7 in the prior window).

The retaliatory targeting escalated sharply. @solovievlive reported at 22:00 UTC that Iran had attacked Jebel Ali port in the UAE. @middle_east_spectator confirmed Iranian drone strikes on Abu Dhabi's Sheikh Zayed Airport at 23:20 and Bahrain International Airport at 00:25 UTC on March 1. BBC Persian at 23:10 carried Fars News Agency's denial of Khamenei's death — 'Trump has again published fake news' — the first major Iranian counter-narrative on the leadership question.

By the early morning hours of March 1, the thread's character had transformed. The Washington Post report (referenced in editorial #29) revealing pre-planned operations introduced the 'premeditation narrative' that would become a separate information battleground. The thread was no longer just tracking strikes — it was processing competing frameworks for understanding their legitimacy.

Sunday March 1 (10:00–22:00 UTC) — hours 28 through 40. Russian channels still produced the most items (214), but the thread's defining feature was the confirmation of Khamenei's death at approximately 11:25 UTC, carried by @tengrinews (51,300 views) citing Tasnim, IRNA, ISNA, Mehr, and Fars simultaneously. This single event reframed every subsequent strike operation from military campaign to regime destruction.

The IRGC's claim to have struck a vessel transiting Hormuz (@middle_east_spectator, 11:56 UTC) marked the operational thread's expansion into maritime interdiction. @readovkanews at 10:05 warned that the UAE 'will not sit idly by' if Iran continues strikes — the first signal of Gulf states potentially entering as active belligerents rather than targets. By editorial #36's window (~31-33 hours in), the IRGC claimed four ballistic missiles had struck the USS Abraham Lincoln — a claim whose verification became its own information battleground. Press TV treated it as confirmed fact; Xinhua ran a two-line wire; Russian milblogs performed their own assessment.

@rybar's 10:19 report on anomalous Polymarket betting patterns before the strikes introduced a financial-intelligence dimension: 'While American and Israeli planes were still approaching targets in Tehran, someone had already placed bets.' This was information-environment analysis happening inside the ecosystem itself.

Sunday night into Monday morning (Mar 1, 22:00 UTC – Mar 2, 10:00 UTC) — hours 40 through 52. The thread entered its attritional phase. Russian channels (156) continued systematic coverage, but Arab sources surged to 113 items, with Iranian channels (70) maintaining steady output. The geographic expansion of the conflict dominated: @boris_rozhin at 22:14 reported Iranian strikes on Bahrain, explosions in Cyprus near the British base at Akrotiri, and France declaring it 'will not' respond — three theaters in a single post.

@middle_east_spectator confirmed strikes on the British base in Cyprus at 22:24, the 'Victoria Base' in Baghdad at 22:35, and — by 05:46 on March 2 — an Iranian Shahed-136 striking the US Embassy in Kuwait, geolocated and confirmed. The operational thread was now spanning from the Strait of Hormuz to the eastern Mediterranean. The B-2 stealth bomber deployment, confirmed by CENTCOM (editorial #43: 'over 1,000 targets hit'), signaled the operation's industrial scale.

The information environment's processing of the F-15 friendly fire incident (editorial #51) revealed ecosystem fault lines. CENTCOM confirmed three F-15Es crashed in Kuwait due to friendly fire. Rozhin immediately argued that admitting Iranian responsibility would contradict claims that Iranian air defenses were destroyed. The same physical event generated entirely incompatible narratives within minutes.

Monday March 2 (10:00–22:00 UTC) — hours 52 through 64. This was the thread's highest-volume day, producing 915 items. Russian channels dominated with 317 items, but Iranian (123) and Arab (128) sources were now producing at industrial scale. The information environment was fully saturated.

The thread's verification crisis peaked. @boris_rozhin at 10:03 performed debunking that would typically be a Western journalist's role: 'The distributed footage of alleged Iranian anti-ship missile strikes on an American vessel is very cheap AI-generated content, stuffed with WWII footage.' At 10:07, he relayed the IRGC's claim that Netanyahu's residence and IAF command headquarters had been struck by precision Kheibar missiles. The juxtaposition — debunking one Iranian claim while relaying another — captured the Russian ecosystem's selective verification function.

The ARAMCO Ras Tannoura strike emerged in this window as the thread's economic inflection point. The Tasnim claim — relayed via TASS — that Israel, not Iran, struck the Saudi refinery represented a real-time attribution contest. The claim's propagation chain (Iranian agency → Russian state media → OSINT aggregators) was textbook cross-ecosystem laundering of an implausible narrative.

Monday night into Tuesday morning (Mar 2, 22:00 UTC – Mar 3, 10:00 UTC) — hours 64 through 76. Iranian sources seized the thread's lead for the first time, producing 200 of 612 items. Arab sources (124) matched Russian output (124) exactly. The ecosystem's center of gravity was shifting eastward.

The B-2 confirmation deepened. @solovievlive at 22:38 relayed CBS News reporting that stealth bombers were striking IRGC command-and-control nodes. @boris_rozhin at 22:41 carried the IRGC's counter-claim: its navy had struck a US destroyer with Qadr-380 and Talaieh missiles. The thread was now processing simultaneous claim-counterclaim cycles at a pace that made verification functionally impossible in real time.

Tuesday morning brought the Israeli air-to-air dimension. @abualiexpress at 08:35 reported an Israeli F-35I shooting down an Iranian YAK-130 over Tehran — a claim that generated competing Iranian interpretations within hours (drone shootdown vs. air-to-air engagement). @middle_east_spectator at 08:56 carried satellite imagery confirming Iranian strikes had destroyed US AN/GSC-52B radars in Bahrain — one of the few OSINT-verified Iranian damage claims in this period.

Tuesday March 3 (10:00–22:00 UTC) — hours 76 through 88, marking the conflict's third full day. Iranian sources dominated decisively with 373 of 1,066 items — the thread's single highest-volume chapter. The Assembly of Experts strike at approximately 14:22 UTC became the window's defining event, not for its military significance but for the framing war it triggered.

@middle_east_spectator reported at 14:22 that Israeli officials claimed the strike targeted the body responsible for selecting a new Supreme Leader. Fox News pushed a maximalist narrative: the strike occurred 'during ballot counting,' with one official stating 'we wanted to reset the clock.' Iranian outlets — Mehr News — countered that the building was 'old and auxiliary, not used for meetings.' BBC Persian confirmed physical destruction. The attribution contest was instantaneous and total: the same building's destruction meant regime decapitation to Israeli sources and irrelevant property damage to Iranian ones.

The IRGC's targeting expanded to Fujairah oil facilities in the UAE and Salalah port in Oman (@milinfolive, 10:28), while @ajanews at 15:13 carried the Wall Street Journal report that Trump was 'open to supporting groups inside Iran willing to take up arms' — the first explicit regime-change signal entering the Arab information space.

Tuesday night into Wednesday morning (Mar 3, 22:00 UTC – Mar 4, 10:00 UTC) — hours 88 through 100. Iranian sources led again (166), closely tracked by Arab (155) and Russian (140) channels. The thread's overnight dynamics revealed a now-settled pattern: IRGC communiqués released during Iranian business hours, amplified through Russian milblogs during European evening, and processed by Arab outlets continuously.

@boris_rozhin at 22:16 reported Iran had destroyed a US AN/TPY-2 radar in Jordan — 'a holiday of sorts,' he quipped. @solovievlive at 22:38 carried CBS News confirming B-2 stealth bombers striking IRGC C2 nodes. The Mojtaba Khamenei succession claim entered the thread via Iran International (opposition) → AbuAliExpress (Israeli OSINT) → Soloviev (Russian political), with Russian milblogs adding the sourcing corrective that other nodes omitted.

By Wednesday morning, the Iranian government spokeswoman told Al Jazeera (@ajanews, 09:41): 'We have suffered painful blows, especially the martyrdom of the Leader of the Revolution and some of our military commanders.' This was the most candid official Iranian admission of damage — and it appeared on an Arab network, not Iranian state media, underscoring how different audiences received different registers of candor.

Wednesday March 4 (10:00–22:00 UTC) — hours 100 through 112, marking the conflict's fifth day. Iranian sources dominated again (358 items), with the thread now processing a mature, multi-front war rather than an initial shock. The information environment had settled into industrialized production cycles.

@rybar at 10:05 reported the sinking of an Iranian frigate near Sri Lanka — 'from where no one expected' — expanding the conflict's naval geography to the Indian Ocean. @boris_rozhin at 10:12 carried the domestic detail that Tehran's metro had gone free as stations served as bomb shelters, alongside Ayatollah Sistani's call for immediate ceasefire from Iraq. Hegseth's doubling down on the Assembly of Experts strike claim (@middle_east_spectator, 13:16) kept the regime-destruction narrative alive.

The most ominous signal appeared at 20:08 via @ajanews: an Iranian military official told Iran Nuance that if America and Israel moved toward 'armed chaos' to topple the regime, 'we will strike Dimona.' The nuclear facility threat — entering through an Arab news relay of an Iranian outlet — represented the thread's highest escalation signal yet, though its sourcing chain (anonymous official → niche outlet → Al Jazeera wire) invited skepticism about authorization level.

Wednesday night into Thursday morning (Mar 4, 22:00 UTC – Mar 5, 08:00 UTC) — hours 112 through 122. Iranian (103) and Arab (100) sources dominated this overnight window, with Russian output dropping to 55 items — the lowest Russian contribution since the conflict began, suggesting possible information-cycle fatigue or editorial prioritization shifts in Moscow.

The White House's 'Call of Duty' strike compilation video (@solovievlive, 03:33) became a cross-ecosystem event. TASS framed it through video-game aesthetics; Radio Farda noted it was released 'to highlight what it considers a successful start.' The gamification of military operations by a belligerent government was processed with fascination across all ecosystems — one of the rare moments of cross-boundary agreement that something unprecedented was occurring in the information space.

@ajanews at 22:14 reported Iraqi security forces seizing a mobile launch platform with two missiles in Basra — the thread's first clear evidence of militia infrastructure being used for independent strikes from Iraqi territory. @middle_east_spectator at 00:16 carried the IRGC Navy targeting a British-flagged oil tanker off Kuwait, extending the maritime dimension to UK-flagged vessels.

Thursday March 5 (08:00–20:00 UTC) — hours 122 through 134. This twelve-hour chapter produced 934 items with a marked amplification surge. Iranian sources led at 367 items — their highest sustained output — with Arab channels (226) providing the relay infrastructure. The thread was now processing the conflict's consolidation phase.

B-52 strikes entered the thread via @ajanews at 16:33, carrying CENTCOM's confirmation that the heavy bombers targeted Iranian ballistic missile sites and command centers. @abualiexpress at 10:25 reported at least 15 US refueling aircraft at Portugal's Lajes airfield in the Azores — OSINT tracking of logistics infrastructure that revealed the operation's transatlantic support chain. Iranian drones hitting Azerbaijan's Nakhchivan airport (@milinfolive, 08:32) introduced a new geographic spillover dimension.

The Azerbaijan confrontation escalated rapidly. @middle_east_spectator at 16:44 carried Azerbaijani President Aliyev's extraordinary statement: 'Iran asked us for help evacuating their diplomatic staff from Lebanon, and we did. Less than two days later, they hit our airport.' This quote — its propagation from presidential statement through OSINT channels to Russian milblogs — became a case study in how an aggrieved neutral state's narrative gets absorbed by belligerent ecosystems.

Thursday night into Friday morning (Mar 5, 20:00 UTC – Mar 6, 08:00 UTC) — hours 134 through 146. Iranian (179) and Arab (146) sources continued to dominate, with Russian channels (64) maintaining a reduced but steady output. The thread entered its most politically charged phase.

BBC Persian at 20:05 reported Trump's endorsement of Kurdish attacks on Iran — a regime-change signal that propagated through Farsi channels to the Kurdish information space. @ajanews at 21:47 carried the US House vote rejecting a resolution to limit further strikes on Iran (219 votes) — a constitutional development that received far more attention in Arab media than in American outlets, where it was buried beneath operational coverage.

The Minab school strike emerged as a pivotal information event. @boris_rozhin at 06:03 on March 6 relayed the New York Times finding that the girls' school bombing was carried out not by Israel but by US Air Force. @milinfolive at 06:30 posted detailed imagery of an F-15E's weapons loadout departing for an Iran strike — the thread's information space now treating individual airframe configurations as newsworthy, a sign of how granular the operational tracking had become.

Friday March 6 (08:00–10:00 UTC) — a compressed two-hour window at approximately hour 146. Iranian sources (60) dominated this brief chapter, with Arab (31) and Russian (20) channels maintaining presence. The thread was processing the conflict's seventh morning.

@solovievlive at 08:18 carried the Iranian casualty toll reaching 1,045 — a number whose propagation path (Iranian authorities → Russian state media → OSINT) ensured it reached global audiences before Western outlets had verified it. @boris_rozhin at 08:16 referred to overnight coalition strikes on Tehran as attacks by 'the Epstein coalition' — a sardonic label that had by now become standard in Russian milblog discourse.

@intelslava at 09:51 carried Trump's statement that he did not plan a ground operation in Iran, calling it a 'waste of time' — a de-escalation signal in the kinetic dimension even as the strike tempo continued. The thread was bifurcating between political signaling (no ground invasion) and operational reality (continued aerial bombardment).

Friday March 6 (10:00–18:00 UTC) — hours 148 through 156, the thread's most recent chapter and its third amplification surge. Iranian sources led with 180 items, Russian channels surged back to 103, and Arab outlets produced 105. The information environment was processing Day 7 with undiminished intensity.

The Azerbaijan dimension escalated: @middle_east_spectator at 10:04 reported Baku withdrawing diplomatic staff from Tehran and Tabriz. @boris_rozhin at 10:13 responded within minutes, arguing Iran should 'completely destroy Azerbaijani oil infrastructure' if Aliyev attacks in US-Israeli interests — Russian milblog commentary now actively shaping the conflict's potential expansion vectors.

The IRGC announced its 22nd strike wave using 'newest super-heavy ballistic missiles' (@solovievlive, 10:25). The Washington Post's report that Russia was providing Iran with intelligence for targeting US forces (@intelslava, 12:12) represented the thread's most consequential great-power escalation signal. @ajanews at 13:17 carried the IDF announcing a new wave of strikes on Tehran and Isfahan infrastructure — the operational tempo showing no signs of diminution as the conflict entered its second week.

Trump's demand for 'unconditional surrender' — tracked in editorial #128 — collided directly with Rubio's assurance to Arab ministers that this was 'not regime change.' The thread's latest chapter thus closed on the same contradiction that has defined it since the first hours: maximalist rhetoric from political leadership meeting operational reality that no amount of information management can fully reconcile.