LIANG YUAN
Bulk carrier · Panama · built 2010 · AIS Class A
In short
LIANG YUAN (Bulk carrier, Panama flag) was last seen on AIS on , under way at 10.6 kn, in the Baltic Sea. Its crew-entered AIS destination is EG PSD (Port Said), with an ETA of Oct 22, 2026, 15:00 UTC; its reported draught is 14.3 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 11:47 UTC). ISM manager: Anglo-Eastern Ship Management Ltd (source: EU MRV (THETIS-MRV) emissions, reporting year 2024).
- Vessel type
- Bulk carrier
- Flag
- Panama
- Year built
- 2010
- Gross tonnage
- 51,265
- Size (length × beam)
- 229 m × 38 m
- ISM manager
- Anglo-Eastern Ship Management Ltd
Watch this ship
Get an email when LIANG YUAN reaches Port Said, and when it 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
- 54.9715° N, 13.564° E
- Area
- Baltic Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 10.6 kn
- Course
- 254°
- Heading
- 250°
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
- LIANG YUAN
- IMO numberWhat is an IMO number?
- 9587477
- MMSIWhat is an MMSI?
- 352003658
- Call signWhat is a call sign?
- 3E4782
- Flag
- Panama
- Vessel type
- Bulk carrier
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 51,265
- Deadweight (DWT)
- Source: Wikidata, record Q83632346. Added to Voydar on September 23, 2026. Licence: CC0 1.0.93,000 t
- Length overall
- 229 m
- Beam
- 38 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.
- Operator
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026Anglo-Eastern Ship Management(not linked to a company record)Source: Wikidata · reported · confidence 0.6 · retrieved Jun 10, 2026
- ISM manager
- Source: EU MRV (THETIS-MRV) emissions · reporting year 2024 · 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 Newport NewsAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at CHESAPEAKE BAY, MD AND VAAuthority-reported | USACE 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.
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 |
|---|---|---|---|---|
| 2018 | 15,544 t | 4,933 t | 225 days | 408 kg |
| 2019 | 20,653 t | 6,604 t | 272 days | 386 kg |
| 2020 | 8,131 t | 2,570 t | 95 days | 381 kg |
| 2021 | 0 t | 0 t | 0 days | — |
| 2022 | 14,962 t | 4,718 t | 199 days | 341 kg |
| 2023 | 15,023 t | 4,779 t | 190 days | 349 kg |
| 2024 | 3,868 t | 1,227 t | 62 days | 345 kg |
Technical efficiency: EIV (4.36 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 | Mar 20, 2025, 15:53 UTC | SELA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Newport News USNNS | Departure | Dec 19, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| CHESAPEAKE BAY, MD AND VA | Arrival | Dec 1, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Newport News USNNS | Departure | Jul 26, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| CHESAPEAKE BAY, MD AND VA | Arrival | Jul 25, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Mobile USMOB | Departure | Sep 26, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Mobile USMOB | Arrival | Sep 25, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| CHESAPEAKE BAY, MD AND VA | Departure | Jul 5, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| CHESAPEAKE BAY, MD AND VA | Arrival | Jun 30, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Newport News USNNS | Departure | Dec 27, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Newport News USNNS | Arrival | Dec 22, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Mobile USMOB | Departure | Dec 15, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: May 13, 2011.
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 LIANG YUAN now?
- LIANG YUAN (Bulk carrier, Panama flag) was last seen on AIS on Oct 6, 2026, 13:02 UTC, under way at 10.6 kn, in the Baltic Sea. The crew-entered destination was EG PSD (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 11:47 UTC). This report does not confirm the ship’s current route.
- What kind of ship is LIANG YUAN?
- LIANG YUAN is a bulk carrier sailing under the flag of Panama, built in 2010 by Jiangsu Yangzi Xinfu Shipbuilding. The vessel is 229 m long with a beam of 38 m and has a gross tonnage of 51,265.
- Who is recorded as the owner or manager of LIANG YUAN?
- Anglo-Eastern Ship Management Ltd is recorded as ISM manager for LIANG YUAN (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 LIANG YUAN?
- Voydar has no matched sanctions record displayed for LIANG 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 LIANG 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/9587477Using 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.