Sea Opera appears on the OFAC SDN list under IRAN-EO13902. Verify at OFAC.
Every vessel on:OFAC SDN list
Sea Opera
LPG carrier · built 1991
In short
Sea Opera (LPG carrier) has no AIS position on record with Voydar. It appears on a sanctions list (details below).
- Vessel type
- LPG carrier
- Flag
- —
- Year built
- 1991
- Gross tonnage
- 42,286
- Size (length × beam)
- 224 m × 36 m
- Registered owner
- —
Watch this ship
Get an email when Sea Opera arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
We email you a link and a code. That creates a free account, no password or card, and follows Sea Opera.
Free account, no card: follow up to 5 ships and ports. Plus follows 50, Pro 500.
By continuing you accept the Terms and the Privacy policy.
Last reported position
No AIS position on record for this vessel. Identity and particulars are below.
A year of history in the Terminal (Plus) · the full archive since June 1, 2026 (Pro)
Try the live demo, no sign-upIdentity & particulars
- Name
- Sea Opera
- IMO numberWhat is an IMO number?
- 9000883
- MMSIWhat is an MMSI?
- —
- Call signWhat is a call sign?
- —
- Flag
- —
- Vessel type
- LPG carrier
- Gross tonnageGross tonnage vs deadweight
- 42,286
- Deadweight (DWT)
- Source: Wikidata, record Q117008689. Added to Voydar on September 23, 2026. Licence: CC0 1.0.49,345 t
- Length overall
- 224 m
- Beam
- 36 m
- Year built
- 1991
A tag next to a value names the register that supplied it (hover or tap it for the record and date). Values without a tag come from the ship's own AIS broadcasts or from Wikidata. Position and identity are derived live from AIS.
Ownership & management
Each line shows where the fact comes from. Links backed by an identifier point to the company page.
- Builder
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
Timeline
Dated events for this ship from every source Voydar holds, newest first. Each line names its source; derived items say how they were derived.
| Date | Event | Source |
|---|---|---|
| Reported departure from HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)Authority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)Authority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from Baton RougeAuthority-reported | USACE foreign traffic vessel entrances & clearances |
Owner, operator and manager changes found by comparing yearly EU MRV reports are dated to the reporting year ("during 2025"), not to a day. Port calls here are the most recent only; the full lists are further down.
Sanctions listings
Every listing of this ship on the sanctions lists Voydar tracks, current and past.
| List | Programme | Listed as | Listed | Status |
|---|---|---|---|---|
| OFAC SDN list (US) | IRAN-EO13902 | SEA OPERA | not published by the list | In force |
Source: OFAC Specially Designated Nationals list. Licence: US Government public domain (17 U.S.C. §105).
Port calls
Two kinds of evidence, kept apart: calls Voydar detected from the ship's AIS positions, and arrivals and departures published by port authorities and customs records.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Aug 19, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Aug 18, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baton Rouge USBTR | Departure | Jul 5, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New Orleans USMSY | Arrival | Jun 29, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baton Rouge USBTR | Departure | Jun 13, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New Orleans USMSY | Arrival | Jun 10, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Apr 10, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Apr 7, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Mar 17, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Mar 15, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ELIZABETH RIVER (SOUTHERN BRANCH) VA | Departure | Feb 9, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ELIZABETH RIVER (SOUTHERN BRANCH) VA | Arrival | Feb 9, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: May 21, 2005.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
Frequently asked questions
- Where is Sea Opera now?
- Voydar has no displayable AIS position for Sea Opera in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
- What kind of ship is Sea Opera?
- Sea Opera is an LPG carrier, built in 1991 by Sakaide Works. The vessel is 224 m long with a beam of 36 m and has a gross tonnage of 42,286.
- What sanctions and inspection records does Voydar hold for Sea Opera?
- Sea Opera appears on the OFAC SDN list under IRAN-EO13902. No matched inspection records are displayed for Sea Opera. Missing records do not establish whether the ship has been detained.
Use this data
This page is also available as JSON, free, with the source and licence of every section. Sections whose sources do not permit redistribution are listed as withheld.
GET /api/v1/vessels/9000883Using this data in code?
Every account gets a personal API allowance: 2,500 credits a month free, 25,000 with Pro. Pro adds internal business use; API plans add building the data into your own products.