Yemen's Ansarullah publishes Saudi strike coordinates as Riyadh confirms interception

Saudi air-defence systems engaged incoming projectiles on the afternoon of 13 July 2026, according to a coalition spokesperson, after Yemeni forces launched what one monitor described as at least six rockets towards a Saudi airport. The acknowledgement came within the same hour as a separate claim from Ansarullah-aligned media publishing the coordinates of Saudi airports and ports it identified as likely targets of follow-on strikes.

The exchange resets the escalation clock on a front that has run hot in fits and starts since the Houthi movement began targeting Saudi and Emirati territory in late 2024. What is different this round is sequencing: the targeting coordinates were published before Riyadh confirmed the first impact, a reversal of the usual information order and a deliberate pressure tactic.

What the coalition said

The spokesman of the Saudi-led coalition confirmed at 17:29 UTC that the kingdom's air-defence systems had "faced the threat" posed by the incoming fire, according to the English service of Iran's Tasnim News. Tasnim is Iranian state media and a documented outlet for Ansarullah-aligned messaging, but its reporting here is corroborative: it reproduces a Saudi acknowledgement of an interception event rather than asserting the strike itself. The Saudi acknowledgement, in turn, follows the pattern of prior admissions in this conflict: a generic engagement notice, no immediate damage disclosure, and a separate Ministry of Interior directive issued within minutes.

That directive, reported by Tasnim at 17:30 UTC and by JahanTasnim shortly after, banned any photography or videography of sites that had been struck. In practice, this is what Saudi authorities have done after every prior Houthi strike on the kingdom: suppress the open-source visual record while the official line is shaped by coalition statements. It is also why almost all imagery of today's impact points, if any exist publicly, will surface through channels other than Saudi-based eyewitnesses.

What Ansarullah published

At 18:05 UTC, Telegram channels aligned with Ansarullah (the political umbrella of the Houthi movement) circulated a video that purports to specify the coordinates of "important airports and ports of Saudi Arabia" framed as future target sets. The clip is a propaganda product and should be read as such: it is intended to deter, to claim reach, and to put civilian and military logistics nodes on notice. But it is also a piece of military signalling that travels through a recognised channel, and Saudi planners will treat it as a targeting threat rather than rhetoric.

Earlier in the afternoon, at 17:48 UTC, the X account @sprinterpress reported that "six Yemeni rockets" had been launched towards a Saudi airport, citing "sources" without naming them. The same timestamp window carried an unsourced reference to an explosion heard inside Saudi territory. None of the available sources identify the specific Saudi airport by name, and the Saudi coalition statement does not specify how many projectiles were engaged or whether any reached their targets.

Why the information order matters

The standard arc of a Houthi-into-Saudi strike runs like this: claim from Sanaa, denial or silence from Riyadh, eventually an oblique coalition acknowledgement, then visual evidence filtered through censorship. The sequence on 13 July 2026 inverts the claim step. The coordinate release landed after Riyadh's acknowledgement and after the photography ban, which means the intended audience is partly domestic Saudi (to communicate that further strikes are coming) and partly foreign-asset and shipping (to signal which nodes are now in scope for disruption or symbolic strikes).

This is the same logic that has governed Houthi operations in the Red Sea and Bab el-Mandeb: a campaign of named-target signalling that aims to extract diplomatic and economic concessions without a full ground war. The expansion of that logic onto Saudi soil is not new, but the publication of precise-looking coordinates for civilian aviation and port infrastructure pushes the signalling past symbolic missile volleys and into the territory of pre-operational disclosure.

Stakes and what to watch

Two trajectories are now in play. The first is kinetic: how many projectiles reach their targets, what damage is acknowledged, and whether Saudi airspace or specific airports are closed. The Saudi photography ban is itself a leading indicator that authorities expect further strikes within the same operational cycle and want to constrain the visual record. The second is diplomatic: whether the coordinate release produces a mediated response through Omani or UN channels, which has been the historical off-ramp for these exchanges, or whether the signalling instead triggers an overt Saudi retaliatory cycle.

The open questions the sources do not resolve are basic and matter. The number of projectiles actually fired is one number on each side: Ansarullah-aligned reporting tends to inflate; coalition reporting tends to compress. The specific Saudi site under fire is not named in any of the items reviewed. Whether any airport or port was forced to suspend operations, even briefly, is not confirmed. And the relationship between today's strike and the broader pattern of Yemeni operations against Red Sea shipping is not addressed by the available reporting, even though that pattern is the structural backdrop against which any Saudi-targeted escalation will be priced by insurers, shippers, and Gulf-state foreign ministries.

What is clear from the record is that on 13 July 2026, at roughly 17:29 to 18:05 UTC, both sides of this conflict were talking to each other and to the world at the same time, and the Saudis lost control of the information cycle within an hour of acknowledging the attack. That is the story the coordinates video is selling, and it is the part of today's events that is least in dispute.

Desk note: This piece leans on Telegram-sourced dispatches from Iranian state media that reproduce Saudi coalition statements. The Saudi framing is taken from those statements, not from independent Saudi reporting, because independent Saudi reporting on these events is, by the Interior Ministry directive cited above, prohibited at source. Where wire confirmation is unavailable, this publication flags the gap rather than inferring it.

Wire provenance

This editorial synthesis draws on the following public wire/social posts:

• https://t.me/JahanTasnim
• https://t.me/JahanTasnim
• https://t.me/JahanTasnim
• https://t.me/tasnimnews_en
• https://t.me/tasnimnews_en