Skip to content

MSC VULCANO II

Container ship · Liberia · built 2005 · AIS Class A

IMO9313228MMSI636025619Call sign5LYI3Last AIS position Oct 4, 2026, 17:20 UTC

In short

MSC VULCANO II (Container ship, Liberia flag) was last seen on AIS on , under way at 14.3 kn, in the Mediterranean 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 LYKHO (Al Khums), with an ETA of Oct 5, 2026, 13:00 UTC; its reported draught is 8.4 m (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 16:59 UTC). ISM manager: MSC Shipmanagement Ltd (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).

Current voyage: from Gioia Tauro (departed Oct 4, 2026, 10:48 UTC) to LYKHO (Al Khums)

Vessel type
Container ship
Year built
2005
Gross tonnage
16,324
Size (length × beam)
169 m × 27 m

Watch this ship

MSC VULCANO II 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.

We email you a link and a code. That creates a free account, no password or card, and follows MSC VULCANO II.

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.

Photo of MSC VULCANO II
Photo: Ein Dahmer · Licence: CC BY-SA 3.0 · via Wikimedia Commons

Last reported position

received
Position
36.9159° N, 15.5403° E
Area
Mediterranean Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
14.3 kn
Course
192°
Heading
193°
36.9159° N, 15.5403° E
Open the full live map →

Last 30 days: 1 port call (Gioia Tauro).

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
MSC VULCANO II
IMO numberWhat is an IMO number?
9313228
MMSIWhat is an MMSI?
636025619
Call signWhat is a call sign?
5LYI3
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
16,324
Length overall
169 m
Beam
27.2 m
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.

ISM manager
Source: EU MRV (THETIS-MRV) emissions · reporting year 2025 · reported · confidence 0.9 · retrieved Sep 28, 2026
Source: EU MRV (THETIS-MRV) emissions · reporting year 2024 · 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 Gioia TauroAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Gioia TauroAIS-detectedVoydar port-call detector (AIS geofence)
ISM manager: MSC SHIPMANAGEMENT LIMITED (previously Eastaway Ship Management PTE. LTD.)Voydar relationship-change derivation (derived by Voydar from EU MRV (THETIS-MRV) emissions)
Reported departure from SeattleAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at SeattleAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from OaklandAuthority-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
201815,026 t4,759 t189 days312 kg
201917,615 t5,579 t204 days301 kg
202018,240 t5,712 t197 days295 kg
202117,375 t5,486 t168 days315 kg
202216,668 t5,265 t192 days305 kg
202312,949 t4,060 t158 days290 kg
202417,388 t5,531 t181 days334 kg
202512,302 t3,904 t176 days330 kg

Technical efficiency: EEXI (19.9 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
Gioia Tauro ITGITOct 1, 2026, 19:28 UTCOct 4, 2026, 10:48 UTC2 d 15 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
Seattle USSEADepartureApr 8, 2009(date only)—USACE foreign traffic vessel entrances & clearances
Seattle USSEAArrivalApr 8, 2009(date only)—USACE foreign traffic vessel entrances & clearances
Oakland USOAKDepartureApr 5, 2009(date only)—USACE foreign traffic vessel entrances & clearances
Oakland USOAKArrivalApr 5, 2009(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXDepartureApr 3, 2009(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXArrivalApr 3, 2009(date only)—USACE foreign traffic vessel entrances & clearances
Long Beach USLGBDepartureMar 24, 2009(date only)—USACE foreign traffic vessel entrances & clearances
Long Beach USLGBArrivalMar 24, 2009(date only)—USACE foreign traffic vessel entrances & clearances
Seattle USSEADepartureMar 19, 2009(date only)—USACE foreign traffic vessel entrances & clearances
Seattle USSEAArrivalMar 19, 2009(date only)—USACE foreign traffic vessel entrances & clearances
Oakland USOAKDepartureMar 16, 2009(date only)—USACE foreign traffic vessel entrances & clearances
Oakland USOAKArrivalMar 16, 2009(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: August 13, 2005.

Frequently asked questions

Where is MSC VULCANO II now?
MSC VULCANO II (Container ship, Liberia flag) was last seen on AIS on Oct 4, 2026, 17:20 UTC, under way at 14.3 kn, in the Mediterranean 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 LYKHO (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 16:59 UTC). This report does not confirm the ship’s current route.
What kind of ship is MSC VULCANO II?
MSC VULCANO II is a container ship sailing under the flag of Liberia, built in 2005 by Meyer Werft. The vessel is 169 m long with a beam of 27.2 m and has a gross tonnage of 16,324.
Who is recorded as the owner or manager of MSC VULCANO II?
MSC Shipmanagement Ltd is recorded as ISM manager for MSC VULCANO II (source: EU MRV (THETIS-MRV) emissions; reporting year 2025). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for MSC VULCANO II?
Voydar has no matched sanctions record displayed for MSC VULCANO II 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 VULCANO II. 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/9313228
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