Skip to content
Sanctioned vessel

Clipper appears on the OFAC SDN list under IRAN-EO13902. Verify at OFAC.

Every vessel on:OFAC SDN list

Clipper

LPG carrier · built 1992

IMO8917807No AIS position on record

In short

Clipper (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
1992
Gross tonnage
45,032
Size (length × beam)
223 m × 36 m
Registered owner
—

Watch this ship

Get an email when Clipper 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 Clipper.

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-up

Identity & particulars

Name
Clipper
IMO numberWhat is an IMO number?
8917807
Flag
—
Vessel type
LPG carrier
Gross tonnageGross tonnage vs deadweight
45,032
Length overall
223 m
Beam
36 m
Year built
1992

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.

DateEventSource
Reported departure from ELIZABETH RIVER (SOUTHERN BRANCH) VAAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at ELIZABETH RIVER (SOUTHERN BRANCH) VAAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from Marcus HookAuthority-reportedUSACE 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.

Former and other names

Names attested for this ship other than its current name.

NameEvidenceDateSource
DOUBLE INName on a sanctions list—OFAC Specially Designated Nationals list

A sanctions list's date is the earliest date the list shows the name, not when the ship took it. A name on a list is shown as a former name only where AIS shows the ship using another name after that date; otherwise it is listed as a name the list uses. AIS name changes are dated when Voydar saw them.

Source: OFAC Specially Designated Nationals list. Licence: US Government public domain (17 U.S.C. §105).

Sanctions listings

Every listing of this ship on the sanctions lists Voydar tracks, current and past.

ListProgrammeListed asListedStatus
OFAC SDN list (US)IRAN-EO13902DOUBLE INnot published by the listIn 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

PortRecordDate (UTC)BerthSource
ELIZABETH RIVER (SOUTHERN BRANCH) VADepartureJan 18, 2007(date only)—USACE foreign traffic vessel entrances & clearances
ELIZABETH RIVER (SOUTHERN BRANCH) VAArrivalJan 17, 2007(date only)—USACE foreign traffic vessel entrances & clearances
Marcus Hook USMAHDepartureJan 13, 2007(date only)—USACE foreign traffic vessel entrances & clearances
Marcus Hook USMAHArrivalJan 13, 2007(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)DepartureOct 18, 2006(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)ArrivalOct 17, 2006(date only)—USACE foreign traffic vessel entrances & clearances
Tampa USTPADepartureSep 11, 2006(date only)—USACE foreign traffic vessel entrances & clearances
Tampa USTPAArrivalSep 9, 2006(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)DepartureSep 6, 2006(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)ArrivalSep 4, 2006(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)DepartureJul 28, 2006(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)ArrivalJul 27, 2006(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: May 21, 2003.

Frequently asked questions

Where is Clipper now?
Voydar has no displayable AIS position for Clipper in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is Clipper?
Clipper is an LPG carrier, built in 1992 by NKK. The vessel is 223 m long with a beam of 36 m and has a gross tonnage of 45,032.
What sanctions and inspection records does Voydar hold for Clipper?
Clipper appears on the OFAC SDN list under IRAN-EO13902. No matched inspection records are displayed for Clipper. 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/8917807
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

Using 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.

See plans