Skip to content
Sanctioned vessel

IMO 9260055 appears on the OFAC SDN list under SDGT. Verify at OFAC.

Every vessel on:OFAC SDN list

IMO 9260055

Tanker · built 2003

IMO9260055No AIS position on record

In short

IMO 9260055 (Tanker) has no AIS position on record with Voydar. It appears on a sanctions list (details below).

Vessel type
Tanker
Flag
—
Year built
2003
Gross tonnage
25,108
Size (length × beam)
176 m × 31 m
Registered owner
—

Watch this ship

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

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.

Photo of IMO 9260055
Photo: Bernhard Fuchs · Licence: CC BY 2.0 · via Wikimedia Commons

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
IMO 9260055
IMO numberWhat is an IMO number?
9260055
Flag
—
Vessel type
Tanker
Gross tonnageGross tonnage vs deadweight
25,108
Length overall
176 m
Beam
31 m
Year built
2003

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
Former name: VardarWikidata
Reported arrival at HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)Authority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)Authority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from PASCAGOULA HARBOR, MSAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Former name: Cape BonWikidata

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
VardarFormer nameJan 1, 2017Wikidata
Cape BonFormer nameJan 1, 2003Wikidata
GRATIAName 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: Wikidata. Licence: CC0 1.0.

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)SDGTGRATIAnot 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
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)ArrivalJul 15, 2016(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)DepartureJul 15, 2016(date only)—USACE foreign traffic vessel entrances & clearances
PASCAGOULA HARBOR, MSDepartureJul 12, 2016(date only)—USACE foreign traffic vessel entrances & clearances
PASCAGOULA HARBOR, MSArrivalJul 10, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPDepartureJun 9, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPArrivalJun 9, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Port Arthur USPOADepartureMay 3, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Port Arthur USPOAArrivalMay 2, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Savannah USSAVDepartureApr 27, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Savannah USSAVArrivalApr 26, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Wilmington USILMDepartureApr 25, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Wilmington USILMArrivalApr 25, 2016(date only)—USACE foreign traffic vessel entrances & clearances

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

Frequently asked questions

Where is IMO 9260055 now?
Voydar has no displayable AIS position for IMO 9260055 in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is IMO 9260055?
IMO 9260055 is a tanker, built in 2003 by HD Hyundai Mipo. The vessel is 176 m long with a beam of 31 m and has a gross tonnage of 25,108.
What sanctions and inspection records does Voydar hold for IMO 9260055?
IMO 9260055 appears on the OFAC SDN list under SDGT. No matched inspection records are displayed for IMO 9260055. 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/9260055
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