Skip to content

CAPE ALIYA

Bulk carrier · Liberia · built 2006 · AIS Class A

IMO9308869MMSI636022587Call sign5LJN4Last AIS position Sep 14, 2026, 13:38 UTC

In short

CAPE ALIYA (Bulk carrier, Liberia flag) was last seen on AIS on , under way at 11.2 kn, in the South Atlantic Ocean. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report.

Vessel type
Bulk carrier
Year built
2006
Gross tonnage
88,930
Size (length × beam)
289 m × 45 m
Registered owner
—

Watch this ship

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

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

received
Position
27.372° S, 14.3486° E
Area
South Atlantic Ocean
StatusWhat do AIS statuses mean?
Under way using engine
Speed
11.2 kn
Course
340°
Heading
336°
27.372° S, 14.3486° E
Open the full live map →

Voydar detected no port call in the last 30 days.

Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls 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
CAPE ALIYA
IMO numberWhat is an IMO number?
9308869
MMSIWhat is an MMSI?
636022587
Call signWhat is a call sign?
5LJN4
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
88,930
Length overall
289 m
Beam
45 m
Year built
2006

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
Reported departure from BaltimoreAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at BaltimoreAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from BaltimoreAuthority-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
20185,115 t1,640 t42 days579 kg
20199,497 t3,044 t78 days532 kg
20227,539 t2,415 t57 days462 kg
20232,372 t761 t18 days550 kg

Technical efficiency: EEXI (2.43 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
Baltimore USBALDepartureDec 7, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Baltimore USBALArrivalOct 27, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Baltimore USBALDepartureJun 13, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Baltimore USBALDepartureJun 11, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Baltimore USBALArrivalJun 6, 2012(date only)—USACE foreign traffic vessel entrances & clearances
ELIZABETH RIVER, VADepartureMar 11, 2012(date only)—USACE foreign traffic vessel entrances & clearances
ELIZABETH RIVER, VAArrivalMar 9, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Baltimore USBALDepartureMar 7, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Baltimore USBALArrivalMar 6, 2012(date only)—USACE foreign traffic vessel entrances & clearances

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

Frequently asked questions

Where is CAPE ALIYA now?
CAPE ALIYA (Bulk carrier, Liberia flag) was last seen on AIS on Sep 14, 2026, 13:38 UTC, under way at 11.2 kn, in the South Atlantic Ocean. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report.
What kind of ship is CAPE ALIYA?
CAPE ALIYA is a bulk carrier sailing under the flag of Liberia, built in 2006 by Shanghai Waigaoqiao Shipbuilding. The vessel is 289 m long with a beam of 45 m and has a gross tonnage of 88,930.
What sanctions and inspection records does Voydar hold for CAPE ALIYA?
Voydar has no matched sanctions record displayed for CAPE ALIYA 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 CAPE ALIYA. 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/9308869
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