Skip to content
Sanctioned vessel

San Jacinto appears on the EU list of designated vessels, the OFAC SDN list, the UK Sanctions List and the Canadian autonomous sanctions list under Russia (Reg. 833/2014 Annex XLII), IRAN-EO13902, Russia. Verify in the Official Journal (EUR-Lex).

Every vessel on:EU list of designated vesselsOFAC SDN listUK Sanctions ListCanadian autonomous sanctions list

San Jacinto

Oil tanker · built 2002

IMO9247778No AIS position on record

In short

San Jacinto (Oil tanker) has no AIS position on record with Voydar. It appears on 4 sanctions lists (details below).

Vessel type
Oil tanker
Flag
—
Year built
2002
Gross tonnage
28,539
Size (length × beam)
183 m
Registered owner
—

Watch this ship

San Jacinto has not been received for a while. Follow it and we will email you as soon as it is heard again, then when it reaches or leaves port.

Free forever. No card. A free account follows up to 5 ships and ports.

Photo of San Jacinto
Photo: Alf van Beem · Licence: CC0 · 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)Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name
San Jacinto
IMO numberWhat is an IMO number?
9247778
Flag
—
Gross tonnageGross tonnage vs deadweight
28,539
Length overall
182.5 m
Beam
—
Year built
2002

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.

Owner or operator (sanctions listing)
Meuse Shipping Inc(not linked to a company record)
Source: UK Sanctions List (FCDO) · reported · confidence 0.7 · retrieved Oct 4, 2026
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
Listed on the Canadian autonomous sanctions list (Russia)Canada Consolidated Autonomous Sanctions List (SEMA/JVCFOA)
Listed on the UK Sanctions List (Russia)UK Sanctions List (FCDO)
Listed on the EU designated vessels (Official Journal) (Russia (Reg. 833/2014 Annex XLII))EU designated vessels (Reg. 833/2014 Annex XLII; Reg. 2017/1509 Annex XIV)
Reported departure from New YorkAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at New YorkAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from PAULSBORO, NJAuthority-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
BREEZName on a sanctions list—UK Sanctions List (FCDO)
IRISName 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: UK Sanctions List (FCDO). Contains public sector information licensed under the Open Government Licence v3.0. Licence: OGL v3.

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
Canadian autonomous sanctions listRussiaBreezJun 12, 2026In force
UK Sanctions ListRussiaBREEZFeb 24, 2026In force
EU designated vessels (Official Journal)Russia (Reg. 833/2014 Annex XLII)BreezDec 19, 2025In force
OFAC SDN list (US)IRAN-EO13902IRISnot published by the listIn force

Source: Canada Consolidated Autonomous Sanctions List (SEMA/JVCFOA). Contains information licensed under the Open Government Licence – Canada. Licence: Open Government Licence – Canada.

Source: UK Sanctions List (FCDO). Contains public sector information licensed under the Open Government Licence v3.0. Licence: OGL v3.

Source: Council Regulation (EU) No 833/2014, Annex XLII, and Council Regulation (EU) 2017/1509, Annex XIV (Official Journal of the European Union); list compiled by the Danish Maritime Authority. Licence: EU legislation (Official Journal): reuse "for commercial or non-commercial purposes" (Decision 2011/833/EU); facts.

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

Emissions & fuel consumption

Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.

YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
20180 t0 t0 days—
20190 t0 t0 days—

Technical efficiency: EIV (6.03 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.

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
New York USNYCDepartureSep 19, 2016(date only)—USACE foreign traffic vessel entrances & clearances
New York USNYCArrivalSep 15, 2016(date only)—USACE foreign traffic vessel entrances & clearances
PAULSBORO, NJDepartureApr 18, 2016(date only)—USACE foreign traffic vessel entrances & clearances
PAULSBORO, NJArrivalApr 17, 2016(date only)—USACE foreign traffic vessel entrances & clearances
New York USNYCDepartureApr 13, 2016(date only)—USACE foreign traffic vessel entrances & clearances
New York USNYCArrivalMar 30, 2016(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)DepartureJun 19, 2009(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)ArrivalJun 16, 2009(date only)—USACE foreign traffic vessel entrances & clearances
New York USNYCDepartureApr 24, 2007(date only)—USACE foreign traffic vessel entrances & clearances
New York USNYCArrivalApr 24, 2007(date only)—USACE foreign traffic vessel entrances & clearances
PROVIDENCE RIVER AND HARBOR, RIDepartureApr 23, 2007(date only)—USACE foreign traffic vessel entrances & clearances
PROVIDENCE RIVER AND HARBOR, RIArrivalApr 22, 2007(date only)—USACE foreign traffic vessel entrances & clearances

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

Frequently asked questions

Where is San Jacinto now?
Voydar has no displayable AIS position for San Jacinto in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is San Jacinto?
San Jacinto is an oil tanker, built in 2002 by Onomichi Dockyard. The vessel is 182.5 m long and has a gross tonnage of 28,539.
What sanctions and inspection records does Voydar hold for San Jacinto?
San Jacinto appears on the EU list of designated vessels, the OFAC SDN list, the UK Sanctions List and the Canadian autonomous sanctions list under Russia (Reg. 833/2014 Annex XLII), IRAN-EO13902, Russia. No matched inspection records are displayed for San Jacinto. 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/9247778
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