Qatar Gas Transport Company (Nakilat) published a numbered company statement titled “AL Mayeda – vessel incident in the Arabian Gulf,” dated 30 October 2026, and still live on the company site this Sunday afternoon. The same text was carried on the Qatar Stock Exchange company-disclosure board. Nakilat confirms that its LNG carrier Al Mayeda was hit by unidentified objects while transiting the Arabian Gulf on Friday evening, 30 October 2026. None of the crew members onboard were injured, and there is no impact on the environment as a result of this incident. The vessel is in a safe condition, operational, and the impact of the incident is being assessed. Nakilat remains in direct coordination with the vessel, its crew and the relevant maritime security authorities in the region to ensure the safety of the crew, while continuing to closely monitor the situation. The closing line states that the safety of people, protection of the environment, and the integrity of assets remain Nakilat’s highest priorities.
That is the working primary. Sunday afternoon’s product is an official operator and exchange disclosure, not a UKMTO PDF, not an MSCIO alert, and not a NAVAREA IX keep-clear. It names a hull. It names a type as LNG carrier. It names the owner as Nakilat. It names a Friday-evening Arabian Gulf clock. It names the method as unidentified objects. It prints a crew-uninjured line, a no-environmental-impact line, and a vessel-safe-and-operational line. It does not print a latitude, a longitude, a port-side or starboard-side hit, a fire, a projectile, an attacker, a keep-clear radius, a disruption or a corridor closure. Friday night’s dedicated UKMTO Warning 188-26 piece on this desk, published about 23:38 UTC on 30 October, still told operators that UKMTO had printed an unnamed vessel Attack, 1800 UTC, 40 nautical miles south of Lavan Island, port-side unknown projectile, fire onboard, crew reported safe, no reported environmental impact, and that the public PDF named neither hull nor IMO. Masters who brief Sunday afternoon as a rewrite of 188-26, as unused 186-26 finally named, as a completed Update 110, or as an IMO 123-count will have merged a named LNG-carrier disclosure into four other series.
What the statement actually printed
The confirmed tape is the body of the Nakilat statement. Qatar Gas Transport Company (Nakilat) confirms that its LNG carrier Al Mayeda was hit by unidentified objects, while transiting the Arabian Gulf on Friday evening, 30 October 2026. None of the crew members onboard were injured. No impact on the environment. Vessel in a safe condition, operational. Impact of the incident being assessed. Direct coordination with the vessel, its crew and the relevant maritime security authorities. Closely monitor the situation. That is the product. Stay with that wording. Do not invent a latitude. Do not invent a Lavan, Khasab, Musandam or Ra’s Tahir offset. Do not invent a fire line, a projectile line, a port-side line or an engine-room line. Those sentences sit on Friday night’s dedicated 188-26 and on Friday morning’s dedicated 187-26. They do not sit on this disclosure. Do not invent an IMO number, a call sign or a flag on the face of the Nakilat text. The statement does not print them. Do not invent a cargo quantity on board, a boil-off figure, a next port, or a force-majeure notice. Do not invent an attacker, an IRGC claim, or a completed class survey.
The product type is the first briefing fact. This is an owner statement on a named LNG carrier, published on the company site and on the Qatar Stock Exchange, not the Attack family that ran dedicated 187-26, 188-26 and 189-26, not the Suspicious Activity family that ran dedicated 190-26 and 185-26, and not the Advisory family that ran 184-26. Nakilat says its LNG carrier was hit by unidentified objects in the Arabian Gulf on Friday evening and that the hull remains safe and operational. It does not say a crude-oil tanker was struck. It does not say the ship was disabled, NUC, under tow, at anchor or on fire. A DPA who briefs Sunday afternoon as “another Hormuz Attack, fire out, crew safe” has borrowed 188-26’s projectile-and-fire lines and has dropped the named LNG-carrier disclosure that is the whole of this note. A DPA who briefs Sunday afternoon as a completed UKMTO naming because 188-26 already printed Friday 1800 UTC and a crew-safe line has under-read a company text that still withholds a plot and a weapon type.
The clock and the basin are the second briefing fact. The statement sits on Friday evening, 30 October 2026, in the Arabian Gulf. It does not sit in the Strait of Hormuz TSS. It does not sit 25 nautical miles northeast of Khasab. It does not sit 9 nautical miles north of Khasab. It does not sit 40 nautical miles south of Lavan Island. Those offsets belong to dedicated UKMTO and NAVAREA files. Nakilat printed “Arabian Gulf” and “Friday evening.” That is a basin and a session, not a surveyed strike coordinate. Channel 16, the UKMTO emergency line, the MSCIO emergency line and the company duty officer still have to be on the night orders for any hull working the Gulf, the Strait or the Fujairah / Khor Fakkan density. Do not treat “LNG carrier” as a crude-oil-tanker naming. Do not treat “unidentified objects” as a completed projectile finding. Do not treat “operational” as a completed damage survey or as a published next-port order.
Open-source particulars of the named hull, held separately from the Nakilat text: Al Mayeda is printed in Equasis-style registers and in Nakilat’s own fleet list as a Q-Max LNG carrier, IMO 9397298, delivered 2009 by Samsung Heavy Industries at Geoje, about 266,000 cubic metres capacity, Marshall Islands flag in those registers, managed in open sources by Nakilat Shipping. Those particulars identify the hull Nakilat named. They are not a UKMTO print, not an MSCIO print, and not an IMO highlighted-incidents row. Saturday afternoon’s dedicated IMO board remains 122 confirmed / 24 seafarer fatalities as at 30 October and does not carry Al Mayeda. Do not promote IMO 9397298 onto Warning 188-26. Do not promote a Q-Max cubic-metre figure onto a UKMTO PDF that still says “vessel.”
Industry colour of the same clock, held separately: Gulf Times, Gulf News and Anadolu restated the Qatar Stock Exchange disclosure on Sunday, some of them using the word “attacked” in a headline. The body they quote is still Nakilat’s unidentified-objects sentence, the crew-uninjured sentence, the no-environmental-impact sentence and the operational sentence. Treat those reprints as industry colour of the public disclosure. Do not collapse them onto 188-26 as a completed identification of Friday night’s unnamed vessel. The public UKMTO PDF as retrieved still does not print Al Mayeda, IMO 9397298, LNG or Q-Max. Do not promote a stock-exchange card to an 188-26 location footer.
What this is not
This is not a rewrite of 188-26, and it is not a UKMTO hull naming. Friday night’s dedicated Warning 188-26 remains an unnamed Attack product, incident 30 October 2026, 1800 UTC, source Master: vessel hit by an unknown projectile on the port side which caused a fire onboard; crew reported safe; no reported environmental impact; location footer Lavan Island, Iran; transit with caution; report to UKMTO. 188-26 printed neither hull, IMO, flag, cargo type, attacker nor a keep-clear radius. Nakilat’s statement is an owner disclosure, LNG carrier, Al Mayeda, unidentified objects, Friday evening, Arabian Gulf, crew uninjured, no environmental impact, vessel operational. 188-26 is UKMTO, Attack, unnamed vessel, unknown projectile, port side, fire, 40 nautical miles south of Lavan. Two Friday-evening Gulf products are two products. Do not merge Friday night’s unnamed projectile-and-fire Attack onto Sunday’s named LNG-carrier disclosure because both print a crew-safe line and no environmental impact. Do not convert Al Mayeda into 188-26’s unnamed hull unless a later UKMTO PDF, flag note, class note, JMIC update or NAVAREA prints Al Mayeda against the 1800 UTC clock. This desk has not retrieved that print.
This is not a rewrite of unused 186-26, dedicated 187-26 or dedicated 189-26. Unused Warning 186-26 remains a CSO Attack: tanker struck by an unknown projectile at 1600 UTC 29 October whilst completing an outbound Hormuz transit, no reported injuries, no environmental impact report, location footer Khasab, Oman. Dedicated Warning 187-26 Update 001 remains an unnamed outbound tanker Attack, 2212 UTC 29 October, 25 nautical miles northeast of Khasab, two explosive devices attached above the waterline, engine-room fire extinguished, continuing. Dedicated Warning 189-26 remains a time-late Attack: crude oil tanker, unknown projectile, outbound Strait of Hormuz, 28 October, time TBC. Nakilat prints Al Mayeda, an LNG carrier, unidentified objects, Friday evening, Arabian Gulf, operational. A projectile, a crude-oil tanker, attached devices and a Hormuz outbound clock are not a named Q-Max disclosure. Do not convert Al Mayeda onto those Attacks as a late naming. Do not promote Louise 1, RIT1, Panama or 25-crew onto this statement.
This is not a rewrite of 420/26, and it is not a rewrite of 182-26. Friday night’s dedicated NAVAREA IX 420/26 remains OIL TANKER (RITI) on fire and anchored at 26-24.07N 056-24.72E, about 1 NM northwest of Ra’s Tahir. Saturday afternoon’s dedicated IMO board and this afternoon’s dedicated Update 109 name GHANA PROSPERITY against 182-26 as a crude-oil tanker disabled and anchored about two nautical miles off Musandam. Al Mayeda is an LNG carrier. RITI is an oil tanker. Ghana Prosperity is a crude-oil tanker. Three hulls. Do not merge a Nakilat Q-Max onto a Ra’s Tahir fire-and-anchor or onto a Musandam disablement because all three print a Friday or late-October Gulf clock.
This is not Update 110, and it is not an International Maritime Organization 123-count. This afternoon’s dedicated JMIC Update 109, JMIC# 001 26, ICOD 291300 UTC 29 October, remains the last numbered public periodic note, with Hormuz SEVERE, the Arabian Gulf SUBSTANTIAL, the Gulf of Oman MODERATE and 160 incidents since 1 March. Update 109’s last 96-hour list ends at 185-26. Al Mayeda is not on that list. Saturday afternoon’s dedicated IMO highlighted-incidents board remains 122 confirmed / 24 seafarer fatalities as at 30 October, with Ghana Prosperity’s second Strait row as the newest named line. A Nakilat LNG-carrier disclosure does not fill those slots and does not belong on that Middle East highlighted-incidents table as a completed IMO increment. Wednesday afternoon’s dedicated JMIC Advisory Note 016-26 remains the blockade visit-and-search document pack. This is not Thursday’s dedicated Contship Jet or Khoryv Black Sea files, and it is not Saturday’s dedicated NAVWARN 775/26, 776/26 or 777/26.
This is not a confirmed fire, a completed disablement, or a corridor closure. Nakilat prints unidentified objects, crew uninjured, no environmental impact, vessel safe and operational, impact being assessed. It does not print a fire-main problem. It does not print NUC, a tug, a tow or an anchorage. It does not print a Ras Laffan, Fujairah or Khor Fakkan arrival. Do not promote “impact being assessed” to a completed class condition or to a published off-hire. Do not promote “Arabian Gulf” to a surveyed Lavan offset. Do not close the Strait or the Gulf on the back of an owner disclosure that still tells operators the hull is operational.
Operational implications
For a master already in the Arabian Gulf, shaping Musandam, or holding on a Fujairah / Khor Fakkan / Ras Laffan approach, Sunday afternoon is a lookout and reporting problem before it is a commercial problem. Nakilat printed a named Q-Max hit by unidentified objects on Friday evening and printed the hull as still operational. That is a company all-clear on crew and environment, not a completed damage survey and not a published plot. A named LNG carrier that has already been hit and is still making way is a traffic and identification problem for every other hull in the same density: AIS name, radar echo, and the risk that a second set of unidentified objects is still in the water. The working instruction on the dedicated UKMTO Attack files remains transit with caution and report to UKMTO. The working instruction on this disclosure is that the named owner says the crew are uninjured, there is no environmental impact, and the ship is operational. Those are different desks and different sentences. Do not drop BMP-MS because an owner said operational. Do not invent a keep-clear around Al Mayeda that Nakilat did not print.
For a DPA and an operator with LNG, LPG or crude hulls in the Gulf this week, the naming split is the operational content. Sightings of Al Mayeda, of unidentified objects near an LNG carrier, of a fire that this statement does not print, or of a close CPA go to UKMTO on the standing 188-26 and 187-26 lines, to MSCIO on the standing MSCIO Attack lines, and to the company security officer. Registering with one mailbox is not a substitute for the other. NAVCENT NCAGS remains the 016-26 blockade mailbox for hulls that still need the Strait. Nakilat’s statement does not order a daylight-only transit, a deviation around 26-24.07N 056-24.72E beyond the existing RITI caution, or a halt to visit-and-search compliance. It also does not authorise a master to treat every Q-Max in the Gulf as a confirmed 188-26 after the fact. Log the statement date, the Friday-evening clock, the Arabian Gulf basin, the name Al Mayeda, the LNG-carrier type, the unidentified-objects method, the crew-uninjured line, the no-environmental-impact line, the operational line, and the “impact being assessed” line. Do not log Lavan, a port-side projectile, a fire, RITI, Ghana Prosperity, Louise 1, or an 188-26 naming that the UKMTO PDF does not print.
Open-source particulars change the manning conversation without changing the official tape. A Q-Max of about 266,000 cubic metres is not a product tanker and is not a 50,000-tonne handy. Charterers, P&I and war-risk underwriters will now ask whether the ship was in the Arabian Gulf on Friday evening, whether it was an LNG carrier, whether it reported a hit by unidentified objects, and whether the owner’s operational sentence matches the master’s noon report. They will not be answered by Friday night’s unnamed 188-26 Attack, by Saturday morning’s 189-26 time-late Hormuz Attack, by this afternoon’s Update 109, or by Saturday afternoon’s IMO 122-count. Off-hire and deviation conversations that treat Al Mayeda as a Hormuz TSS fixture problem, or as RITI under another name, have misread the product type and the basin.
The missing plot, fire and weapon lines are the practical watch, not a completed all-clear. The official tape says unidentified objects and operational. It does not say whether the objects were projectiles, attached devices, debris or something else. It does not say where in the Gulf the hit occurred. It does not say whether a fire was fought and not mentioned, or whether there was never a fire. Those missing lines are omissions. They are not a completed “all well” beyond the crew and environment sentences Nakilat did print, and they are not a confirmed 188-26 naming. Next-port authorities will want a written account that this disclosure does not contain. Keep Update 109’s Arabian Gulf SUBSTANTIAL / Hormuz SEVERE lines and 016-26 visit-and-search in the master’s pack. Watch a UKMTO PDF that prints Al Mayeda against the 1800 UTC clock, an MSCIO alert that names the hull, a NAVAREA that plots this Q-Max, a flag or class note, an IMO-board move off 122, or a JMIC Update 110 — not a headline that Sunday afternoon closed Friday night’s Lavan file or completed unused 186-26.
Keep the dedicated files on their own lines. 188-26 remains Friday night’s unnamed vessel Attack 40 nautical miles south of Lavan Island, port-side projectile, fire, crew reported safe. 187-26 remains Friday morning’s unnamed outbound-tanker Attack 25 nautical miles northeast of Khasab. 189-26 remains Saturday morning’s unnamed time-late Hormuz crude-oil-tanker Attack. 186-26 remains the unused 1600 UTC unknown-projectile Attack. 185-26 remains Thursday’s 9-nautical-mile north-of-Khasab fire sighting. 183-26 remains the 26 October Al-Faw fire. 182-26 remains the 23 October outbound-Hormuz disablement, named Ghana Prosperity on Update 109 and on Saturday afternoon’s IMO 122-count as wrap, not as an Al Mayeda hull. 420/26 remains Friday night’s dedicated RITI fire-and-anchor. 417/26 remains Friday morning’s dedicated MSV Quba wreck. Update 109 remains this afternoon’s dedicated periodic threat note. 016-26 remains Wednesday afternoon’s blockade document pack. 190-26 remains Saturday night’s unnamed fishing-vessel boarding. 161/26 remains Sunday morning’s dedicated AZINI hijack. Saturday’s dedicated 775/26, 776/26 and 777/26 remain the Bulgarian territorial-sea e-mail, the Galata diving box and the Burgas cutter. Sunday morning’s dedicated ARN 162/2026 remains the Romanian two-nautical-mile drifting-object watch. Do not recast 1 November afternoon as a UKMTO naming, as unused 186-26 finally published, as Update 110, as an IMO 123-count, or as a corridor closure.
What Operators Should Note
- Log the Nakilat disclosure as a named LNG-carrier hit with an operational line, not as a rewrite of 188-26 and not as a UKMTO naming. Qatar Gas Transport Company (Nakilat), “AL Mayeda – vessel incident in the Arabian Gulf,” dated 30 October 2026, company site and Qatar Stock Exchange. LNG carrier Al Mayeda hit by unidentified objects while transiting the Arabian Gulf on Friday evening, 30 October 2026. Crew uninjured. No environmental impact. Vessel safe, operational, impact being assessed. Coordinating with the vessel, crew and relevant maritime security authorities. Nakilat printed neither lat/long, fire, projectile, port side, attacker, keep-clear radius, disruption nor a corridor closure. This is not 188-26, not 187-26, not 189-26, not 420/26, and not Update 109.
- Hold the clock, the basin and the product type. This is an owner and exchange disclosure, not Attack, not Suspicious Activity and not Advisory. The working date is Friday evening, 30 October 2026. The working basin is the Arabian Gulf, not a printed Lavan, Khasab or Musandam offset. The working hull is Al Mayeda, LNG carrier, not a crude-oil tanker and not an unnamed “vessel.” The working method is unidentified objects, not an unknown projectile on the face of this text and not two attached devices. Do not brief Sunday afternoon as “Friday night’s unnamed Lavan Attack, now named.” Do not brief Sunday afternoon as quiet because the statement says operational.
- Hold 188-26 on its own line until a UKMTO PDF prints Al Mayeda. Warning 188-26 remains the dedicated 1800 UTC 30 October unnamed vessel Attack, 40 nautical miles south of Lavan Island, port-side unknown projectile, fire, crew reported safe, no reported environmental impact. It still prints no hull and no IMO on the public PDF as retrieved. Do not promote Al Mayeda to an 188-26 naming. Do not promote 188-26’s Lavan footer onto the Nakilat statement. Two Friday-evening Gulf products are two products until an official series joins them.
- Hold open-source particulars as particulars, not as a UKMTO or IMO print. Registers and Nakilat’s fleet list identify Al Mayeda as IMO 9397298, Q-Max, about 266,000 cubic metres, 2009 Samsung Geoje, Marshall Islands in those registers. Saturday’s dedicated IMO board remains 122 / 24 as at 30 October and does not carry this hull. This afternoon’s dedicated Update 109 names Ghana Prosperity against 182-26, not Al Mayeda. Do not write IMO 9397298 onto Warning 188-26. Do not write a Q-Max cubic-metre figure onto a PDF that still says vessel.
- Treat the missing plot, fire and weapon lines as open watch lines. The official tape does not print a coordinate, a fire-main problem, NUC, a tow or a next port. It does print crew uninjured, no environmental impact, and operational. Keep Update 109 Arabian Gulf SUBSTANTIAL / Hormuz SEVERE and 016-26 visit-and-search in the master’s pack. Report to UKMTO and keep the MSCIO mailbox current. Do not invent a keep-clear around Al Mayeda. Do not drop BMP-MS because the owner said operational. Watch a UKMTO PDF that prints Al Mayeda, an MSCIO alert that names the hull, a NAVAREA that plots this Q-Max, a flag or class note, an IMO-board move off 122, or a JMIC Update 110 — not a headline that Sunday afternoon closed Friday night’s Lavan file.
- Do not collapse 187-26, 189-26, unused 186-26, 420/26 or 182-26 onto this name. 187-26 remains the dedicated 2212 UTC attached-device Attack 25 nautical miles northeast of Khasab. 189-26 remains the dedicated time-late outbound-Hormuz crude-oil-tanker Attack. 186-26 remains the unused 1600 UTC 29 October CSO unknown-projectile Attack, Khasab footer. 420/26 remains Friday night’s dedicated RITI fire-and-anchor at 26-24.07N 056-24.72E. 182-26 remains the dedicated 23 October unnamed outbound-Hormuz disablement, named Ghana Prosperity on Update 109 and on Saturday’s IMO 122-count as wrap. Five late-October tanker products are five products. They are not a Nakilat Q-Max.
Regulas Shipping will keep lining Nakilat’s Al Mayeda disclosure against Friday night’s dedicated Warning 188-26 so operators can treat Sunday afternoon’s tape as a named LNG-carrier hit with an operational line, not as a UKMTO naming, a Lavan rewrite, or a completed Update 110.
