Jin Yuan
Bulk carrier · Hong Kong · built 2007 · AIS Class A
In short
Jin Yuan (Bulk carrier, Hong Kong flag) was last seen on AIS on , under way at 11.4 kn, in the South Atlantic Ocean. Its crew-entered AIS destination is LUANDA, with an ETA of Oct 11, 2026, 17:00 UTC; its reported draught is 11.9 m (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 07:06 UTC). ISM manager: Goldbeam International Ltd. (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
- Vessel type
- Bulk carrier
- Flag
- Hong Kong
- Year built
- 2007
- Gross tonnage
- 30,722
- Size (length × beam)
- 190 m × 32 m
- ISM manager
- Goldbeam International Ltd.
Watch this ship
Get an email when Jin Yuan arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
Free forever. No card. A free account follows up to 5 ships and ports.
Last reported position
received- Position
- 34.8119° S, 18.8714° E
- Area
- South Atlantic Ocean
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 11.4 kn
- Course
- 287°
- Heading
- 288°
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)Free forever. No card. New accounts include 14 days of Pro.
Try the live demo, no sign-upIdentity & particulars
- Name
- Jin Yuan
- IMO numberWhat is an IMO number?
- 9380776
- MMSIWhat is an MMSI?
- 477830900
- Call signWhat is a call sign?
- VRCY3
- Flag
- Hong Kong
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 30,722
- Deadweight (DWT)
- Source: Wikidata, record Q85974992. Added to Voydar on September 23, 2026. Licence: CC0 1.0.55,496 t
- Length overall
- 190 m
- Beam
- 32.3 m
- Year built
- 2007
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 Oct 5, 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.
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 | 5,632 t | 1,804 t | 68 days | 306 kg |
| 2025 | 0 t | 0 t | 0 days | — |
Technical efficiency: EEXI (4.2 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 | Apr 10, 2026, 23:42 UTC | SOUTH EAST LAMMA ANCHORAGE | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Oct 26, 2025, 12:02 UTC | SELA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Oct 25, 2023, 13:35 UTC | PT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Aug 24, 2023, 19:28 UTC | SWLA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Mar 8, 2023, 23:50 UTC | PT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Jul 8, 2020, 09:01 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Sep 26, 2019, 12:08 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Dec 7, 2018, 06:21 UTC | PT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Jul 24, 2018, 17:34 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| PORT OF SOUTH LOUISIANA (LA) | Departure | Mar 28, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New Orleans USMSY | Arrival | Mar 21, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Port Arthur USPOA | Departure | Jun 27, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: July 10, 2007.
Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
Frequently asked questions
- Where is Jin Yuan now?
- Jin Yuan (Bulk carrier, Hong Kong flag) was last seen on AIS on Oct 5, 2026, 07:34 UTC, under way at 11.4 kn, in the South Atlantic Ocean. The crew-entered destination was LUANDA (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 07:06 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Jin Yuan?
- Jin Yuan is a bulk carrier sailing under the flag of Hong Kong, built in 2007 by Oshima Shipbuilding. The vessel is 190 m long with a beam of 32.3 m and has a gross tonnage of 30,722.
- Who is recorded as the owner or manager of Jin Yuan?
- Goldbeam International Ltd. is recorded as ISM manager for Jin Yuan (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 Jin Yuan?
- Voydar has no matched sanctions record displayed for Jin Yuan 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 Jin Yuan. 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/9380776Using 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.