Skip to content

Yi Peng 3

Bulk carrier · China · built 2001 · AIS Class A

IMO9224984MMSI414270000Call signBPME8Last AIS position Oct 1, 2026, 13:03 UTC

In short

Yi Peng 3 (Bulk carrier, China flag) was last seen on AIS on , under way at 10.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 VLADIVOSTOK,RUSSIA, with an ETA of Oct 5, 2026, 12:00 UTC; its reported draught is 7.8 m (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 05:37 UTC). Registered owner: Ningbo Yipeng Shipping Co., Ltd. (source: Wikidata).

Vessel type
Bulk carrier
Flag
China
Year built
2001
Gross tonnage
40,622
Size (length × beam)
225 m × 32 m

Watch this ship

Get an email when Yi Peng 3 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 Yi Peng 3.

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.5895° N, 121.5253° E
Area
East China Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
10.6 kn
Course
38°
Heading
39°
26.5895° N, 121.5253° 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
Yi Peng 3
IMO numberWhat is an IMO number?
9224984
MMSIWhat is an MMSI?
414270000
Call signWhat is a call sign?
BPME8
Flag
China
Vessel type
Bulk carrier
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
40,622
Net tonnage
24,975
Length overall
225 m
Beam
32.3 m
Year built
2001

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.

Registered owner
Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 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.

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 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 HKHKGArrivalSep 27, 2026, 06:17 UTCSELAHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Aug 19, 2026, 09:43 UTCSOUTH WEST LAMMA ANCHORAGEHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Mar 6, 2026, 14:49 UTCSELAHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalOct 5, 2025, 16:31 UTCSWLAHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Vancouver USVANDepartureApr 1, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Longview USLOGArrivalMar 29, 2016(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)DepartureNov 7, 2014(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF PLAQUEMINES, LAArrivalNov 3, 2014(date only)—USACE foreign traffic vessel entrances & clearances
MATAGORDA SHIP CHANNEL, TX (PORT LAVACA/POINT COMFORT, TX)DepartureOct 27, 2014(date only)—USACE foreign traffic vessel entrances & clearances
MATAGORDA SHIP CHANNEL, TX (PORT LAVACA/POINT COMFORT, TX)ArrivalOct 27, 2014(date only)—USACE foreign traffic vessel entrances & clearances
ELIZABETH RIVER, VADepartureSep 3, 2014(date only)—USACE foreign traffic vessel entrances & clearances
CHESAPEAKE BAY, MD AND VAArrivalAug 21, 2014(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: February 12, 2002.

About Yi Peng 3

On 17–18 November 2024, two submarine telecommunication cables, the BCS East-West Interlink and C-Lion1 fibre-optic cables, were disrupted in the Baltic Sea. The incidents involving both cables occurred in close proximity to each other and near-simultaneously, which prompted accusations from European government officials and NATO member states of hybrid warfare and sabotage as the cause of the damage. Currently, the damage to those undersea cables has not been conclusively attributed to any specific party. Investigations are ongoing and since 19 November, the Chinese cargo ship Yi Peng 3 has been under scrutiny due to its presence near the cables at the time of the incidents. Western intelligence officials believe the ship's anchor may have caused the damage, either accidentally or under the influence of Russian intelligence.

Summary from Wikipedia, licensed CC BY-SA.

Frequently asked questions

Where is Yi Peng 3 now?
Yi Peng 3 (Bulk carrier, China flag) was last seen on AIS on Oct 1, 2026, 13:03 UTC, under way at 10.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 VLADIVOSTOK,RUSSIA (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 05:37 UTC). This report does not confirm the ship’s current route.
What kind of ship is Yi Peng 3?
Yi Peng 3 is a bulk carrier sailing under the flag of China, built in 2001 by HD Hyundai Samho. The vessel is 225 m long with a beam of 32.3 m and has a gross tonnage of 40,622.
Who is recorded as the owner or manager of Yi Peng 3?
Ningbo Yipeng Shipping Co., Ltd. is recorded as Registered owner for Yi Peng 3 (source: Wikidata). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for Yi Peng 3?
Voydar has no matched sanctions record displayed for Yi Peng 3 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 Yi Peng 3. 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/9224984
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