Skip to content

CSCL Jupiter

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

IMO9467263MMSI477213400Call signVRIL4Last AIS position Sep 27, 2026, 08:48 UTC

In short

CSCL Jupiter (Container ship, Hong Kong flag) was last seen on AIS on , under way at 13.6 kn, in the East China 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 CNSHA; its reported draught is 11.8 m (voyage report via AISstream.io global terrestrial AIS, received Sep 27, 2026, 00:28 UTC). ISM manager: Shanghai Ocean Shipping Co.,Ltd. (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Vessel type
Container ship
Year built
2011
Gross tonnage
158,000
Size (length × beam)
366 m

Watch this ship

Get an email when CSCL Jupiter arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.

We email you a link and a code. That creates a free account, no password or card, and follows CSCL Jupiter.

Free account, no card: follow up to 5 ships and ports. Plus follows 50, Pro 500.

By continuing you accept the Terms and the Privacy policy.

Photo of CSCL Jupiter
Photo: kees torn · Licence: CC BY-SA 2.0 · via Wikimedia Commons

Last reported position

received
Position
27.1026° N, 121.9348° E
Area
East China Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
13.6 kn
Course
47°
Heading
48°
27.1026° N, 121.9348° E
Open the full live map →

Voydar detected no port call in the last 30 days.

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)

Try the live demo, no sign-up

Identity & particulars

Name
CSCL Jupiter
IMO numberWhat is an IMO number?
9467263
MMSIWhat is an MMSI?
477213400
Call signWhat is a call sign?
VRIL4
Vessel type
Container ship
AIS ship type
Cargo (hazardous cat. D)
Gross tonnageGross tonnage vs deadweight
158,000
Length overall
365.5 m
Beam
—
Year built
2011

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 Sep 28, 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
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
201813,693 t4,388 t28 days1,090 kg
201922,827 t7,322 t63 days842 kg
202073,364 t23,518 t165 days1,081 kg
202186,362 t27,680 t195 days1,296 kg
202276,191 t24,445 t161 days1,168 kg
202334,441 t11,005 t112 days950 kg
202453,401 t17,192 t149 days1,093 kg
202539,645 t12,880 t135 days985 kg

Technical efficiency: EEXI (8.67 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.

Reported by authorities Authority-reported

PortRecordDate (UTC)BerthSource
Hong Kong HKHKGArrivalMar 1, 2023, 09:25 UTCMBHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalAug 21, 2021, 00:52 UTCKC12Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalJun 2, 2021, 21:46 UTCKC14Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalMay 17, 2021, 18:40 UTCKC12Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalMar 1, 2021, 08:53 UTCKC13Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalDec 22, 2020, 14:04 UTCMBHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalOct 31, 2020, 12:33 UTCKC13Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalAug 15, 2020, 10:20 UTCKC13Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalJun 3, 2020, 11:02 UTCKC14Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalMar 21, 2020, 11:29 UTCKC14Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalDec 21, 2019, 14:44 UTCKC13Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalSep 28, 2019, 06:44 UTCWLHong Kong vessel arrivals & departures (incl. VTMS daily reports)

Records published by the authority named on each row. Earliest record for this ship: April 28, 2018.

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

Frequently asked questions

Where is CSCL Jupiter now?
CSCL Jupiter (Container ship, Hong Kong flag) was last seen on AIS on Sep 27, 2026, 08:48 UTC, under way at 13.6 kn, in the East China Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was CNSHA (voyage report via AISstream.io global terrestrial AIS, received Sep 27, 2026, 00:28 UTC). This report does not confirm the ship’s current route.
What kind of ship is CSCL Jupiter?
CSCL Jupiter is a container ship sailing under the flag of Hong Kong, built in 2011 by Samsung Heavy Industries. The vessel is 365.5 m long and has a gross tonnage of 158,000.
Who is recorded as the owner or manager of CSCL Jupiter?
Shanghai Ocean Shipping Co.,Ltd. is recorded as ISM manager for CSCL Jupiter (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 CSCL Jupiter?
Voydar has no matched sanctions record displayed for CSCL Jupiter from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels and the New Zealand Russia Sanctions Register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for CSCL Jupiter. 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/9467263
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