COSCO JAPAN
Container ship · Singapore · built 2010 · AIS Class A
In short
COSCO JAPAN (Container ship, Singapore flag) was last seen on AIS on , under way at 15.2 kn, in the Mediterranean Sea. 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 BEANR>GRPIR, with an ETA of Nov 22, 2026, 20:00 UTC; its reported draught is 14.5 m (voyage report via AISstream.io global terrestrial AIS, received Nov 18, 2026, 18:12 UTC). ISM manager: Seaspan Ship Management Ltd. (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
Current voyage: from Zandvliet (departed Nov 15, 2026, 01:56 UTC) to BEANR>GRPIR
- Vessel type
- Container ship
- Flag
- Singapore
- Year built
- 2010
- Gross tonnage
- 91,051
- Size (length × beam)
- 334 m × 43 m
- ISM manager
- Seaspan Ship Management Ltd.

Last reported position: 36.5987° N, 0.6281° W · Mediterranean Sea · See on the map
Watch this ship
COSCO JAPAN has not been received for a while. Follow it for an email update when Voydar receives a new position, and for arrival and departure alerts.
What you would have been told
Nothing in the last 24 hours: no arrival or departure at a port. You are told the moment that changes.
Detected from AIS, as of Nov 20, 2026, 15:58 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for COSCO JAPAN reach you the moment they happen, arrival-time changes included. When it ends you stay on Free, with a daily email, unless you keep Plus (US$7 a month). Compare plans
Get alerts on your phone: the Voydar app
Last reported position
received- Position
- 36.5987° N, 0.6281° W
- Area
- Mediterranean Sea
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 15.2 kn
- Course
- 72°
- Heading
- 72°
- Compass: course over ground 72°, heading 72°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 4 port calls (Zandvliet, Wilhelmshaven, Bremerhaven, and Harwich).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows COSCO JAPAN's track before the last 30 days. Voydar has recorded its port calls since July 24, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
Length overall 334 mone tick every 50 m
Beam 42.8 mPlan outline, to scale
- Name
- COSCO JAPAN
- IMO numberWhat is an IMO number?
- 9448748
- MMSIWhat is an MMSI?
- 563277600
- Call signWhat is a call sign?
- 9VMV5
- Flag
- Singapore
- Vessel type
- Detailed type from WikidataContainer ship
- AIS ship type
- Cargo (hazardous cat. D)
- Gross tonnageGross tonnage vs deadweight
- 91,051
- Length overall
- 334 m
- Beam
- 42.8 m
- 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.
- Operator
- Source: Wikidata · reported · high confidence · retrieved Nov 15, 2026
- ISM manager
- Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–2025 · reported · high confidence · retrieved Nov 16, 2026
- Builder
- Source: Wikidata · reported · high confidence · retrieved Nov 15, 2026
Checking ownership or sanctions for your business? Teams screen fleets by IMO, keep watch with alerts and keep a dated record. Voydar for business →
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 ZandvlietAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at ZandvlietAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left WilhelmshavenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at WilhelmshavenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left BremerhavenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at BremerhavenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Port State Control inspection at Houston, Texas | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at STATEN ISLAND, New York | USCG PSIX / CGMIX inspections | |
| Reported departure from Los AngelesAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at Los AngelesAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from OaklandAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Port State Control inspection at San Pedro, California | USCG PSIX / CGMIX inspections | |
| Inspection at San Pedro, California | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at San Pedro, California | USCG PSIX / CGMIX inspections | |
| Inspection at JBER, Alaska | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at San Pedro, California | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at San Pedro, California | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at San Pedro, California | USCG PSIX / CGMIX inspections | |
| Inspection at San Pedro, California | 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 |
|---|---|---|---|
| Jul 27, 2020 | Vessel InspectionPSC | Houston, Texas | clean |
| Dec 20, 2017 | Vessel InspectionPSC | STATEN ISLAND, New York | clean |
| Aug 23, 2016 | Vessel InspectionPSC | San Pedro, California | clean |
| Sep 16, 2015 | Vessel Inspection | San Pedro, California | clean |
| Jul 30, 2015 | Vessel InspectionPSC | San Pedro, California | clean |
| Jan 9, 2015 | Vessel Inspection | JBER, Alaska | clean |
| Jul 3, 2014 | Vessel InspectionPSC | San Pedro, California | clean |
| Jun 19, 2013 | Vessel InspectionPSC | San Pedro, California | clean |
| Jun 26, 2012 | Vessel InspectionPSC | San Pedro, California | clean |
| Jan 20, 2012 | Vessel Inspection | San Pedro, California | clean |
| Jan 19, 2012 | Incident Investigation | WASHINGTON, District of Columbia | clean |
| May 31, 2011 | Vessel InspectionPSC | San Pedro, California | 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 | 8,255 t | 2,649 t | 32 days | 719 kg |
| 2021 | 19,016 t | 6,000 t | 72 days | 892 kg |
| 2022 | 28,938 t | 9,132 t | 105 days | 859 kg |
| 2023 | 31,209 t | 9,998 t | 142 days | 723 kg |
| 2024 | 34,823 t | 11,164 t | 137 days | 780 kg |
| 2025 | 25,361 t | 8,120 t | 121 days | 647 kg |
Technical efficiency: EEXI (11.12 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.
Compared with ships of its type
Where this ship’s reported CO₂ intensity for 2025 sits among the ships EU MRV lists as “Container ship”. Lower is less CO₂.
- CO₂ per tonne of cargo carried one nautical mile10.42 g per tonne-nautical mile
- Lowest reportedHighest reported
28% of the 2,233 ships in this group reported a lower figure.
Group: lower quartile 9.85 · median 16.45 · upper quartile 29.35
- CO₂ per nautical mile sailed646.7 kg per nautical mile
- Lowest reportedHighest reported
61% of the 2,256 ships in this group reported a lower figure.
Group: lower quartile 313.5 · median 541.9 · upper quartile 768.9
Calculated by Voydar from the figures ships report under EU MRV. This is not a rating and not the IMO Carbon Intensity Indicator (CII). EU MRV covers ships over 5,000 gross tonnage on voyages to, from and within the EU/EEA, so the group is those ships, not the world fleet. How this is calculated
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 |
|---|---|---|---|
| Zandvliet BEZVT | Nov 13, 2026, 23:02 UTC | Nov 15, 2026, 01:56 UTC | 26 h 54 min |
| Wilhelmshaven DEWVN | Nov 11, 2026, 05:11 UTC | Nov 12, 2026, 20:03 UTC | 38 h 52 min |
| Bremerhaven DEBRV | Nov 9, 2026, 02:54 UTC | Nov 10, 2026, 12:02 UTC | 33 h 8 min |
| Harwich GBHRW | Nov 6, 2026, 06:01 UTC | Nov 8, 2026, 05:18 UTC | 47 h 18 min |
| Ambarli TRAMR | Oct 9, 2026, 01:58 UTC | Oct 9, 2026, 04:08 UTC | 2 h 10 min |
| Piraeus GRPIR | Oct 3, 2026, 03:51 UTC | Oct 4, 2026, 12:37 UTC | 32 h 46 min |
| Zandvliet BEZVT | Sep 24, 2026, 05:05 UTC | Sep 25, 2026, 21:31 UTC | 40 h 26 min |
| Bremerhaven DEBRV | Sep 20, 2026, 15:42 UTC | Sep 22, 2026, 06:26 UTC | 38 h 44 min |
| Wilhelmshaven DEWVN | Sep 19, 2026, 17:50 UTC | Sep 20, 2026, 12:01 UTC | 18 h 11 min |
| Harwich GBHRW | Sep 16, 2026, 05:21 UTC | Sep 18, 2026, 21:06 UTC | 2 d 15 h |
| Perama GRPER | Aug 30, 2026, 05:12 UTC | Aug 31, 2026, 13:48 UTC | 32 h 36 min |
| Perama GRPER | Jul 24, 2026, 00:57 UTC | Jul 24, 2026, 07:43 UTC | 6 h 46 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 |
|---|---|---|---|---|
| Los Angeles USLAX | Departure | Dec 31, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Arrival | Dec 28, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Oakland USOAK | Departure | Nov 22, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Oakland USOAK | Arrival | Nov 21, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Departure | Nov 18, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Arrival | Nov 16, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Oakland USOAK | Arrival | Oct 10, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Oakland USOAK | Departure | Oct 10, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Departure | Oct 7, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Arrival | Oct 5, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Oakland USOAK | Departure | Aug 28, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Oakland USOAK | Arrival | Aug 27, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: May 30, 2011.
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 |
|---|---|---|
| Nov 15, 2026, 01:20 UTC | Draught change Reported draught went from 13.4 m to 14.5 m while in port at Zandvliet. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 12, 2026, 18:48 UTC | Draught change Reported draught went from 12.1 m to 13.4 m while in port at Wilhelmshaven. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 4, 2026, 12:36 UTC | Draught change Reported draught went from 13.7 m to 12.3 m while in port at Piraeus. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 25, 2026, 19:48 UTC | Draught change Reported draught went from 13.1 m to 13.9 m while in port at Zandvliet. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 23, 2026, 01:23 UTC | Loitering Stayed within 9.9 km for 12 h 22 min (circling), 51 km from the nearest port and outside known anchorages. Method seadar.behaviour.loitering v1 | Medium (65%) |
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
- What kind of ship is COSCO JAPAN?
- COSCO JAPAN is a container ship sailing under the flag of Singapore, built in 2010 by HD Hyundai Heavy Industries. The vessel is 334 m long with a beam of 42.8 m and has a gross tonnage of 91,051.
- Who is recorded as the owner or manager of COSCO JAPAN?
- Seaspan Ship Management Ltd. is recorded as ISM manager for COSCO JAPAN (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 COSCO JAPAN?
- Voydar has no matched sanctions record displayed for COSCO JAPAN 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. COSCO JAPAN has 12 recorded Port State Control inspections. Detention and deficiency detail is not recorded for these inspections.
Full Vessel Report
A dated PDF with the complete track since June 2026, every port call, ownership and flag changes, inspections, a sanctions and dark-activity screening snapshot, emissions, companies and every source.
Sample: a real report for EVER GIVEN (IMO 9811000), built from public data and marked SAMPLE on every page.
Every fact on this page stays free.
Know this ship?
Help other readers. Member posts are shown as member content, never as sourced data.
- Date, place and an optional note
- Members who know her can answer
- Suggest a correctionChecked against sources before anything changes
More Container ships
Other container ships with full Voydar profiles. A different set each day. All container ships
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/9448748Cite this page
COSCO JAPAN. Voydar (voydar.com). https://www.voydar.com/vessel/9448748-cosco-japan. Retrieved November 20, 2026.
Each fact above names its own source and date. Cite that primary source too when you rely on a fact.
Using this data in code?
Every account gets a personal API allowance: 2,500 credits a month free, 25,000 with Pro. Pro includes use in your own product. Growth and Scale add volume, and each includes one Pro membership.