Skip to content

Fei Yun He

Container ship · China · built 2000 · AIS Class A

IMO9223760MMSI413333930Call signBOTULast AIS position Oct 6, 2026, 16:28 UTC

In short

Fei Yun He (Container ship, China flag) was last seen on AIS on , under way at 11.5 kn, in the East China Sea. Its last detected port call was at Keelung (Chilung): arrived Oct 3, 2026, left Oct 4, 2026.

Vessel type
Container ship
Flag
China
Year built
2000
Gross tonnage
20,569
Size (length × beam)
179 m × 27 m
Registered owner
—

Watch this ship

Get an email when Fei Yun He 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
25.1586° N, 120.8813° E
Area
East China Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
11.5 kn
Course
33°
Heading
34°
25.1586° N, 120.8813° E
Open the full live map →

Last 30 days: 1 port call (Keelung (Chilung)).

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
Fei Yun He
IMO numberWhat is an IMO number?
9223760
MMSIWhat is an MMSI?
413333930
Flag
China
Vessel type
Container ship
AIS ship type
Cargo (hazardous cat. A)
Gross tonnageGross tonnage vs deadweight
20,569
Length overall
179 m
Beam
27 m
Year built
2000

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
Left Keelung (Chilung)AIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Keelung (Chilung)AIS-detectedVoydar port-call detector (AIS geofence)
Reported departure from CharlestonAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at CharlestonAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from ELIZABETH RIVER, VAAuthority-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.

Detected from AIS AIS-detected

PortArrivedDepartedTime in port
Keelung (Chilung) TWKELOct 3, 2026, 16:53 UTCOct 4, 2026, 04:43 UTC11 h 50 min

Detected by Voydar when the ship's AIS positions stayed slow inside a harbour area. Calls shorter than 30 minutes are not shown. Depends on AIS reception; detection started on June 8, 2026.

Reported by authorities Authority-reported

PortRecordDate (UTC)BerthSource
Charleston USCHSDepartureAug 12, 2007(date only)—USACE foreign traffic vessel entrances & clearances
Charleston USCHSArrivalAug 12, 2007(date only)—USACE foreign traffic vessel entrances & clearances
ELIZABETH RIVER, VADepartureAug 10, 2007(date only)—USACE foreign traffic vessel entrances & clearances
New York USNYCDepartureAug 10, 2007(date only)—USACE foreign traffic vessel entrances & clearances
ELIZABETH RIVER, VAArrivalAug 10, 2007(date only)—USACE foreign traffic vessel entrances & clearances
New York USNYCArrivalAug 9, 2007(date only)—USACE foreign traffic vessel entrances & clearances
Charleston USCHSDepartureJul 16, 2007(date only)—USACE foreign traffic vessel entrances & clearances
Charleston USCHSArrivalJul 16, 2007(date only)—USACE foreign traffic vessel entrances & clearances
ELIZABETH RIVER, VADepartureJul 14, 2007(date only)—USACE foreign traffic vessel entrances & clearances
ELIZABETH RIVER, VAArrivalJul 14, 2007(date only)—USACE foreign traffic vessel entrances & clearances
New York USNYCDepartureJul 13, 2007(date only)—USACE foreign traffic vessel entrances & clearances
New York USNYCArrivalJul 12, 2007(date only)—USACE foreign traffic vessel entrances & clearances

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

Frequently asked questions

Where is Fei Yun He now?
Fei Yun He (Container ship, China flag) was last seen on AIS on Oct 6, 2026, 16:28 UTC, under way at 11.5 kn, in the East China Sea.
What kind of ship is Fei Yun He?
Fei Yun He is a container ship sailing under the flag of China, built in 2000. The vessel is 179 m long with a beam of 27 m and has a gross tonnage of 20,569.
What sanctions and inspection records does Voydar hold for Fei Yun He?
Voydar has no matched sanctions record displayed for Fei Yun He 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 Fei Yun He. 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/9223760
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