Skip to content

Cape Artemisio

Cargo ship · Malta · built 2017 · AIS Class A

IMO9777175MMSI248140000Call sign9HA4529Last AIS position Oct 1, 2026, 21:33 UTC

In short

Cape Artemisio (Cargo ship, Malta flag) was last seen on AIS on , at anchor, near Itajai (South Atlantic Ocean). Its crew-entered AIS destination is BRNVT (Navegantes), with an ETA of Oct 2, 2026, 21:00 UTC; its reported draught is 9.1 m (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 21:20 UTC).

Current voyage: from Buenos Aires (departed Sep 30, 2026, 18:41 UTC) to BRNVT (Navegantes)

Vessel type
Cargo ship
Flag
Malta
Year built
2017
Gross tonnage
112,836
Size (length × beam)
330 m × 48 m
Registered owner
—

Watch this ship

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

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
26.8575° S, 48.5263° W
Area
South Atlantic Ocean
Speed
0.2 kn
Course
38°
Heading
153°
26.8575° S, 48.5263° W
Open the full live map →

Last 30 days: 1 port call (Buenos Aires).

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 Artemisio
IMO numberWhat is an IMO number?
9777175
MMSIWhat is an MMSI?
248140000
Call signWhat is a call sign?
9HA4529
Flag
Malta
Vessel type
Cargo ship
AIS ship type
Cargo (hazardous cat. A)
Gross tonnageGross tonnage vs deadweight
112,836
Length overall
330 m
Beam
48.3 m
Year built
2017

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
Left Buenos AiresAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Buenos AiresAIS-detectedVoydar port-call detector (AIS geofence)
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 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)

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.

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
Buenos Aires ARBUESep 26, 2026, 19:40 UTCSep 30, 2026, 18:41 UTC3 d 23 h

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
Hong Kong HKHKGArrivalAug 12, 2026, 06:56 UTCKWAICHUNG CONTR. BERTH NO.19 (TERMINAL 9)Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalJul 26, 2026, 14:51 UTCKWAICHUNG CONTR. BERTH NO.17 (TERMINAL 9)Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalMay 6, 2026, 05:02 UTCKC2Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Apr 20, 2026, 22:51 UTCKC5Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalJan 23, 2026, 18:31 UTCKC2Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalSep 30, 2025, 15:03 UTCKC2Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalSep 28, 2025, 13:14 UTCWA2Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalJun 23, 2025, 19:01 UTCKCHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalJun 9, 2025, 10:10 UTCKC5Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalMar 17, 2025, 15:51 UTCKC5Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalDec 14, 2024, 23:41 UTCKC5Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalSep 9, 2024, 21:22 UTCKC5Hong Kong vessel arrivals & departures (incl. VTMS daily reports)

Records published by the authority named on each row. Earliest record for this ship: June 18, 2018.

Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.

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, 20:38 UTC
Draught change

Reported draught went from 9.6 m to 9.1 m after leaving Buenos Aires. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (55%)

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 Cape Artemisio now?
Cape Artemisio (Cargo ship, Malta flag) was last seen on AIS on Oct 1, 2026, 21:33 UTC, at anchor, near Itajai (South Atlantic Ocean). The crew-entered destination was BRNVT (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 21:20 UTC). This report does not confirm the ship’s current route.
What kind of ship is Cape Artemisio?
Cape Artemisio is a cargo ship sailing under the flag of Malta, built in 2017 by HHIC Phil. The vessel is 330 m long with a beam of 48.3 m and has a gross tonnage of 112,836.
What sanctions and inspection records does Voydar hold for Cape Artemisio?
Voydar has no matched sanctions record displayed for Cape Artemisio 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 Cape Artemisio. 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/9777175
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