Skip to content

AK KARAM

Bulk carrier · Barbados · built 2003 · AIS Class A

IMO9276731MMSI314800000Call sign8PTO2Last AIS position Oct 1, 2026, 21:30 UTC

In short

AK KARAM (Bulk carrier, Barbados flag) was last seen on AIS on , under way at 11 kn, in the Baltic Sea. Its crew-entered AIS destination is DKSKA (Skagen), with an ETA of Oct 2, 2026, 06:00 UTC; its reported draught is 10.2 m (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 21:16 UTC). ISM manager: ZJ Shipping Ltd (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Vessel type
Bulk carrier
Year built
2003
Gross tonnage
17,979
Size (length × beam)
170 m × 27 m
ISM manager
ZJ Shipping Ltd

Watch this ship

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

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
56.0849° N, 11.1584° E
Area
Baltic Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
11 kn
Course
30°
Heading
33°
56.0849° N, 11.1584° 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
AK KARAM
IMO numberWhat is an IMO number?
9276731
MMSIWhat is an MMSI?
314800000
Call signWhat is a call sign?
8PTO2
Vessel type
Bulk carrier
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
17,979
Length overall
170 m
Beam
27 m
Year built
2003

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 Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported arrival at Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported departure from Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported arrival at Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported departure from PORT OF SOUTH LOUISIANA (LA)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
2023960 t304 t16 days123 kg
20243,785 t1,196 t77 days223 kg
20250 t0 t0 days—

Technical efficiency: EEXI (5.65 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
Hong Kong HKHKGArrivalMar 4, 2023, 04:25 UTCCCMHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalJul 16, 2021, 18:36 UTCSELAHong Kong vessel arrivals & departures (incl. VTMS daily reports)
PORT OF SOUTH LOUISIANA (LA)DepartureApr 6, 2015(date only)—USACE foreign traffic vessel entrances & clearances
New Orleans USMSYArrivalMar 18, 2015(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)DepartureOct 15, 2014(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)DepartureOct 3, 2014(date only)—USACE foreign traffic vessel entrances & clearances
New Orleans USMSYArrivalOct 2, 2014(date only)—USACE foreign traffic vessel entrances & clearances
ELIZABETH RIVER (SOUTHERN BRANCH) VADepartureSep 7, 2014(date only)—USACE foreign traffic vessel entrances & clearances
ELIZABETH RIVER (SOUTHERN BRANCH) VAArrivalSep 5, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Longview USLOGDepartureDec 12, 2013(date only)—USACE foreign traffic vessel entrances & clearances
Longview USLOGArrivalDec 3, 2013(date only)—USACE foreign traffic vessel entrances & clearances
Longview USLOGDepartureAug 19, 2013(date only)—USACE foreign traffic vessel entrances & clearances

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

Behaviour at sea Voydar-derived

Patterns Voydar derived from this ship's AIS broadcasts. They are inferences, not reports: each one shows how it was computed and how confident we are, and none of them says why a ship behaved this way.

WhenWhat we observedConfidence
Sep 26, 2026, 14:40 UTC
Two positions

This MMSI was reported in two places 12 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (60%)

Source: Fintraffic / digitraffic.fi, license CC 4.0 BY. Licence: CC BY 4.0.

Derived from AIS positions of feeds whose terms allow display on Voydar. Coverage is terrestrial: gaps are reported only where our receivers kept hearing other ships. Detections below medium confidence are not shown.

How these are computed →

Frequently asked questions

Where is AK KARAM now?
AK KARAM (Bulk carrier, Barbados flag) was last seen on AIS on Oct 1, 2026, 21:30 UTC, under way at 11 kn, in the Baltic Sea. The crew-entered destination was DKSKA (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 21:16 UTC). This report does not confirm the ship’s current route.
What kind of ship is AK KARAM?
AK KARAM is a bulk carrier sailing under the flag of Barbados, built in 2003 by Shikoku Dockyard. The vessel is 170 m long with a beam of 27 m and has a gross tonnage of 17,979.
Who is recorded as the owner or manager of AK KARAM?
ZJ Shipping Ltd is recorded as ISM manager for AK KARAM (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 AK KARAM?
Voydar has no matched sanctions record displayed for AK KARAM 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 AK KARAM. 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/9276731
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