Skip to content

Great Jin

Bulk carrier · Hong Kong · built 2010 · AIS Class A

IMO9526679MMSI477726100Call signVRFZ3Last AIS position Oct 1, 2026, 06:29 UTC

In short

Great Jin (Bulk carrier, Hong Kong flag) was last seen on AIS on , under way at 11.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 AU PHE>CN BEI; its reported draught is 17.4 m (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 03:45 UTC).

Vessel type
Bulk carrier
Year built
2010
Gross tonnage
91,751
Size (length × beam)
291 m × 45 m
Registered owner
—

Watch this ship

Get an email when Great Jin 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 Great Jin.

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
26.3645° N, 123.3006° E
Area
East China Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
11.6 kn
Course
21°
Heading
20°
26.3645° N, 123.3006° 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
Great Jin
IMO numberWhat is an IMO number?
9526679
MMSIWhat is an MMSI?
477726100
Call signWhat is a call sign?
VRFZ3
Vessel type
Bulk carrier
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
91,751
Length overall
291 m
Beam
45 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.

No owner, operator or manager is recorded for this vessel yet.

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

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 31, 2026, 11:02 UTCSELAHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalMar 14, 2019, 14:20 UTCSELAHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Baltimore USBALDepartureMar 9, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Baltimore USBALArrivalMar 8, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Baltimore USBALDepartureSep 30, 2011(date only)—USACE foreign traffic vessel entrances & clearances
Baltimore USBALDepartureSep 28, 2011(date only)—USACE foreign traffic vessel entrances & clearances
Baltimore USBALDepartureSep 27, 2011(date only)—USACE foreign traffic vessel entrances & clearances
Baltimore USBALArrivalSep 8, 2011(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: September 8, 2011.

Frequently asked questions

Where is Great Jin now?
Great Jin (Bulk carrier, Hong Kong flag) was last seen on AIS on Oct 1, 2026, 06:29 UTC, under way at 11.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 AU PHE>CN BEI (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 03:45 UTC). This report does not confirm the ship’s current route.
What kind of ship is Great Jin?
Great Jin is a bulk carrier sailing under the flag of Hong Kong, built in 2010. The vessel is 291 m long with a beam of 45 m and has a gross tonnage of 91,751.
What sanctions and inspection records does Voydar hold for Great Jin?
Voydar has no matched sanctions record displayed for Great Jin 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. No matched inspection records are displayed for Great Jin. 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/9526679
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