Skip to content

OOCL Seoul

Container ship · Hong Kong · built 2010 · AIS Class A

IMO9417244MMSI477617700Call signVRFU8Last AIS position Oct 6, 2026, 12:05 UTC

In short

OOCL Seoul (Container ship, Hong Kong flag) was last seen on AIS on , moored, in the port of Voltri. Its crew-entered AIS destination is FRFOS (Fos-sur-Mer), with an ETA of Oct 7, 2026, 09:00 UTC; its reported draught is 12.5 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 12:23 UTC). It arrived there on Oct 4, 2026, 13:33 UTC. ISM manager: Orient Overseas Container Line Ltd (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Vessel type
Container ship
Year built
2010
Gross tonnage
89,097
Size (length × beam)
323 m

Watch this ship

Get an email when OOCL Seoul reaches Fos-sur-Mer, 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.

Photo of OOCL SEOUL
Photo: Bruce Tuten from Savannah, Georgia, United States · Licence: CC BY 2.0 · via Wikimedia Commons

Last reported position

received
Position
44.4173° N, 8.7943° E
Area
Mediterranean Sea
Speed
0 kn
Course
197°
Heading
282°
44.4173° N, 8.7943° E
Open the full live map →

Last 30 days: 2 port calls (Voltri and Algeciras).

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
OOCL Seoul
IMO numberWhat is an IMO number?
9417244
MMSIWhat is an MMSI?
477617700
Call signWhat is a call sign?
VRFU8
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
89,097
Length overall
323 m
Beam
—
Year built
2010

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

DateEventSource
Arrived at VoltriAIS-detectedVoydar port-call detector (AIS geofence)
Call sign changed from VRFU8 to DATAHUBAIS, seen by Voydar
Left AlgecirasAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at AlgecirasAIS-detectedVoydar port-call detector (AIS geofence)
Inspection at Baltimore, MarylandUSCG PSIX / CGMIX inspections
Port State Control inspection at Portsmouth, VirginiaUSCG PSIX / CGMIX inspections
Port State Control inspection at Portsmouth, VirginiaUSCG PSIX / CGMIX inspections
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 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 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)
Port State Control inspection at STATEN ISLAND, New YorkUSCG PSIX / CGMIX inspections
Port State Control inspection at Seattle, WashingtonUSCG PSIX / CGMIX inspections
Port State Control inspection at Jacksonville, FloridaUSCG PSIX / CGMIX inspections
Port State Control inspection at Seattle, WashingtonUSCG PSIX / CGMIX inspections
Inspection at Seattle, WashingtonUSCG PSIX / CGMIX inspections
Port State Control inspection at STATEN ISLAND, New YorkUSCG PSIX / CGMIX inspections
Inspection at STATEN ISLAND, New YorkUSCG 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

13
Inspections
not recorded
Detentions
0
Deficiencies
DateTypePortFindings
Sep 8, 2025Vessel InspectionBaltimore, Marylandclean
Jun 25, 2024Vessel InspectionPSCPortsmouth, Virginiaclean
May 21, 2024Vessel InspectionPSCPortsmouth, Virginiaclean
May 19, 2021Vessel InspectionPSCSTATEN ISLAND, New Yorkclean
Jun 1, 2018Vessel InspectionPSCSeattle, Washingtonclean
Oct 12, 2016Vessel InspectionPSCJacksonville, Floridaclean
Oct 13, 2015Vessel InspectionPSCSeattle, Washingtonclean
Feb 24, 2015BoardingSeattle, Washingtonclean
Sep 17, 2014Vessel InspectionPSCSTATEN ISLAND, New Yorkclean
Aug 29, 2013Vessel Operational ControlSTATEN ISLAND, New Yorkclean
Aug 29, 2013Vessel InspectionPSCSTATEN ISLAND, New Yorkclean
Aug 29, 2013Incident InvestigationWASHINGTON, District of Columbiaclean
Aug 27, 2013Vessel InspectionPSCSTATEN ISLAND, New Yorkclean

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.

YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
202128,971 t9,180 t110 days762 kg
202239,764 t12,666 t162 days743 kg
202427,317 t8,675 t97 days850 kg
202524,861 t7,870 t120 days705 kg

Technical efficiency: EEXI (11.1 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
Voltri ITVTIOct 4, 2026, 13:33 UTCin port—
Algeciras ESALGSep 22, 2026, 15:31 UTCSep 23, 2026, 03:20 UTC11 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

PortRecordDate (UTC)BerthSource
Hong Kong HKHKGArrivalDec 22, 2023, 14:47 UTCPOTOI ISLANDHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalDec 8, 2023, 20:24 UTCKCHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalSep 18, 2023, 06:47 UTCMIRS BAY (TAI PANG WAN) WATERSHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalJul 3, 2023, 07:46 UTCKC9Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalApr 17, 2023, 08:28 UTCKC11Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalJan 16, 2023, 05:57 UTCKC13Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalNov 7, 2022, 17:20 UTCKC12Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalMar 17, 2021, 20:41 UTCKC8Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalFeb 19, 2021, 08:47 UTCKC8Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Jan 15, 2021, 03:18 UTCTSKHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalDec 27, 2020, 14:52 UTCKC14Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Nov 23, 2020, 22:03 UTCTSKHong Kong vessel arrivals & departures (incl. VTMS daily reports)

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

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

Frequently asked questions

Where is OOCL Seoul now?
OOCL Seoul (Container ship, Hong Kong flag) was last seen on AIS on Oct 6, 2026, 12:05 UTC, moored, in the port of Voltri. The crew-entered destination was FRFOS (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 12:23 UTC). This report does not confirm the ship’s current route.
What kind of ship is OOCL Seoul?
OOCL Seoul is a container ship sailing under the flag of Hong Kong, built in 2010 by Samsung Heavy Industries. The vessel is 323 m long and has a gross tonnage of 89,097.
Who is recorded as the owner or manager of OOCL Seoul?
Orient Overseas Container Line Ltd is recorded as ISM manager for OOCL Seoul (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 OOCL Seoul?
Voydar has no matched sanctions record displayed for OOCL Seoul 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. OOCL Seoul has 13 recorded Port State Control inspections. Detention and deficiency detail is not recorded for these inspections.

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/9417244
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