Skip to content

MSC VAIGA III

Cargo ship · Liberia · built 2005 · AIS Class A

IMO9315836MMSI636021031Call sign5LBX4Last AIS position Oct 4, 2026, 16:01 UTC

In short

MSC VAIGA III (Cargo ship, Liberia flag) was last seen on AIS on , under way at 13.8 kn, in the Java Sea. 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 IDSUB (Surabaya), with an ETA of Oct 4, 2026, 23:00 UTC; its reported draught is 7.9 m (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 15:21 UTC).

Vessel type
Cargo ship
Year built
2005
Gross tonnage
28,927
Size (length × beam)
222 m
Registered owner
—

Watch this ship

MSC VAIGA III has not been received for a while. Follow it and we will email you as soon as it is heard again, then when it reaches or leaves port.

Free forever. No card. A free account follows up to 5 ships and ports.

Photo of MSC VAIGA III
Photo: Alf van Beem · Licence: CC0 · via Wikimedia Commons

Last reported position

received
Position
6.7377° S, 112.7319° E
Area
Java Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
13.8 kn
Course
158°
Heading
157°
6.7377° S, 112.7319° 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)Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name
MSC VAIGA III
IMO numberWhat is an IMO number?
9315836
MMSIWhat is an MMSI?
636021031
Call signWhat is a call sign?
5LBX4
Vessel type
Cargo ship
AIS ship type
Cargo (hazardous cat. A)
Gross tonnageGross tonnage vs deadweight
28,927
Length overall
222.2 m
Beam
—
Year built
2005

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 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 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.

Reported by authorities Authority-reported

PortRecordDate (UTC)BerthSource
Hong Kong HKHKGArrivalAug 14, 2021, 07:59 UTCNLAHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalAug 14, 2021, 07:59 UTCNLAHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Dec 29, 2019, 06:34 UTCTSKHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Dec 17, 2019, 01:36 UTCWLHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Dec 15, 2019, 23:47 UTCMBHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Jun 21, 2019, 23:57 UTCWLHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalJun 3, 2018, 05:20 UTCKC20Hong Kong vessel arrivals & departures (incl. VTMS daily reports)

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

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

Frequently asked questions

Where is MSC VAIGA III now?
MSC VAIGA III (Cargo ship, Liberia flag) was last seen on AIS on Oct 4, 2026, 16:01 UTC, under way at 13.8 kn, in the Java Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was IDSUB (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 15:21 UTC). This report does not confirm the ship’s current route.
What kind of ship is MSC VAIGA III?
MSC VAIGA III is a cargo ship sailing under the flag of Liberia, built in 2005 by HD Hyundai Mipo. The vessel is 222.2 m long and has a gross tonnage of 28,927.
What sanctions and inspection records does Voydar hold for MSC VAIGA III?
Voydar has no matched sanctions record displayed for MSC VAIGA III 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 MSC VAIGA III. 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/9315836
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