- IMO
- 9448748
- MMSI
- 563277600
- Call Sign
- 9VMV5
Technical Specifications
Key Figures
Live Tracking
Current Position
Where it waited most
Most time stopped at Port of Felixstowe — 36 h across 1 stay.
- 1
- 2Bremerhaven28 h
- 3Wangerooge24 h · 3×
- 4Offshore 54.47,6.942 h
Derived from the AIS track — runs of near-zero speed (anchored, moored or drifting) snapped to the nearest port. Builds up as we observe the vessel.
Resolved from the live AIS destination. Distance is the real sea route (around land and through canals); the computed ETA is at the vessel’s passage speed. A destination is the crew’s stated intent, not a confirmed fixture.
Intelligence
Risk & Sustainability
- AER (CO₂/capacity·nm)
- 7.6
- Fuel burned
- 11,164 t
- Technical
- EEXI (11.12 gCO₂/t·nm)
Verified reported figure. Band is peer-relative, not official IMO CII.
- Bremerhaven1.2 dJun 28, 2026
- Harwich1.5 dJun 24, 2026
AIS-derived from our live feed.
Compliance
Safety Record
- RISK OF GROUNDINGMinorOct 18, 2017Holland Rocks, Prine Rupert, BC, BRITISH COLUMBIA (BC)
On 18 October 2017, the container vessel "COSCO JAPAN", with 23 people on board, reported its anchor dragged due to heavy weather and at a risk of grounding while anchored at Anchorage 9 in Prince Rupert Harbour, BC. A pilot attended the vessel and re-positioned the anchor.
- STRIKING - Allision with a fixed object (striking - includes berthed/docked vessels)SeriousAug 11, 2014Fairview Container Terminal, Prince Rupert, B.C., BRITISH COLUMBIA (BC)
On 11 August 2014, the container vessel "COSCO JAPAN" struck the pier and damaged a fender while berthing in Prince Rupert, B.C.
Recorded marine occurrences naming this vessel.
Operational Status
Activity
Under way but in the slow band — effective capacity voluntarily withdrawn.
Read from the single most-recent AIS broadcast we hold for this hull — we keep no position history, so this is a point-in-time posture, not a dwell inference. Derived in-house from our own AIS feed; weight it by the broadcast age above.
Port calls
1 recent · AIS-detectedArrivals, time in port and the load/discharge inferred from the draught change — detected from AIS track history. An open call means the vessel is still in port (no departure observed yet).
- no cargo change→ · 37 h in port· draught 13.1→13.1 m
Method: each call is a run of fixes inside a port’s geofence confirmed by a stop (or an AIS gap); load/discharge is the sign of the draught delta over the call. Indicative — arrivals before our AIS history began read from the first observation.
Where it waits
1 port · 37 h totalTime-in-port summed by port from the AIS-detected port-call history — the ports this vessel has spent the most time at, longest first.
- Harwich· United Kingdom37 h1 call · 37 h avg
Based on 1 completed call observed since — open calls (no departure yet) are excluded. The distribution sharpens as AIS history accrues.
Composite Risk
Risk Score
Some elevated factors — typically age or a lower-graded flag — but no acute ship-specific flag.
A coverage-weighted blend of the 2 components we could read for this hull — the weights renormalise over only the components present, so a thin read is never inflated and a hull is never credited a “safe 0” for a signal it has no row for. This headline is flagged low-confidence (a thin or structural-only read) and should not be treated as a verdict. Higher means riskier. Derived in-house from government-open port-State-control, flag, sanctions and our own vessel data; weight it by the coverage above.
Estimated
Capacity & Classification
Container · summer draught 14.5 m · 112.4 t per cm immersion
Estimate only — modelled from deadweight (hull geometry) using a first-principles hydrostatic model, not measured hydrostatic tables. The design draught it is anchored to is unreliable across the fleet.
density DWT/GT=1.13 is consistent with declared container
Declared type is consistent with the class implied by the vessel’s size signals. Inferred via our shared size-based classifier.
Commercial
Voyage Estimate

Visual Archive
Gallery
Explore More
Similar Vessels
Community
Vessel Comments