MSC PILAR VI
Container ship · Liberia · built 2003 · AIS Class A
In short
MSC PILAR VI (Container ship, Liberia flag) was last seen on AIS on , under way at 1 kn, near Sines (North Atlantic Ocean). Its crew-entered AIS destination is PTSIE (Sines), with an ETA of Oct 6, 2026, 06:00 UTC; its reported draught is 13.6 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 12:43 UTC). ISM manager: MSC Shipmanagement Ltd (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).
Current voyage: from Le Havre (departed Oct 3, 2026, 19:19 UTC) to PTSIE (Sines)
- Vessel type
- Container ship
- Flag
- Liberia
- Year built
- 2003
- Gross tonnage
- 65,918
- Size (length × beam)
- 279 m × 40 m
- ISM manager
- MSC Shipmanagement Ltd
Watch this ship
Get an email when MSC PILAR VI reaches Sines, and when it leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
Free forever. No card. A free account follows up to 5 ships and ports.
Last reported position
received- Position
- 37.9258° N, 8.8386° W
- Area
- North Atlantic Ocean
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 1 kn
- Course
- 340°
- Heading
- 133°
Last 30 days: 3 port calls (Le Havre, Doel, and Europoort).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows MSC PILAR VI's track before the last 30 days. Voydar has recorded its port calls since August 26, 2026.Free forever. No card. New accounts include 14 days of Pro.
Try the live demo, no sign-upIdentity & particulars
- Name
- MSC PILAR VI
- IMO numberWhat is an IMO number?
- 9248148
- MMSIWhat is an MMSI?
- 636023065
- Call signWhat is a call sign?
- 5LLT8
- Flag
- Liberia
- AIS ship type
- Cargo (hazardous cat. A)
- Gross tonnageGross tonnage vs deadweight
- 65,918
- Deadweight (DWT)
- Source: Wikidata, record Q83603453. Added to Voydar on September 23, 2026. Licence: CC0 1.0.67,979 t
- Length overall
- 278.9 m
- Beam
- 40.3 m
- Year built
- 2003
LiberiaA 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 Oct 5, 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 Le HavreAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Le HavreAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left DoelAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at DoelAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left EuropoortAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at EuropoortAIS-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 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) |
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.
| Year | CO₂ emitted | Fuel burned | Time at sea | CO₂ / n mile |
|---|---|---|---|---|
| 2018 | 4,715 t | 1,512 t | 27 days | 567 kg |
| 2025 | 44,052 t | 14,131 t | 202 days | 620 kg |
Technical efficiency: EEXI (11.67 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 |
|---|---|---|---|
| Le Havre FRLEH | Oct 3, 2026, 03:32 UTC | Oct 3, 2026, 19:19 UTC | 15 h 47 min |
| Doel BEDEL | Sep 30, 2026, 03:39 UTC | Oct 2, 2026, 01:19 UTC | 45 h 40 min |
| Europoort NLEUR | Sep 27, 2026, 14:14 UTC | Sep 28, 2026, 22:33 UTC | 32 h 19 min |
| Hamburg DEHAM | Aug 26, 2026, 17:25 UTC | Sep 13, 2026, 03:10 UTC | 17 d 9 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
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Hong Kong HKHKG | Arrival(matched by call sign) | Mar 24, 2023, 03:46 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Mar 8, 2023, 08:03 UTC | PT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Feb 22, 2023, 02:12 UTC | PT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Dec 6, 2022, 19:20 UTC | TSK | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Oct 11, 2022, 18:36 UTC | TSK | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Aug 21, 2022, 09:13 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Jul 16, 2020, 15:00 UTC | SWLA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Oakland USOAK | Departure | Feb 21, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Oakland USOAK | Arrival | Feb 21, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Departure | Feb 17, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Arrival | Feb 17, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Oakland USOAK | Arrival | Nov 13, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: April 5, 2007.
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.
Frequently asked questions
- Where is MSC PILAR VI now?
- MSC PILAR VI (Container ship, Liberia flag) was last seen on AIS on Oct 6, 2026, 13:04 UTC, under way at 1 kn, near Sines (North Atlantic Ocean). The crew-entered destination was PTSIE (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 12:43 UTC). This report does not confirm the ship’s current route.
- What kind of ship is MSC PILAR VI?
- MSC PILAR VI is a container ship sailing under the flag of Liberia, built in 2003 by HJ Shipbuilding & Construction. The vessel is 278.9 m long with a beam of 40.3 m and has a gross tonnage of 65,918.
- Who is recorded as the owner or manager of MSC PILAR VI?
- MSC Shipmanagement Ltd is recorded as ISM manager for MSC PILAR VI (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 PILAR VI?
- Voydar has no matched sanctions record displayed for MSC PILAR VI 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 PILAR VI. Missing records do not establish whether the ship has been detained.
Sister ships
Likely sister ships: built by HJ Shipbuilding & Construction, same type, gross tonnage within 2.5% and length within 1.5% of this ship's.
- Hanjin BeijingIMO 9115731Container ship · built 1996 · 66,654 GT
- MSC Darwin VIIMO 9200689Container ship · built 1999 · 66,278 GT
- MSC Sydney VIIMO 9200677Container ship · built 1999 · 66,278 GT
- BZ CHONGFUIMO 9200691Container ship · built 2000 · 66,278 GT
- ESL MUNDRAIMO 9200706Container ship · built 2000 · 66,278 GT
- Hanjin OttawaIMO 9200718Container ship · built 2000 · 66,278 GT
- Hanjin ViennaIMO 9215634Container ship · built 2000 · 65,918 GT
- Hanjin MadridIMO 9248150Container ship · built 2003 · 65,918 GT
- PANDA 008IMO 9248162Container ship · built 2003 · 65,918 GT
Neighbouring IMO numbers
IMO numbers are issued in sequence. These are the nearest numbers below and above this ship's that have a full Voydar profile.
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/9248148Using 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.