MSC LUANDA VIII
Container ship · Liberia · built 2006 · AIS Class A
In short
MSC LUANDA VIII (Container ship, Liberia flag) was last seen on AIS on , under way at 11.9 kn, in the Mediterranean Sea. Its crew-entered AIS destination is FOS SUR MER, with an ETA of Oct 4, 2026, 15:30 UTC; its reported draught is 11.9 m (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 07:03 UTC).
Current voyage: from Livorno (departed Oct 3, 2026, 18:24 UTC) to FOS SUR MER
- Vessel type
- Container ship
- Flag
- Liberia
- Year built
- 2006
- Gross tonnage
- 89,941
- Size (length × beam)
- 334 m
- Registered owner
- —
Watch this ship
Get an email when MSC LUANDA VIII 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 MSC LUANDA VIII.
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
- 42.7531° N, 6.3706° E
- Area
- Mediterranean Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 11.9 kn
- Course
- 265°
- Heading
- 263°
Last 30 days: 2 port calls (Livorno and Haifa).
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-upIdentity & particulars
- Name
- MSC LUANDA VIII
- IMO numberWhat is an IMO number?
- 9301471
- MMSIWhat is an MMSI?
- 636024876
- Call signWhat is a call sign?
- 5LUS5
- Flag
- Liberia
- Vessel type
- Detailed type from WikidataContainer ship
- AIS ship type
- Cargo (hazardous cat. D)
- Gross tonnageGross tonnage vs deadweight
- 89,941
- Length overall
- 334 m
- Beam
- —
- Year built
- 2006
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, 2026Source: EU MRV (THETIS-MRV) emissions · reporting year 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.
| Date | Event | Source |
|---|---|---|
| Left LivornoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at LivornoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left HaifaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at HaifaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported departure from Long BeachAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Former name: Csav Valencia | Wikidata | |
| Former name: Hammonia Jork | Wikidata | |
| Former name: MSC Valencia | Wikidata |
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.
Former and other names
Names attested for this ship other than its current name.
| Name | Evidence | Date | Source |
|---|---|---|---|
| Csav Valencia | Former name | Jan 1, 2012 | Wikidata |
| Hammonia Jork | Former name | Jan 1, 2006 | Wikidata |
| MSC Valencia | Former name | Jan 1, 2006 | Wikidata |
A sanctions list's date is the earliest date the list shows the name, not when the ship took it. A name on a list is shown as a former name only where AIS shows the ship using another name after that date; otherwise it is listed as a name the list uses. AIS name changes are dated when Voydar saw them.
Source: Wikidata. Licence: CC0 1.0.
Emissions & fuel consumption
Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.
| Year | CO₂ emitted | Fuel burned | Time at sea | CO₂ / n mile |
|---|---|---|---|---|
| 2018 | 57,142 t | 18,329 t | 138 days | 1,035 kg |
| 2019 | 8,810 t | 2,814 t | 25 days | 1,019 kg |
| 2020 | 26,369 t | 8,467 t | 84 days | 897 kg |
| 2021 | 46,072 t | 14,792 t | 106 days | 1,006 kg |
| 2022 | 4,906 t | 1,576 t | 15 days | 977 kg |
| 2025 | 4,231 t | 1,356 t | 14 days | 782 kg |
Technical efficiency: EEXI (11.14 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
| Port | Arrived | Departed | Time in port |
|---|---|---|---|
| Livorno ITLIV | Oct 1, 2026, 11:00 UTC | Oct 3, 2026, 18:24 UTC | 2 d 7 h |
| Haifa ILHFA | Sep 26, 2026, 07:09 UTC | Sep 26, 2026, 13:13 UTC | 6 h 4 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
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Hong Kong HKHKG | Arrival | May 3, 2019, 21:04 UTC | SELA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Nov 2, 2018, 07:04 UTC | TSK | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Long Beach USLGB | Departure | Dec 13, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Arrival | Dec 10, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Oakland USOAK | Departure | May 12, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Oakland USOAK | Arrival | May 12, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Departure | May 9, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Arrival | May 8, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Oakland USOAK | Departure | Feb 7, 2006(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Oakland USOAK | Departure | Feb 7, 2006(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Oakland USOAK | Arrival | Feb 7, 2006(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Departure | Feb 3, 2006(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: February 2, 2006.
Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
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.
| When | What we observed | Confidence |
|---|---|---|
| Oct 3, 2026, 14:53 UTC | Draught change Reported draught went from 10.7 m to 11.9 m while in port at Livorno. 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.
Frequently asked questions
- Where is MSC LUANDA VIII now?
- MSC LUANDA VIII (Container ship, Liberia flag) was last seen on AIS on Oct 4, 2026, 08:20 UTC, under way at 11.9 kn, in the Mediterranean Sea. The crew-entered destination was FOS SUR MER (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 07:03 UTC). This report does not confirm the ship’s current route.
- What kind of ship is MSC LUANDA VIII?
- MSC LUANDA VIII is a container ship sailing under the flag of Liberia, built in 2006 by HD Hyundai Heavy Industries. The vessel is 334 m long and has a gross tonnage of 89,941.
- What sanctions and inspection records does Voydar hold for MSC LUANDA VIII?
- Voydar has no matched sanctions record displayed for MSC LUANDA VIII 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 LUANDA VIII. 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/9301471Using 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.