Skip to content

MU DAN YUAN

Tanker · China · AIS Class A

IMO9955404MMSI413623710Call signBPEF2Last AIS position Oct 6, 2026, 11:10 UTC

In short

MU DAN YUAN (Tanker, China flag) was last seen on AIS on , at anchor, near Hong Kong (South China Sea). Its crew-entered AIS destination is TH RYG, with an ETA of Oct 11, 2026, 16:00 UTC; its reported draught is 4.5 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 15:25 UTC).

Vessel type
Tanker
Flag
China
Year built
—
Gross tonnage
—
Size (length × beam)
—
Registered owner
—

Watch this ship

Get an email when MU DAN 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
22.1602° N, 114.1478° E
Area
South China Sea
Speed
0.2 kn
Course
179°
Heading
53°
22.1602° N, 114.1478° 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)Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name
MU DAN YUAN
IMO numberWhat is an IMO number?
9955404
MMSIWhat is an MMSI?
413623710
Call signWhat is a call sign?
BPEF2
Flag
China
Vessel type
Tanker
Length overall
—
Beam
—
Year built
—

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 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 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)

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 HKHKGArrivalOct 6, 2026, 10:32 UTCSOUTH LAMMA DG ANCHORAGEHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Sep 10, 2026, 05:19 UTCSOUTH LAMMA DG ANCHORAGEHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalJul 27, 2026, 23:41 UTCSOUTH LAMMA DG ANCHORAGEHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalMay 25, 2026, 14:00 UTCSOUTH LAMMA DG ANCHORAGEHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Apr 5, 2026, 02:34 UTCSLAHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalFeb 28, 2026, 17:55 UTCSLAHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Nov 21, 2024, 09:31 UTCPTHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Sep 29, 2024, 09:46 UTCPTHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Mar 30, 2024, 10:30 UTCPTHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Jul 21, 2023, 08:41 UTCPTHong Kong vessel arrivals & departures (incl. VTMS daily reports)

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

Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.

Frequently asked questions

Where is MU DAN YUAN now?
MU DAN YUAN (Tanker, China flag) was last seen on AIS on Oct 6, 2026, 11:10 UTC, at anchor, near Hong Kong (South China Sea). The crew-entered destination was TH RYG (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 15:25 UTC). This report does not confirm the ship’s current route.
What kind of ship is MU DAN YUAN?
MU DAN YUAN is a tanker sailing under the flag of China.
What sanctions and inspection records does Voydar hold for MU DAN YUAN?
Voydar has no matched sanctions record displayed for MU DAN 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 MU DAN 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/9955404
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