{"id":1078,"date":"2026-10-23T03:32:52","date_gmt":"2026-10-23T03:32:52","guid":{"rendered":"https:\/\/regulasshipping.com\/blog\/irgc-navy-claims-four-gulf-sts-fires-and-three-mine-hits-west-of-hormuz\/"},"modified":"2026-10-23T03:32:52","modified_gmt":"2026-10-23T03:32:52","slug":"irgc-navy-claims-four-gulf-sts-fires-and-three-mine-hits-west-of-hormuz","status":"publish","type":"post","link":"https:\/\/regulasshipping.com\/blog\/irgc-navy-claims-four-gulf-sts-fires-and-three-mine-hits-west-of-hormuz\/","title":{"rendered":"IRGC Navy claims four Gulf STS fires and three mine hits west of Hormuz"},"content":{"rendered":"<p>Iran\u2019s Islamic Revolutionary Guard Corps Navy issued a Thursday statement claiming seven commercial hulls were damaged overnight Wednesday into Thursday. Reuters, writing from Dubai, printed the split as four vessels involved in what the IRGC called illegal oil transfers in the northern Persian Gulf, tracked on Wednesday, then simultaneously hit and caught fire; and three further vessels that, on the same statement, collided with mines west of the Strait of Hormuz. Al Jazeera, AFP and Associated Press carried the same seven-hull total from Sepah News and Iranian state television. None of those wires printed a ship name, an IMO number, a flag, a cargo grade, a coordinate pair, a casualty line or an independent confirmation. The Associated Press said it could not independently confirm the claims.<\/p>\n<p>This is an IRGC Navy claim file. It is not a UKMTO Attack product. UKMTO has not issued Warning 181-26, or any later numbered PDF, against this overnight. The recent-incidents board does not list a new named Attack or Advisory dated 22 October. It is not an IMO highlighted-incidents increment. The board, as at 22 October, remains 120 confirmed incidents and 24 confirmed seafarer fatalities, with SOYIA and CHLOE still the newest named rows. It is not JMIC Update 107. Update 106 remains the last numbered public note, JMIC# 001 26, information cut-off 181300 UTC 18 October, Hormuz SEVERE, Arabian Gulf SUBSTANTIAL. Thursday afternoon\u2019s dedicated 120-count piece on this desk already told operators not to recast Iranian seven-tanker colour as that board. This morning is the dedicated claim file those wires actually printed.<\/p>\n<p>A U.S. Central Command spokesperson, speaking anonymously to Al Jazeera, called the mine claims incorrect. The spokesperson said U.S. forces have cleared international shipping lanes of mines, that Iran is using missiles and drones, that the strait remains open, and that 95 percent of vessels are getting through. President Donald Trump, on Truth Social the same day, said Iran was doing everything it could to drive up the oil price ahead of the U.S. midterm election and was \u201cmaking up fake hits, mines, and everything else.\u201d That is a political line, not a UKMTO product and not a completed hydrographic survey. Hold both official tapes. Do not brief Thursday as a verified seven-hull Attack board, as a completed minefield, or as a Hormuz closure.<\/p>\n<h2>What the IRGC and the wires actually printed<\/h2>\n<p>The confirmed IRGC tape, as Reuters printed it, is short. Four vessels. Illegal oil transfers, in the IRGC\u2019s wording. Northern Persian Gulf, also printed as northern Arabian Gulf. Tracked by IRGC forces on Wednesday. Simultaneously hit. Caught fire. Three more vessels. Collided with mines west of the Strait of Hormuz. Warning to the U.S. military that continued provocations could lead to a wider response against regional bases. Sepah News, as Al Jazeera quoted it: \u201cThe US military must know that if this trend continues, the conflict will extend to its bases in the region.\u201d \u201cThis is a serious warning.\u201d No names. No flags. No IMO numbers. No times of hit. No fire-extinguished line. No crew-safe line. No pollution line. That is the product.<\/p>\n<p>Wire colour around the same statement is not a naming. Al Jazeera, AFP and AP wrapped the seven-hull total as possibly the largest single-day number of vessels damaged in the waterway since the war that began on 28 February, and they said the claims could not be independently verified. NBC\u2019s reprint of the AP file added that the report did not mention casualties. Arab News, on an AFP rewrite later Thursday, printed four ships hit overnight as they attempted to pass through the wider Gulf, and restated the Sepah News threat against U.S. bases if escorts continue. That AFP geography is \u201cwider Gulf,\u201d not \u201cwest of Hormuz.\u201d Keep Reuters\u2019 northern-Gulf STS-and-fire four and west-of-Hormuz mine three as the working split. Do not collapse the two clusters onto a single Strait of Hormuz Attack, and do not invent a UKMTO coordinate from either wire.<\/p>\n<p>CENTCOM\u2019s rebuttal is also short, and it is a mine rebuttal, not a finding that nothing happened. Lanes cleared of mines. Missiles and drones as the weapons in use. Strait open. Ninety-five percent of vessels getting through. Attacks as \u201cdesperation\u201d under the U.S. blockade of Iranian ports. The 95 percent line is a transit-success figure, not a safe-passage guarantee and not a war-risk cancellation. It sits against the IRGC\u2019s claim of control over the strait and against Trump\u2019s \u201cmore oil is coming through than even prior to the conflict\u201d line. Neither line is a UKMTO transit count. Dedicated UKMTO weekly colour earlier this month had already been printing reduced transits and a reporting gap because many targeted hulls now refuse to report. Do not use Thursday\u2019s CENTCOM percentage to overwrite that reporting-gap file, and do not use the IRGC\u2019s seven-hull total to overwrite IMO 120.<\/p>\n<p>Update 106 already treated an earlier IRGC claim of two fully laden supertankers striking naval mines in Hormuz as unsubstantiated. Thursday\u2019s three-hull mine cluster is the same class of claim until UKMTO, JMIC or IMO take it. JMIC has not issued Update 107. IMO has not added seven unnamed rows. UKMTO has not printed 181-26. A DPA who briefs Thursday as \u201cthe mines are back\u201d on an IRGC statement will over-read the instrument. A DPA who briefs Thursday as \u201cnothing happened because CENTCOM cleared the lanes\u201d will under-read the missile-and-drone line and the fire claim on the northern-Gulf four.<\/p>\n<h2>Operational implications<\/h2>\n<p>For a CSO still running the night shuttle through the Oman-side lane, Thursday is a claim-and-rebuttal file, not a new numbered warning you can pin to a hull. NBC\u2019s reprint of the Associated Press, citing Lloyd\u2019s List Intelligence, is the live operating picture that does not depend on the IRGC naming anyone: tanker operators willing to risk the voyage have been shuttling oil from Gulf producers through the strait at night with location systems and mobile phones turned off, using a U.S.-protected lane near the coast of Oman, then transferring cargo to hulls waiting in the Gulf of Oman for the Asia stem. That geometry already sits on this desk from the Hormuz tape. The IRGC\u2019s \u201cillegal oil transfers\u201d wording is aimed at that STS pattern. Treat the four-hull fire claim as a claimed hit on the northern-Gulf transfer layer, and treat the three-hull mine claim as a claimed hit west of the strait, until a numbered product attaches a name or a NAVAREA.<\/p>\n<p>Damage-control and routing still have to hold two mechanisms at once. If the CENTCOM weapons line is the working one, the overnight risk remains missiles and drones, which is the mechanism UKMTO has been printing as \u201cunknown projectile\u201d on the numbered Attack PDFs. If any part of the IRGC mine line is later taken by UKMTO or a NAVAREA IX hydrographic product, the west-of-Hormuz approaches become a mine-countermeasure and lookout problem as well as a projectile problem. Do not wait for that confirmation to keep a mine-watch in the night orders, and do not treat an IRGC statement as a completed minefield overlay you can plot. There is no official position, no official time, and no official hull. Passage planning, AIS policy, citadel and fire-party readiness, and the decision to wait at Fujairah, Khor Fakkan or Sohar still sit with the company.<\/p>\n<p>Do not merge Thursday onto hulls this desk has already named. SOYIA remains the IMO print on Warning 180-26, 30 nautical miles southeast of Al Faw, 20 October. AL DASMA remains the 20 October Strait second-attack row and the dedicated Warning 179-26 Bukha fire-and-anchor file. CHLOE remains the IMO print on Advisory 178-26, 121 nautical miles from the Oman coast. LOYALTY and ST3 remain the 16 October Al Jubail pair. JIF BARRACUDA remains the 18 October Khor Fakkan tug. None of those rows is a Thursday overnight unnamed seven. Do not invent an 181-26 number as a suppressed Al Dasma rewrite, and do not treat CENTCOM\u2019s 95 percent as a finding that 179-26 or 180-26 did not happen.<\/p>\n<p>War-risk and fixture language should track the verification gap. Underwriters have already been pricing Hormuz as severe and the Arabian Gulf as substantial on Update 106. Thursday does not print a new Joint War Committee circle, a new UKMTO Attack, a new IMO increment, or a closed strait. A charterer who asks whether seven tankers were hit overnight should be answered from the wires: IRGC Navy claim, four northern-Gulf STS fires and three west-of-Hormuz mine collisions, no names, not independently confirmed, CENTCOM rejects the mine mechanism, UKMTO silent, IMO still 120. What can be said is that the shuttle and the Oman-side night lane remain the live pattern, that missiles and drones remain the CENTCOM weapons line, and that a numbered UKMTO, MSCIO or NAVAREA product would be the thing that moves the master\u2019s pack. Do not sell Thursday as a Hormuz reopen or as a completed seven-hull casualty board.<\/p>\n<p>Do not recast 22 October as Update 107, as UKMTO 181-26, as an IMO move past 120, as a naming of Soyia, Chloe or Al Dasma, as a verified minefield west of Hormuz, as a strait closure, or as a rewrite of Thursday afternoon\u2019s 120-count piece or of Wednesday\u2019s 180-26 and 179-26 files. The confirmed facts are the IRGC Navy statement of Thursday 22 October, Reuters\u2019 4+3 split, no independent naming, CENTCOM\u2019s mine rebuttal and 95 percent transit line, IMO still 120 as at 22 October, JMIC still Update 106, and no new UKMTO numbered product.<\/p>\n<h2>What Operators Should Note<\/h2>\n<ul>\n<li><strong>Log an IRGC claim, not a UKMTO Attack.<\/strong> IRGC Navy, Thursday 22 October. Four vessels, \u201cillegal oil transfers,\u201d northern Persian Gulf, tracked Wednesday, simultaneously hit, caught fire. Three further vessels, mines west of the Strait of Hormuz. No names, flags, IMO numbers, times, casualties or pollution line. Reuters, Al Jazeera, AFP and AP could not independently verify. There is no Warning 181-26. Do not invent a number, a coordinate or a hull.<\/li>\n<li><strong>Hold CENTCOM\u2019s mine rebuttal beside the fire claim.<\/strong> Anonymous CENTCOM spokesperson to Al Jazeera: mine claims incorrect; international lanes cleared of mines; Iran using missiles and drones; strait open; 95 percent of vessels getting through. That is a mechanism dispute, not a finding that the four-hull fire claim is closed. Trump\u2019s \u201cfake hits, mines\u201d line is political colour. Do not brief a completed hydrographic survey, and do not drop a mine-watch from the night orders until a NAVAREA or UKMTO product says otherwise.<\/li>\n<li><strong>Leave the official boards on their last prints.<\/strong> IMO highlighted incidents remain 120 confirmed, 24 dead, as at 22 October, with SOYIA (9263916) and CHLOE (MIVERVA V, 9315367) still the newest named rows. JMIC remains Update 106, ICOD 181300 UTC 18 October, Hormuz SEVERE, Arabian Gulf SUBSTANTIAL. UKMTO\u2019s last numbered Attacks on this desk remain 179-26 (Bukha) and 180-26 (Al Faw). Update 106 already treated an earlier IRGC two-supertanker mine claim as unsubstantiated. Thursday is the same class until those instruments move.<\/li>\n<li><strong>Keep the night shuttle and the STS layer on their own geometry.<\/strong> Lloyd\u2019s List Intelligence, via the AP file: night transits, AIS and phones off, U.S.-protected Oman-side lane, cargo handed to waiting hulls in the Gulf of Oman. The IRGC\u2019s \u201cillegal oil transfers\u201d wording is aimed at that pattern. Treat the claimed four as a northern-Gulf transfer-layer hit and the claimed three as a west-of-Hormuz mine cluster. Do not collapse both onto a single Strait Attack, and do not treat Fujairah, Khor Fakkan or Sohar waiting hulls as covered by CENTCOM\u2019s 95 percent figure.<\/li>\n<li><strong>Do not merge Thursday onto named rows.<\/strong> Soyia is 180-26\u2019s Al Faw IMO print. Al Dasma is the 20 October Strait second-attack row and the dedicated 179-26 Bukha fire-and-anchor file. Chloe is 178-26\u2019s Duqm-offset IMO print. Loyalty, ST3 and Jif Barracuda remain the mid-October named tape. None of them is a Thursday overnight unnamed seven. Report contacts to UKMTO and to the flag. Do not wait for an IRGC naming that the statement did not give.<\/li>\n<li><strong>Do not sell a closure or a reopen into the fixture.<\/strong> Thursday prints neither a Joint War Committee change, a NAVAREA IX mine warning, a UKMTO Attack, an IMO increment, nor a Hormuz closure. War-risk, laycan flexibility and the decision to run the night lane remain company decisions. Answer a charterer with the verification gap, not with a seven-hull board. Keep the Black Sea files on their own desk; this is a Gulf and Hormuz claim file.<\/li>\n<\/ul>\n<p>Regulas Shipping will keep lining Thursday\u2019s IRGC Navy 4+3 claim against UKMTO numbered products, IMO\u2019s 120-count board and JMIC Update 106 so operators can treat the overnight as an unverified statement with a CENTCOM mine rebuttal, not as a completed Attack board or a Hormuz closure.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Iran\u2019s Islamic Revolutionary Guard Corps Navy issued a Thursday statement claiming seven commercial hulls were damaged overnight Wednesday into Thursday. Reuters, writing from Dubai, printed the split as four vessels involved in what the IRGC called illegal oil transfers in the northern Persian Gulf, tracked on Wednesday, then simultaneously hit and caught fire; and three [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":1076,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"wpai_generated_summary":"","wpai_meta_description":"","footnotes":""},"categories":[26,18,4],"tags":[],"class_list":["post-1078","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-highlights","category-maritime-industry","category-maritime-security"],"_links":{"self":[{"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/posts\/1078","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/comments?post=1078"}],"version-history":[{"count":0,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/posts\/1078\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/media\/1076"}],"wp:attachment":[{"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/media?parent=1078"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/categories?post=1078"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/tags?post=1078"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}