Skip to content

Ym Ideals

Cargo ship · Taiwan · built 2006 · AIS Class A

IMO9319129MMSI416488000Call signBLHFLast AIS position Oct 1, 2026, 19:41 UTC

In short

Ym Ideals (Cargo ship, Taiwan flag) was last seen on AIS on , moored, in the port of Keelung (Chilung). Its crew-entered AIS destination is CN LYG > TW KEL, with an ETA of Oct 1, 2026, 10:00 UTC; its reported draught is 9.7 m (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 19:25 UTC). It arrived there on Oct 1, 2026, 10:29 UTC.

Vessel type
Cargo ship
Flag
Taiwan
Year built
2006
Gross tonnage
16,488
Size (length × beam)
173 m × 27 m
Registered owner
—

Watch this ship

Get an email when Ym Ideals 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 Ym Ideals.

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
25.1478° N, 121.7518° E
Area
East China Sea
Speed
0 kn
Course
327°
Heading
242°
25.1478° N, 121.7518° E
Open the full live map →

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

Port calls are detected by Seadar 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
Ym Ideals
IMO numberWhat is an IMO number?
9319129
MMSIWhat is an MMSI?
416488000
Flag
Taiwan
Vessel type
Cargo ship
AIS ship type
Cargo (hazardous cat. D)
Gross tonnageGross tonnage vs deadweight
16,488
Length overall
172.7 m
Beam
27.3 m
Year built
2006

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 Seadar holds, newest first. Each line names its source; derived items say how they were derived.

DateEventSource
Arrived at Keelung (Chilung)AIS-detectedSeadar port-call detector (AIS geofence)
Reported departure from Los AngelesAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at Los AngelesAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at OaklandAuthority-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 Seadar 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 1, 2026, 10:29 UTCin port—

Detected by Seadar 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
Los Angeles USLAXDepartureJun 26, 2008(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXArrivalJun 19, 2008(date only)—USACE foreign traffic vessel entrances & clearances
Oakland USOAKArrivalJun 18, 2008(date only)—USACE foreign traffic vessel entrances & clearances
Oakland USOAKDepartureJun 17, 2008(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXDepartureMay 14, 2008(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXArrivalMay 14, 2008(date only)—USACE foreign traffic vessel entrances & clearances
Oakland USOAKDepartureMay 12, 2008(date only)—USACE foreign traffic vessel entrances & clearances
Oakland USOAKArrivalMay 12, 2008(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXDepartureApr 9, 2008(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXArrivalApr 9, 2008(date only)—USACE foreign traffic vessel entrances & clearances
Oakland USOAKDepartureApr 7, 2008(date only)—USACE foreign traffic vessel entrances & clearances
Oakland USOAKArrivalApr 7, 2008(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: April 19, 2006.

Frequently asked questions

Where is Ym Ideals now?
Ym Ideals (Cargo ship, Taiwan flag) was last seen on AIS on Oct 1, 2026, 19:41 UTC, moored, in the port of Keelung (Chilung). The crew-entered destination was CN LYG > TW KEL (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 19:25 UTC). This report does not confirm the ship’s current route.
What kind of ship is Ym Ideals?
Ym Ideals is a cargo ship sailing under the flag of Taiwan, built in 2006. The vessel is 172.7 m long with a beam of 27.3 m and has a gross tonnage of 16,488.
What sanctions and inspection records does Seadar hold for Ym Ideals?
Seadar has no matched sanctions record displayed for Ym Ideals 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 Ym Ideals. 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/9319129
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