Skip to content

Ocean Crown

Bulk carrier · built 2005

IMO9317107No AIS position on record

In short

Ocean Crown (Bulk carrier) has no AIS position on record with Voydar. ISM manager: Global Carriers Ltd. (source: EU MRV (THETIS-MRV) emissions, reporting year 2024).

Vessel type
Bulk carrier
Flag
—
Year built
2005
Gross tonnage
30,057
Size (length × beam)
190 m

Watch this ship

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

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 Ocean Crown
Photo: Alfvanbeem · 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)

Try the live demo, no sign-up

Identity & particulars

Name
Ocean Crown
IMO numberWhat is an IMO number?
9317107
Flag
—
Gross tonnageGross tonnage vs deadweight
30,057
Length overall
190 m
Beam
—
Year built
2005

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 year 2024 · reported · confidence 0.9 · retrieved Sep 28, 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
Reported departure from StocktonAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at OTHER SAN FRANCISCO BAY AREA PORTS, CA (NET)Authority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from OaklandAuthority-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
20181,483 t474 t25 days285 kg
20192,535 t812 t39 days350 kg
20212,169 t688 t28 days294 kg
20227,175 t2,277 t91 days315 kg
20240 t0 t0 days—

Technical efficiency: EEXI (4.32 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
Stockton USSCKDepartureMay 29, 2015(date only)—USACE foreign traffic vessel entrances & clearances
OTHER SAN FRANCISCO BAY AREA PORTS, CA (NET)ArrivalMay 22, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Oakland USOAKDepartureJan 27, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Oakland USOAKArrivalJan 18, 2012(date only)—USACE foreign traffic vessel entrances & clearances
UNALASKA ISLAND, ALASKA (INCLUDING DUTCH & ILIULIUK HARBORS)DepartureSep 14, 2011(date only)—USACE foreign traffic vessel entrances & clearances
UNALASKA ISLAND, ALASKA (INCLUDING DUTCH & ILIULIUK HARBORS)ArrivalSep 14, 2011(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)DepartureJul 22, 2011(date only)—USACE foreign traffic vessel entrances & clearances
New Orleans USMSYArrivalJul 11, 2011(date only)—USACE foreign traffic vessel entrances & clearances
New York USNYCDepartureMar 19, 2010(date only)—USACE foreign traffic vessel entrances & clearances
New York USNYCArrivalMar 15, 2010(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: March 15, 2010.

Frequently asked questions

Where is Ocean Crown now?
Voydar has no displayable AIS position for Ocean Crown in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is Ocean Crown?
Ocean Crown is a bulk carrier, built in 2005 by Tsuneishi Shipbuilding. The vessel is 190 m long and has a gross tonnage of 30,057.
Who is recorded as the owner or manager of Ocean Crown?
Global Carriers Ltd. is recorded as ISM manager for Ocean Crown (source: EU MRV (THETIS-MRV) emissions; reporting year 2024). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for Ocean Crown?
Voydar has no matched sanctions record displayed for Ocean Crown from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels, the New Zealand Russia Sanctions Register and the French national asset-freeze register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for Ocean Crown. 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/9317107
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