5JUL

140 executions sit beneath the talks

1 min read

10:09UTC

Iran Human Rights put the final tally of executions for the Iranian month of Khordad at 140, six above the 134 already recorded, a verification catch-up rather than fresh killings.

← Back to Iran's new leader wounded, not just hiding Jump to analysis ↓

ConflictDeveloping

Key takeaway

Iran Human Rights raised the Khordad execution toll to 140, six more than 134, as a verification catch-up.

Iran Human Rights, a Norway-based monitor, finalised the execution count for Khordad, the Iranian calendar month running 22 May to 21 June, at 140 people on 30 June ¹. That revises up the 134 already in the record , a correction as the monthly verification caught up rather than fresh killings, since Khordad had ended nine days earlier. Six more names were added to a month already closed.

Those 140 executions are the human cost sitting beneath a fortnight of negotiation over oil, assets and inspections. For European governments that tie engagement with Tehran to human-rights progress, an execution surge during a diplomatic opening is the contradiction they have not addressed. Iran Human Rights frames the revision as a verification lag, not a new wave, which makes the figure a fuller count of killings already carried out rather than evidence of an acceleration.

Deep Analysis

In plain English

Khordad is a month in the Iranian calendar that ran from 22 May to 21 June this year. Iran Human Rights, an independent monitoring group based in Oslo, Norway, tracks executions in Iran because the Iranian government doesn't publish its own official count. The group first recorded 134 executions during Khordad. On 30 June, nine days after the month ended, it raised that figure to 140. This isn't because six more people were executed after the month finished; it's because some cases take longer to confirm than others, and those six had only just cleared the group's verification standard.

Deep Analysis

Root Causes

Iran Human Rights' count rises for a structural reason, not a new killing wave. The Oslo-based NGO builds its tally from lawyers, families and local reporting that reach it at different speeds after each execution. A monthly figure published at month-close is provisional and gets revised upward for weeks as slower reports pass its verification threshold, which is why six additional Khordad cases clearing that bar by 30 June moved the count from 134 to 140.

Iran's own judiciary does not publish a real-time aggregate execution count, which leaves outside verification as the only mechanism tracking the true total. That absence of an official register is itself the structural cause of the lag: there is no faster, authoritative source to check the NGO's figures against.

What could happen next?

Meaning
The six-case upward revision came entirely from reports pending verification when Khordad closed on 21 June, not from new death sentences carried out after that date.
Risk
Because Iran publishes no competing official count, every future IHR revision will be reported as if it were new information, even when it is the same lag mechanism repeating.

Sources:Iran Human Rights

Mentions:Iran Human Rights →Iran →Norway →Tehran →EU AI Act →

First Reported In

Update #142 · Doha: three stories, no signed paper

Iran Human Rights· 1 Jul 2026

Read original →

Causes and effects

This Event

140 executions sit beneath the talks

The revised toll puts 140 executions under a fortnight of oil-and-assets diplomacy that has said nothing about Iran's death-penalty surge.

Led to

Monitors report a Tehran death sentence

The sentence extends the repression pattern behind the revised 140-execution Khordad toll.

Occurred 1 Jul 2026

Read story →

Different Perspectives

Oil market and P&I insurers

Brent cleared $87 intraday only once CENTCOM's blockade became physical rather than declared, even though P&I Clubs had already excluded Hormuz war risk a week earlier on 7 July: capital hedged ahead of enforcement, but prices moved only after it.

UAE reporting

UAE reporting placed the Omani tanker deaths at one seafarer against the International Maritime Agency's count of two, the first time in this war that a Gulf state's casualty figures have diverged from an international monitor's.

Jordan

Iranian strikes reached Jordan again on 14 July as part of the Gulf-wide retaliation for the Hormuz blockade, extending the conflict's geographic footprint to a state with no direct stake in the strait itself.

Bahrain

Bahrain sounded air-raid sirens on 14 July during Iran's Gulf-wide retaliation, the same day CENTCOM's blockade order and fourth night of strikes pushed the conflict's physical reach into the wider Gulf littoral.

Kuwait

Kuwait intercepted Iranian missiles and drones on 14 July as Tehran's blockade retaliation reached Gulf states beyond Iran's immediate shoreline, confirming Kuwaiti airspace now sits inside Iran's retaliatory envelope.

Oman

Oman absorbed the war's first tanker casualties in its own waters on 14 July, with two supertankers disabled and seafarers killed, putting the sultanate's shipping lanes directly in the path of the blockade fight for the first time.