Skip to content

OOCL Germany

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

IMO9776183MMSI477035800Call signVRQS3Last AIS position Oct 5, 2026, 07:12 UTC

In short

OOCL Germany (Container ship, Hong Kong flag) was last seen on AIS on , under way at 17.2 kn, near Rodby (Baltic Sea). Its crew-entered AIS destination is BEZEE>>PLGDN, with an ETA of Oct 6, 2026, 01:00 UTC; its reported draught is 14 m (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 07:06 UTC). ISM manager: Orient Overseas Container Line Ltd (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Current voyage: from Zeebrugge (departed Oct 3, 2026, 07:32 UTC) to BEZEE>>PLGDN

Vessel type
Container ship
Year built
2017
Gross tonnage
199,000
Size (length × beam)
400 m

Watch this ship

Get an email when OOCL Germany arrives or 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 GERMANY
Photo: kees torn · Licence: CC BY-SA 2.0 · via Wikimedia Commons

Last reported position

received
Position
54.5035° N, 11.4666° E
Area
Baltic Sea
StatusWhat do AIS statuses mean?
Constrained by her draught
Speed
17.2 kn
Course
114°
Heading
114°
54.5035° N, 11.4666° E
Open the full live map →

Last 30 days: 2 port calls (Zeebrugge and Felixstowe).

Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.

Pro shows OOCL Germany's track before the last 30 days. Voydar has recorded its port calls since June 19, 2026.Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name
OOCL Germany
IMO numberWhat is an IMO number?
9776183
MMSIWhat is an MMSI?
477035800
Call signWhat is a call sign?
VRQS3
AIS ship type
Cargo (hazardous cat. A)
Gross tonnageGross tonnage vs deadweight
199,000
Length overall
400 m
Beam
—
Year built
2017

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
Left ZeebruggeAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at ZeebruggeAIS-detectedVoydar port-call detector (AIS geofence)
Left FelixstoweAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at FelixstoweAIS-detectedVoydar port-call detector (AIS geofence)
Left Nowy Port/GdanskAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Nowy Port/GdanskAIS-detectedVoydar port-call detector (AIS geofence)
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)

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
201881,688 t26,104 t216 days971 kg
201971,848 t22,927 t213 days902 kg
202054,386 t17,382 t161 days914 kg
202144,897 t14,294 t124 days1,054 kg
202236,712 t11,710 t117 days874 kg
202329,347 t9,333 t113 days757 kg
202437,253 t11,892 t119 days852 kg
202549,402 t15,926 t145 days887 kg

Technical efficiency: EEDI (7.81 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
Zeebrugge BEZEEOct 1, 2026, 20:27 UTCOct 3, 2026, 07:32 UTC35 h 6 min
Felixstowe GBFXTSep 25, 2026, 00:53 UTCSep 28, 2026, 02:01 UTC3 d 1 h
Nowy Port/Gdansk PLNOWJun 19, 2026, 01:19 UTCJun 19, 2026, 19:41 UTC18 h 22 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 HKHKGArrivalMay 30, 2020, 19:33 UTCKC9Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalFeb 4, 2020, 06:30 UTCKC14Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Nov 6, 2019, 23:14 UTCWLHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Aug 21, 2019, 00:12 UTCWLHong Kong vessel arrivals & departures (incl. VTMS daily reports)

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

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

About OOCL Germany

OOCL Germany is the second G-class container ship built at the Samsung Heavy Industries shipyard in Geoje. She was completed and christened in August 2017 and entered service for OOCL's Asia-Europe trade lane.

Summary from Wikipedia, licensed CC BY-SA.

Frequently asked questions

Where is OOCL Germany now?
OOCL Germany (Container ship, Hong Kong flag) was last seen on AIS on Oct 5, 2026, 07:12 UTC, under way at 17.2 kn, near Rodby (Baltic Sea). The crew-entered destination was BEZEE>>PLGDN (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 07:06 UTC). This report does not confirm the ship’s current route.
What kind of ship is OOCL Germany?
OOCL Germany is a container ship sailing under the flag of Hong Kong, built in 2017 by Samsung Heavy Industries. The vessel is 400 m long and has a gross tonnage of 199,000.
Who is recorded as the owner or manager of OOCL Germany?
Orient Overseas Container Line Ltd is recorded as ISM manager for OOCL Germany (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 Germany?
Voydar has no matched sanctions record displayed for OOCL Germany 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 OOCL Germany. 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/9776183
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