Skip to content

Legacy

Bulk carrier · built 2011

IMO9561992No AIS position on record

In short

Legacy (Bulk carrier) has no AIS position on record with Voydar. ISM manager: Changzhou Dexin Shipping Co. Ltd (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Vessel type
Bulk carrier
Flag
—
Year built
2011
Gross tonnage
32,987
Size (length × beam)
189 m × 32 m

Watch this ship

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

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
Legacy
IMO numberWhat is an IMO number?
9561992
Flag
—
Vessel type
Bulk carrier
Gross tonnageGross tonnage vs deadweight
32,987
Length overall
189 m
Beam
32 m
Year built
2011

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
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 PORT OF SOUTH LOUISIANA (LA)Authority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at PORT OF SOUTH LOUISIANA (LA)Authority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)Authority-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
20180 t0 t0 days—
20191,508 t483 t19 days299 kg
20200 t0 t0 days—
20231,726 t543 t22 days441 kg
20242,472 t792 t30 days288 kg
20250 t0 t0 days—

Technical efficiency: EEXI (4.14 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 SOUTH LOUISIANA (LA)DepartureMar 3, 2015(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)ArrivalFeb 27, 2015(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)DepartureFeb 25, 2015(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)ArrivalFeb 18, 2015(date only)—USACE foreign traffic vessel entrances & clearances
New Orleans USMSYDepartureFeb 15, 2015(date only)—USACE foreign traffic vessel entrances & clearances
New Orleans USMSYArrivalFeb 14, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Savannah USSAVDepartureFeb 9, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Savannah USSAVArrivalFeb 7, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPDepartureFeb 2, 2013(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPArrivalJan 21, 2013(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)DepartureJan 18, 2013(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)ArrivalJan 15, 2013(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: November 19, 2011.

Frequently asked questions

Where is Legacy now?
Voydar has no displayable AIS position for Legacy in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is Legacy?
Legacy is a bulk carrier, built in 2011 by CSC Jinling. The vessel is 189 m long with a beam of 32 m and has a gross tonnage of 32,987.
Who is recorded as the owner or manager of Legacy?
Changzhou Dexin Shipping Co. Ltd is recorded as ISM manager for Legacy (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 Legacy?
Voydar has no matched sanctions record displayed for Legacy 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 Legacy. 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/9561992
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