Skip to content
You can now search across every topic, entity and event.What's new
Iran Conflict 2026
3AUG

Iran names two soldiers among its dead

2 min read
15:23UTC

An Iranian Army statement named Sergeant Ali Moeinni and First Seaman Shahab Omidi, killed on 10 July at Shahid Yasini Air Base, the first individual dead confirmed in the current wave.

ConflictDeveloping
Key takeaway

Iran names Sergeant Moeinni and Seaman Omidi killed on 10 July, its first individually named dead of the wave.

An Iranian Army general-staff statement named two service members killed in a 10 July strike on Shahid Yasini Air Base in Bushehr province: Sergeant Ali Moeinni and First Seaman Shahab Omidi of the navy's special operations. 1 They are the first individual dead Iran has named in the current wave.

A separate general-staff statement had put eight military personnel killed at Bandar Abbas and Bushehr in the 8 to 9 July strikes. 2 Moeinni and Omidi advance that aggregate toll rather than restate it , confirm the dead include regular-Army personnel alongside IRGC members, and push the documented strike cadence into the morning of 10 July.

The two deaths sit apart from the disputed Bushehr nuclear-plant claim. Iran's own officials reported no casualties from the noon 9 July perimeter strike; Moeinni and Omidi died the next morning in a separate air-base strike elsewhere in the province. 3 Coverage that merges the two would put deaths at the reactor that Iran itself does not claim.

Deep Analysis

In plain English

Iran's Army has for the first time named individual soldiers killed in the current wave of strikes: Sergeant Ali Moeinni and First Seaman Shahab Omidi, both killed on the morning of 10 July at an air base in Bushehr province. Until now, Iran had only given a total number, eight dead, without naming anyone. Naming individual casualties, rather than just a count, is a significant moment in how a country manages a war at home. It usually means officials have finished verifying who died and are now ready to make the losses public and personal, rather than keeping them as an abstract toll.

Deep Analysis
Root Causes

Iran's Army and IRGC run separate casualty-reporting chains, which is why regular-Army losses required their own general-staff statement rather than folding into the aggregate toll already reported at Bandar Abbas and Bushehr.

Each branch verifies and releases its own dead on its own schedule, so the state's overall casualty picture assembles in stages rather than through one central announcement.

What could happen next?
  • Precedent

    This is Iran's first individually named military casualty confirmation of the current wave, distinct from the aggregate tolls issued through 9 July.

First Reported In

Update #151 · Iran widens war to Jordan; oil shrugs

Fararu· 10 Jul 2026
Read original
Causes and effects
This Event
Iran names two soldiers among its dead
The named dead confirm regular-Army losses and push the documented strike cadence into the morning of 10 July.
Different Perspectives
Lloyd's Market Association
Lloyd's Market Association
War-risk underwriters price the Houthis' Red Sea attacks because the group announces its targets in advance, but the unclaimed Damietta drone gives insurers a hit with no author to price against. An attack nobody claims costs shipping more than one that is claimed, since premiums are set against a known pattern, not raw damage.
US Central Command
US Central Command
CENTCOM has announced no strike on Iran since resuming bombing on 30 July within hours of an IRGC salvo on Jordan, and centcom.mil did not respond to requests to confirm any pause. The command has gone quiet before while a larger operation was being weighed, so silence alone proves nothing about what it has or has not done.
Hengaw
Hengaw
Hengaw recorded at least 67 executions in Iran during July, of which the state acknowledged only eight, and reported the 1 August execution of protest detainee Arvin Kheirkhahan at Shahrud with no advance notice to his family. A family's first notice of a death sentence is now usually the instruction to collect a body.
Egypt
Egypt
Egypt's government asked media on 2 August to report the Damietta attack accurately, named no author, and said no findings will be published before its own investigation concludes. Cairo holds the debris and jurisdiction over an attack on its own soil, and naming a culprit now would pull it into a dispute it has avoided for five months.
Iran's Foreign Ministry
Iran's Foreign Ministry
Araghchi called the Hormuz talks with Oman final-stage on 2 August, four days after his own deputy rejected Oman's lane proposal, and denied the Damietta drone strike as an Israeli false flag while two Iranian officials privately claimed it for Tehran. Iran's public position now contradicts itself on both files at once.
Bahrain and Kuwait
Bahrain and Kuwait
Bahraini and Kuwaiti aircraft flew their own strikes on Iranian depots in July with Emirati air cover behind them, and Ynetnews reports some Gulf capitals wanted the 2 August strike to proceed rather than stop. States that have already taken fire see a closing window on Iranian weakness, not a reason to pause.