Skip to content
voydar.com

COSCO JAPAN

Container ship · Singapore · built 2010 · AIS Class A

IMO9448748MMSI563277600Call sign9VMV5Last AIS position Nov 19, 2026, 06:08 UTC

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

Data: AISHub contributors

Vessel type
Container ship
Year built
2010
Gross tonnage
91,051
Size (length × beam)
334 m × 43 m
Photo of COSCO JAPAN
Photo: Wolfgang Fricke · Licence: CC BY 3.0 · via Wikimedia Commons

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°
NArrow: course. Hull: heading. As broadcast on AIS.
36.5987° N, 0.6281° W. Reference map only, not for navigation.
Locator map: Natural Earth (public domain)
36.5987° N, 0.6281° W
See it live in 3D →

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.

Data: AISHub contributors

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

Identity & particulars

Length overall 334 mone tick every 50 m

Beam 42.8 mPlan outline, to scale

Drawn by Voydar from the recorded type, length and beam. The side view is a drawing of the ship type, not of this ship; the length rule and the plan outline's proportions are to scale, the hull shape is not surveyed.
Name
COSCO JAPAN
IMO numberWhat is an IMO number?
9448748
MMSIWhat is an MMSI?
563277600
Call signWhat is a call sign?
9VMV5
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.

DateEventSource
Left ZandvlietAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at ZandvlietAIS-detectedVoydar port-call detector (AIS geofence)
Left WilhelmshavenAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at WilhelmshavenAIS-detectedVoydar port-call detector (AIS geofence)
Left BremerhavenAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at BremerhavenAIS-detectedVoydar port-call detector (AIS geofence)
Port State Control inspection at Houston, TexasUSCG PSIX / CGMIX inspections
Port State Control inspection at STATEN ISLAND, New YorkUSCG PSIX / CGMIX inspections
Reported departure from Los AngelesAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at Los AngelesAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from OaklandAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Port State Control inspection at San Pedro, CaliforniaUSCG PSIX / CGMIX inspections
Inspection at San Pedro, CaliforniaUSCG PSIX / CGMIX inspections
Port State Control inspection at San Pedro, CaliforniaUSCG PSIX / CGMIX inspections
Inspection at JBER, AlaskaUSCG PSIX / CGMIX inspections
Port State Control inspection at San Pedro, CaliforniaUSCG PSIX / CGMIX inspections
Port State Control inspection at San Pedro, CaliforniaUSCG PSIX / CGMIX inspections
Port State Control inspection at San Pedro, CaliforniaUSCG PSIX / CGMIX inspections
Inspection at San Pedro, CaliforniaUSCG 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

12
Inspections
not recorded
Detentions
0
Deficiencies
DateTypePortFindings
Jul 27, 2020Vessel InspectionPSCHouston, Texasclean
Dec 20, 2017Vessel InspectionPSCSTATEN ISLAND, New Yorkclean
Aug 23, 2016Vessel InspectionPSCSan Pedro, Californiaclean
Sep 16, 2015Vessel InspectionSan Pedro, Californiaclean
Jul 30, 2015Vessel InspectionPSCSan Pedro, Californiaclean
Jan 9, 2015Vessel InspectionJBER, Alaskaclean
Jul 3, 2014Vessel InspectionPSCSan Pedro, Californiaclean
Jun 19, 2013Vessel InspectionPSCSan Pedro, Californiaclean
Jun 26, 2012Vessel InspectionPSCSan Pedro, Californiaclean
Jan 20, 2012Vessel InspectionSan Pedro, Californiaclean
Jan 19, 2012Incident InvestigationWASHINGTON, District of Columbiaclean
May 31, 2011Vessel InspectionPSCSan Pedro, Californiaclean

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.

CO₂ emitted per reporting year, tonnes (EU MRV, as reported and verified). The table below has every figure.
YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
20188,255 t2,649 t32 days719 kg
202119,016 t6,000 t72 days892 kg
202228,938 t9,132 t105 days859 kg
202331,209 t9,998 t142 days723 kg
202434,823 t11,164 t137 days780 kg
202525,361 t8,120 t121 days647 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

Time in port over the last 121 days, drawn by Voydar from the AIS-detected calls listed below. Each bar runs from arrival to departure; gaps are time away from a detected port or without reception.
PortArrivedDepartedTime in port
Zandvliet BEZVTNov 13, 2026, 23:02 UTCNov 15, 2026, 01:56 UTC26 h 54 min
Wilhelmshaven DEWVNNov 11, 2026, 05:11 UTCNov 12, 2026, 20:03 UTC38 h 52 min
Bremerhaven DEBRVNov 9, 2026, 02:54 UTCNov 10, 2026, 12:02 UTC33 h 8 min
Harwich GBHRWNov 6, 2026, 06:01 UTCNov 8, 2026, 05:18 UTC47 h 18 min
Ambarli TRAMROct 9, 2026, 01:58 UTCOct 9, 2026, 04:08 UTC2 h 10 min
Piraeus GRPIROct 3, 2026, 03:51 UTCOct 4, 2026, 12:37 UTC32 h 46 min
Zandvliet BEZVTSep 24, 2026, 05:05 UTCSep 25, 2026, 21:31 UTC40 h 26 min
Bremerhaven DEBRVSep 20, 2026, 15:42 UTCSep 22, 2026, 06:26 UTC38 h 44 min
Wilhelmshaven DEWVNSep 19, 2026, 17:50 UTCSep 20, 2026, 12:01 UTC18 h 11 min
Harwich GBHRWSep 16, 2026, 05:21 UTCSep 18, 2026, 21:06 UTC2 d 15 h
Perama GRPERAug 30, 2026, 05:12 UTCAug 31, 2026, 13:48 UTC32 h 36 min
Perama GRPERJul 24, 2026, 00:57 UTCJul 24, 2026, 07:43 UTC6 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

PortRecordDate (UTC)BerthSource
Los Angeles USLAXDepartureDec 31, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXArrivalDec 28, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Oakland USOAKDepartureNov 22, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Oakland USOAKArrivalNov 21, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXDepartureNov 18, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXArrivalNov 16, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Oakland USOAKArrivalOct 10, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Oakland USOAKDepartureOct 10, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXDepartureOct 7, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXArrivalOct 5, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Oakland USOAKDepartureAug 28, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Oakland USOAKArrivalAug 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.

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.

WhenWhat we observedConfidence
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.

How these are computed →

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.

See a sample report (PDF)

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/9448748
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

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

See plans

Sources and attribution

  • Data: AISHub contributors (AISHub Terms of Use (2026-10-08))
  • Wikidata (CC0 1.0)

Each fact above names its source and the date it was retrieved. Each source's licence applies to its data.

Compiled by Voydar from the sources named on this page.

Page: https://www.voydar.com/vessel/9448748-cosco-japan

Generated from voydar.com on Nov 20, 2026, 15:58 UTC