Skip to content

CHIPOLBROK MOON

General cargo ship · Hong Kong · built 2004 · AIS Class A

IMO9272216MMSI477160100Call signVRZT3Last AIS position Sep 25, 2026, 17:53 UTC

In short

CHIPOLBROK MOON (General cargo ship, Hong Kong flag) was last seen on AIS on , under way at 11.4 kn, in the Java Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. ISM manager: Chinese-Polish Joint Stock Shipping Company (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Year built
2004
Gross tonnage
—
Size (length × beam)
200 m

Watch this ship

Get an email when CHIPOLBROK MOON 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 CHIPOLBROK MOON.

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 IMO 9272216
Photo: Wolfgang Fricke · Licence: CC BY 3.0 · via Wikimedia Commons

Last reported position

received
Position
6.2177° S, 105.534° E
Area
Java Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
11.4 kn
Course
66°
Heading
62°
6.2177° S, 105.534° 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
CHIPOLBROK MOON
IMO numberWhat is an IMO number?
9272216
MMSIWhat is an MMSI?
477160100
Call signWhat is a call sign?
VRZT3
AIS ship type
Cargo
Length overall
199.8 m
Beam
—
Year built
2004

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

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 DELAWARE RIVER AT CAMDEN, NJ (INCLUDED IN DELAWARE RIVER, PHILADELPHIA, PA TO THE SEA)Authority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at DELAWARE RIVER AT CAMDEN, NJ (INCLUDED IN DELAWARE RIVER, PHILADELPHIA, PA TO THE SEA)Authority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from New OrleansAuthority-reportedUSACE foreign traffic vessel entrances & clearances

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 May 23, 2018ACC · Cargo, GeneralNTSB marine investigations (CAROL)Houston, TX, USA

    Chipolbrok Moon, Houston, TX, USA (NTSB DCA18FM025)Report published Apr 24, 2019

    The National Transportation Safety Board determines that the probable cause of the fire aboard cargo vessel Chipolbrok Moon was the crew’s lack of adherence to the company’s safety management system and the marine chemist’s instructions pertaining to hotwork precautions, which allowed sparks and slag to fall through unprotected gaps between the removable decking pontoons and ignite the dust-protec

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.

YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
20182,326 t740 t24 days332 kg
20198,569 t2,733 t90 days314 kg
202011,440 t3,656 t134 days294 kg
20210 t0 t0 days—
20225,059 t1,607 t59 days275 kg
20230 t0 t0 days—
20240 t0 t0 days—
20251,548 t501 t21 days228 kg

Technical efficiency: Not Applicable. 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
DELAWARE RIVER AT CAMDEN, NJ (INCLUDED IN DELAWARE RIVER, PHILADELPHIA, PA TO THE SEA)DepartureJan 31, 2015(date only)—USACE foreign traffic vessel entrances & clearances
DELAWARE RIVER AT CAMDEN, NJ (INCLUDED IN DELAWARE RIVER, PHILADELPHIA, PA TO THE SEA)ArrivalJan 31, 2015(date only)—USACE foreign traffic vessel entrances & clearances
New Orleans USMSYDepartureJan 24, 2015(date only)—USACE foreign traffic vessel entrances & clearances
New Orleans USMSYArrivalJan 24, 2015(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)DepartureJan 20, 2015(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)ArrivalJan 10, 2015(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)DepartureAug 4, 2014(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)ArrivalAug 1, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPDepartureJul 29, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPArrivalJul 29, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Philadelphia USPHLDepartureJan 29, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Philadelphia USPHLArrivalJan 29, 2014(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: July 2, 2005.

Frequently asked questions

Where is CHIPOLBROK MOON now?
CHIPOLBROK MOON (General cargo ship, Hong Kong flag) was last seen on AIS on Sep 25, 2026, 17:53 UTC, under way at 11.4 kn, in the Java 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 CHIPOLBROK MOON?
CHIPOLBROK MOON is a general cargo ship sailing under the flag of Hong Kong, built in 2004. The vessel is 199.8 m long.
Who is recorded as the owner or manager of CHIPOLBROK MOON?
Chinese-Polish Joint Stock Shipping Company is recorded as ISM manager for CHIPOLBROK MOON (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 CHIPOLBROK MOON?
Voydar has no matched sanctions record displayed for CHIPOLBROK MOON 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 CHIPOLBROK MOON. 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/9272216
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