MSC MARYLENA II
Container ship · Liberia · built 1998 · AIS Class A
In short
MSC MARYLENA II (Container ship, Liberia flag) was last seen on AIS on , not moving, near Gijon (Bay of Biscay). 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 ESGIJ (Gijon), with an ETA of Oct 6, 2026, 03:00 UTC; its reported draught is 10.9 m (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 21:43 UTC). ISM manager: MSC Shipmanagement Ltd (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
Current voyage: from Le Havre (departed Oct 2, 2026, 11:35 UTC) to ESGIJ (Gijon)
- Vessel type
- Container ship
- Flag
- Liberia
- Year built
- 1998
- Gross tonnage
- 25,219
- Size (length × beam)
- 216 m × 27 m
- ISM manager
- MSC Shipmanagement Ltd
Watch this ship
MSC MARYLENA 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.
Free forever. No card. A free account follows up to 5 ships and ports.
Last reported position
received- Position
- 43.5571° N, 5.6887° W
- Area
- Bay of Biscay
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 0.1 kn
- Course
- 152°
- Heading
- 217°
Last 30 days: 2 port calls (Le Havre and Doel).
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-upIdentity & particulars
- Name
- MSC MARYLENA II
- IMO numberWhat is an IMO number?
- 9169031
- MMSIWhat is an MMSI?
- 636023608
- Call signWhat is a call sign?
- 5LON5
- Flag
- Liberia
- Vessel type
- Detailed type from WikidataContainer ship
- AIS ship type
- Cargo (hazardous cat. A)
- Gross tonnageGross tonnage vs deadweight
- 25,219
- Deadweight (DWT)
- Source: Wikidata, record Q83487983. Added to Voydar on September 23, 2026. Licence: CC0 1.0.23,487 t
- Length overall
- 216 m
- Beam
- 26.7 m
- Year built
- 1998
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.
- Operator
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026MSC Shipmanagement(not linked to a company record)Source: Wikidata · reported · confidence 0.6 · retrieved Jun 8, 2026
- ISM manager
- Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–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) | |
| Port State Control inspection at San Pedro, California | USCG PSIX / CGMIX inspections | |
| Reported departure from Long BeachAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at Long BeachAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Inspection at San Pedro, California | USCG PSIX / CGMIX inspections | |
| Inspection at San Pedro, California | USCG PSIX / CGMIX inspections | |
| Inspection at Seattle, Washington | USCG PSIX / CGMIX inspections |
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.
Safety & inspections
| Date | Type | Port | Findings |
|---|---|---|---|
| Nov 18, 2002 | Vessel InspectionPSC | San Pedro, California | clean |
| Feb 8, 2000 | Vessel Inspection | San Pedro, California | clean |
| Jan 7, 2000 | Vessel Inspection | San Pedro, California | clean |
| Dec 12, 1999 | Vessel Inspection | Seattle, Washington | clean |
Source: U.S. Coast Guard Port State Information Exchange (PSIX) — public domain. Covers inspections recorded in U.S. waters. Free on Voydar; the incumbents charge for this.
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 | 25,218 t | 8,089 t | 186 days | 455 kg |
| 2019 | 31,758 t | 10,185 t | 256 days | 401 kg |
| 2020 | 26,296 t | 8,338 t | 234 days | 370 kg |
| 2021 | 27,160 t | 8,614 t | 225 days | 396 kg |
| 2022 | 16,463 t | 5,219 t | 136 days | 472 kg |
| 2023 | 27,724 t | 8,790 t | 223 days | 443 kg |
| 2024 | 17,618 t | 5,634 t | 197 days | 417 kg |
| 2025 | 21,655 t | 6,817 t | 206 days | 437 kg |
Technical efficiency: EEXI (18.29 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 1, 2026, 19:02 UTC | Oct 2, 2026, 11:35 UTC | 16 h 34 min |
| Doel BEDEL | Sep 27, 2026, 02:34 UTC | Sep 28, 2026, 13:22 UTC | 34 h 48 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 |
|---|---|---|---|---|
| Long Beach USLGB | Departure | Nov 18, 2002(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Arrival | Nov 17, 2002(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: November 17, 2002.
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 2, 2026, 10:14 UTC | Draught change Reported draught went from 10 m to 10.9 m while in port at Le Havre. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 28, 2026, 14:15 UTC | Draught change Reported draught went from 9.4 m to 10 m after leaving Doel. Voydar infers the ship probably loaded 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.
Frequently asked questions
- Where is MSC MARYLENA II now?
- MSC MARYLENA II (Container ship, Liberia flag) was last seen on AIS on Oct 6, 2026, 03:40 UTC, not moving, near Gijon (Bay of Biscay). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was ESGIJ (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 21:43 UTC). This report does not confirm the ship’s current route.
- What kind of ship is MSC MARYLENA II?
- MSC MARYLENA II is a container ship sailing under the flag of Liberia, built in 1998 by Howaldtswerke-Deutsche Werft. The vessel is 216 m long with a beam of 26.7 m and has a gross tonnage of 25,219.
- Who is recorded as the owner or manager of MSC MARYLENA II?
- MSC Shipmanagement Ltd is recorded as ISM manager for MSC MARYLENA II (source: EU MRV (THETIS-MRV) emissions; reporting years 2024–2025). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for MSC MARYLENA II?
- Voydar has no matched sanctions record displayed for MSC MARYLENA 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. MSC MARYLENA II has 4 recorded Port State Control inspections. Detention and deficiency detail is not recorded for these inspections.
Sister ships
Likely sister ships: built by Howaldtswerke-Deutsche Werft, same type, gross tonnage within 2.5% and length within 1.5% of this ship's.
- MSC ADRIANA IIIMO 9169055Container ship · built 1998 · 25,219 GT
- MSC CAITLIN IIIMO 9169043Container ship · built 1998 · 25,219 GT
- MSC EDITH IIIMO 9169029Container ship · built 1998 · 25,219 GT
- MSC MIA SUMMER IIIMO 9169067Container ship · built 1999 · 25,219 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/9169031Using 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.