IRGC Navy broadcast on VHF Channel 16 turns Hormuz into a live warning zone

At 19:25 UTC on 13 July 2026, a voice identifying itself as the IRGC Navy broke into VHF marine Channel 16, the international hailing and distress frequency, and told every vessel in the Strait of Hormuz and the Oman Sea to stand clear. "For your own safety and safety of your crew, do not approach," the transmission said, according to audio circulated by Middle East Spectator on Telegram at 19:25 UTC and republished minutes later by Geopolitical Watch and DD Geopolitics, both at 19:34 UTC. Channel 16 is the band merchant ships, naval escorts, and port pilots all monitor by default; commandeering it is, in effect, a public broadcast.

Three hours and thirty-eight minutes later, at 23:03 UTC, a second transmission on the same frequency was logged by Shaykh Sulaiman on X: "This is IRGC Navy. Captain, we are firing. I repeat, we are firing. Do you copy?" The post carried the dateline that Iran had fired missiles at several ships being escorted by the United States. The framing, the channel, and the cadence all point to a single conclusion: Tehran is no longer content to shadow US-flagged convoys or warn them by side-band. It is using the mariner's own emergency frequency to choreograph the encounter.

A frequency built for safety, repurposed for warning

Channel 16's purpose is prosaic and universal. It is where a captain calls for a tow, reports a man overboard, or reaches a coast guard. By taking it over in open water, IRGC Navy has done something that more powerful navies have generally avoided in the Gulf: it has converted a safety-of-life-at-sea channel into a warning broadcast, with the implicit promise that the next message could be ordnance. The first transmission at 19:25 UTC framed itself as protective: stand off, the message said, for the safety of your crew. The second at 23:03 UTC dropped the protective framing. "We are firing" is operational, not advisory.

The chain of custody for the audio is short and identifiable. Middle East Spectator published the first clip first, at 19:25 UTC on 13 July 2026, with the timestamp visible on the Telegram post. Two independent Telegram channels, Geopolitical Watch and DD Geopolitics, then reposted the same text at 19:34 UTC, less than ten minutes later. The second transmission was logged at 23:03 UTC by Shaykh Sulaiman on X, with the explicit framing that missiles had been fired at vessels under US escort. The sourcing is unidirectional: the broadcasts themselves came from the IRGC Navy; the circulation came from channels that monitor Gulf maritime traffic and from a correspondent posting on X. No independent Western wire has yet authenticated the second transmission.

What Iran is signalling

Iranian naval doctrine has, for two decades, treated the Strait of Hormuz as an asymmetric battlespace: fast boats, anti-ship cruise missiles arrayed along the northern shore, and a layered threat that pushes Western fleets to operate in formation. The use of Channel 16 fits that playbook but reframes the audience. The audience is no longer just the US Fifth Fleet, operating out of Bahrain, or the commercial tankers that move roughly a fifth of the world's seaborne oil through the strait each day. The audience is every ship within VHF range, and every port operator who listens to Channel 16 in real time.

The likely intent is twofold. First, it places the burden of de-escalation on the mariner: a master who proceeds after a Channel 16 warning does so with the knowledge that a broadcast was logged and disseminated. Second, it produces a record. Telegram channels have already archived the audio; X has logged the second transmission; the maritime press will, in coming days, be reviewing bridge recordings. Each repetition tightens the political cost of an incident, for whichever side is judged to have escalated. The IRGC Navy is, in effect, narrating the encounter as it happens.

What the Western wire line leaves out

Western coverage of Iranian naval activity has tended to frame each incident as a discrete provocation: a boarding, a drone downing, a tanker seizure. The narrower frame is correct as far as it goes; it tracks the event, names the vessel, and reads the protest notes. What it understates is the doctrinal shift on display here. Iran is no longer treating the strait as a stage on which incidents occur; it is treating it as a stage it can direct. The Channel 16 broadcasts are direction, not incident. Read together, the 19:25 UTC warning and the 23:03 UTC "we are firing" message describe a sequence: stand off, then fire if the warning is ignored.

A counter-reading deserves airtime. It is possible that the second transmission, attributed to the moment Iran fired, is in fact a record of an exchange between an IRGC commander and a specific vessel the Iranians believed was about to cross a declared exclusion zone, rather than a general broadcast. The phrasing "Captain, we are firing" is second-person, addressed to one ship, not the universal address used in the 19:25 UTC clip. That nuance matters for legal characterisation: a targeted warning to a single vessel, even on Channel 16, is different from a general broadcast. The sources circulated on 13 July do not resolve which reading is correct.

What remains unverified

The audio quality, the precise vessel(s) under escort at 23:03 UTC, and the identity of the US unit(s) involved are not specified in the circulated material. Neither the US Navy's Bahrain-based public affairs office nor CENTCOM has, in the items available to this publication on 14 July 2026, issued a confirming statement attached to these specific timestamps. Reports from Iranian state media, including outlets such as PressTV, Tasnim, and IRNA, were not part of the wire items reviewed for this article and have not been cited as stand-alone factual bases. Telegram channels that first relayed the 19:25 UTC transmission, including Middle East Spectator, are open-source aggregators; their value is in distributing the audio in near-real-time, not in authenticating it. The 23:03 UTC post on X by Shaykh Sulaiman is a single-source claim that "we are firing" coincided with an Iranian missile engagement of US-escorted vessels; corroboration from a wire service, a national maritime authority, or a Lloyd's List intelligence note is the threshold this publication would normally require before stating that engagement as fact.

What can be stated is narrower and sturdier. At 19:25 UTC on 13 July 2026, a voice identifying itself as the IRGC Navy broadcast a stand-clear warning on VHF Channel 16 to all vessels in the Strait of Hormuz and the Oman Sea. At 23:03 UTC the same day, a second transmission on Channel 16 was logged, addressed to a single "Captain," stating "we are firing." Both transmissions were disseminated by identifiable channels within minutes of release. Both fall inside an Iranian pattern of using public maritime frequencies to communicate intent in the world's most sensitive oil corridor. The next dateline to watch is the first formal acknowledgement from a flag state, an insurance underwriter, or a recognised maritime authority; that acknowledgement will determine whether the second transmission is recorded as a warning, a provocation, or an act of engagement.

This publication framed the 13 July VHF traffic as a documented pattern, not a confirmed engagement. Where the circulated material stops, the article stops; the 23:03 UTC transmission is reported as logged, not as adjudicated.

Wire provenance

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

• https://t.me/s/Middle_East_Spectator
• https://t.me/s/GeoPWatch
• https://t.me/s/DDGeopolitics
• https://t.me/s/Middle_East_Spectator