BEIJING
Container ship · Malta · built 2006 · AIS Class A
In short
BEIJING (Container ship, Malta flag) was last seen on AIS on , at anchor, in the East China Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. ISM manager: Capetanissa Maritime Corp (source: EU MRV (THETIS-MRV) emissions, reporting year 2024).
- Vessel type
- Container ship
- Flag
- Malta
- Year built
- 2006
- Gross tonnage
- 109,149
- Size (length × beam)
- 351 m
- ISM manager
- Capetanissa Maritime Corp
Watch this ship
Get an email when BEIJING 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 BEIJING.
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.

Last reported position
received- Position
- 30.2507° N, 123.1484° E
- Area
- East China Sea
- StatusWhat do AIS statuses mean?
- At anchor
- Speed
- 0 kn
- Course
- 79°
- Heading
- 162°
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-upIdentity & particulars
- Name
- BEIJING
- IMO numberWhat is an IMO number?
- 9308508
- MMSIWhat is an MMSI?
- 256937000
- Call signWhat is a call sign?
- 9HA4041
- Flag
- Malta
- Vessel type
- Container ship
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 109,149
- Length overall
- 350.6 m
- Beam
- —
- Year built
- 2006
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 year 2024 · 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.
| Date | Event | Source |
|---|---|---|
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong 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.
Incidents & investigations Authority-reported
Accident and incident reports by national investigation boards, and casualty warnings, that concern this ship. Each links to the original.
- Occurred Oct 1, 2021ACC · OtherNTSB marine investigations (CAROL)Huntington Beach, CA, USA
San Pedro Bay Pipeline / MSC Danit / Beijing, Huntington Beach, CA, USA (NTSB DCA22FM001)Report published Jan 25, 2024
The probable cause of the damage to and subsequent crude oil release from the San Pedro Bay Pipeline was the proximity of established anchorage positions to the pipeline, which resulted in two containerships’ anchors striking the pipeline when the ships dragged anchor in high winds and seas. Contributing to the crude oil release was the undetected damage to the pipeline, which allowed fatigue crac
Source: NTSB marine investigations (CAROL). Courtesy: National Transportation Safety Board. Licence: US Government work (17 U.S.C. §105), public domain.
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 |
|---|---|---|---|---|
| 2024 | 19,941 t | 6,391 t | 73 days | 777 kg |
Technical efficiency: EEXI (10.9 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
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Hong Kong HKHKG | Arrival | Sep 12, 2026, 11:18 UTC | KWAICHUNG CONTR. BERTH NO. 13 (TERMINAL 8) | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Jun 11, 2026, 15:55 UTC | KC14 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | May 28, 2026, 14:46 UTC | KC14 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | May 1, 2026, 06:19 UTC | KC12 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Jan 27, 2026, 14:51 UTC | KC13 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Nov 5, 2025, 20:28 UTC | KC13 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Jul 29, 2025, 15:41 UTC | KC12 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | May 7, 2025, 07:05 UTC | KC12 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Feb 11, 2025, 17:52 UTC | KC14 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Dec 24, 2024, 09:35 UTC | KC13 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Nov 6, 2024, 16:14 UTC | KC13 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | May 7, 2024, 03:54 UTC | MB | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
Records published by the authority named on each row. Earliest record for this ship: March 2, 2015.
Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.
About BEIJING
COSCO Beijing is a container ship built in 2006, by Hyundai Heavy Industries Co., Ltd. in South Korea. Beijing is owned by Capetanissa Maritime Corp of Greece, and operated by COSCO Container Lines Co Ltd (COSCON).
Summary from Wikipedia, licensed CC BY-SA.
Frequently asked questions
- Where is BEIJING now?
- BEIJING (Container ship, Malta flag) was last seen on AIS on Sep 27, 2026, 01:08 UTC, at anchor, in the East China Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report.
- What kind of ship is BEIJING?
- BEIJING is a container ship sailing under the flag of Malta, built in 2006 by HD Hyundai Heavy Industries. The vessel is 350.6 m long and has a gross tonnage of 109,149.
- Who is recorded as the owner or manager of BEIJING?
- Capetanissa Maritime Corp is recorded as ISM manager for BEIJING (source: EU MRV (THETIS-MRV) emissions; reporting year 2024). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for BEIJING?
- Voydar has no matched sanctions record displayed for BEIJING 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 BEIJING. 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/9308508Using 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.