Skip to content

Arkas

Bulk carrier · Liberia · built 2012 · AIS Class A

IMO9486142MMSI636015367Call signD5AF8Last AIS position Sep 30, 2026, 17:03 UTC

In short

Arkas (Bulk carrier, Liberia flag) was last seen on AIS on , under way at 10.4 kn, in the Indian Ocean. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its crew-entered AIS destination is ZARCB (Richards Bay); its reported draught is 8.1 m (voyage report via AISstream.io global terrestrial AIS, received Sep 30, 2026, 15:44 UTC). ISM manager: AEGEAN BULK CO. INC. (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Current voyage: from Durban (departed Sep 30, 2026, 15:09 UTC) to ZARCB (Richards Bay)

Vessel type
Bulk carrier
Year built
2012
Gross tonnage
34,554
Size (length × beam)
196 m

Watch this ship

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

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
29.5675° S, 31.4222° E
Area
Indian Ocean
StatusWhat do AIS statuses mean?
Under way using engine
Speed
10.4 kn
Course
38°
Heading
39°
29.5675° S, 31.4222° E
Open the full live map →

Last 30 days: 2 port calls (Durban).

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
Arkas
IMO numberWhat is an IMO number?
9486142
MMSIWhat is an MMSI?
636015367
Call signWhat is a call sign?
D5AF8
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
34,554
Length overall
196 m
Beam
—
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
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
Left DurbanAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at DurbanAIS-detectedVoydar port-call detector (AIS geofence)
Left DurbanAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at DurbanAIS-detectedVoydar port-call detector (AIS geofence)
Reported departure from Port ArthurAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at Port ArthurAuthority-reportedUSACE foreign traffic vessel entrances & clearances
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
20240 t0 t0 days—
20250 t0 t0 days—

Technical efficiency: EEXI (4.1 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.

Detected from AIS AIS-detected

PortArrivedDepartedTime in port
Durban ZADURSep 26, 2026, 13:49 UTCSep 30, 2026, 15:09 UTC4 d 1 h
Durban ZADURSep 26, 2026, 00:07 UTCSep 26, 2026, 01:39 UTC1 h 32 min

Detected by Voydar when the ship's AIS positions stayed slow inside a harbour area. Calls shorter than 30 minutes are not shown. Depends on AIS reception; detection started on June 8, 2026.

Reported by authorities Authority-reported

PortRecordDate (UTC)BerthSource
Port Arthur USPOADepartureOct 16, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Port Arthur USPOAArrivalOct 15, 2012(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)DepartureOct 11, 2012(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)ArrivalOct 10, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Charleston USCHSDepartureOct 4, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Charleston USCHSArrivalOct 4, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Morehead City USMRHDepartureOct 2, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Morehead City USMRHArrivalOct 1, 2012(date only)—USACE foreign traffic vessel entrances & clearances

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

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 30, 2026, 14:21 UTC
Draught change

Reported draught went from 7.2 m to 8.1 m while in port at Durban. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)

Source: AISstream.io global terrestrial AIS. AIS data: AISstream.io. Licence: none published.

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 Arkas now?
Arkas (Bulk carrier, Liberia flag) was last seen on AIS on Sep 30, 2026, 17:03 UTC, under way at 10.4 kn, in the Indian Ocean. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was ZARCB (voyage report via AISstream.io global terrestrial AIS, received Sep 30, 2026, 15:44 UTC). This report does not confirm the ship’s current route.
What kind of ship is Arkas?
Arkas is a bulk carrier sailing under the flag of Liberia, built in 2012 by SPP Shipbuilding Co., Ltd.. The vessel is 196 m long and has a gross tonnage of 34,554.
Who is recorded as the owner or manager of Arkas?
AEGEAN BULK CO. INC. is recorded as ISM manager for Arkas (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 Arkas?
Voydar has no matched sanctions record displayed for Arkas 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 Arkas. 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/9486142
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