Skip to content

San

General cargo ship · built 2012

IMO9521851No AIS position on record

In short

San (General cargo ship) has no AIS position on record with Voydar. ISM manager: Bulkship Management AS (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Flag
—
Year built
2012
Gross tonnage
13,579
Size (length × beam)
150 m × 24 m

Watch this ship

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

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
San
IMO numberWhat is an IMO number?
9521851
Flag
—
Gross tonnageGross tonnage vs deadweight
13,579
Length overall
150 m
Beam
23.6 m
Year built
2012

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.

ISM manager
Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–2025 · reported · confidence 0.9 · retrieved Sep 28, 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 PORT OF PLAQUEMINES, LAAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at PORT OF PLAQUEMINES, LAAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from DULUTH-SUPERIOR HARBOR, MN AND WIAuthority-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.

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
20182,887 t922 t78 days206 kg
20195,500 t1,747 t138 days207 kg
20224,871 t1,542 t75 days227 kg
20236,921 t2,185 t143 days182 kg
20249,562 t3,022 t207 days180 kg
20259,077 t2,880 t192 days183 kg

Technical efficiency: EEXI (8.95 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
PORT OF PLAQUEMINES, LADepartureNov 16, 2016(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF PLAQUEMINES, LAArrivalNov 10, 2016(date only)—USACE foreign traffic vessel entrances & clearances
DULUTH-SUPERIOR HARBOR, MN AND WIDepartureAug 9, 2016(date only)—USACE foreign traffic vessel entrances & clearances
DULUTH-SUPERIOR HARBOR, MN AND WIArrivalAug 9, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Baltimore USBALDepartureJul 25, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Baltimore USBALArrivalJul 24, 2016(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)DepartureJun 17, 2016(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)ArrivalJun 14, 2016(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF PLAQUEMINES, LADepartureMar 21, 2016(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF PLAQUEMINES, LADepartureMar 18, 2016(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF PLAQUEMINES, LAArrivalMar 15, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Charleston USCHSDepartureMar 4, 2016(date only)—USACE foreign traffic vessel entrances & clearances

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

Frequently asked questions

Where is San now?
Voydar has no displayable AIS position for San 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?
San is a general cargo ship, built in 2012. The vessel is 150 m long with a beam of 23.6 m and has a gross tonnage of 13,579.
Who is recorded as the owner or manager of San?
Bulkship Management AS is recorded as ISM manager for San (source: EU MRV (THETIS-MRV) emissions; reporting years 2024–2025). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for San?
Voydar has no matched sanctions record displayed for San from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels and the New Zealand Russia Sanctions Register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for San. 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/9521851
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