Jin Hai Ou
Bulk carrier · built 1997
In short
Jin Hai Ou (Bulk carrier) has no AIS position on record with Seadar.
- Vessel type
- Bulk carrier
- Flag
- —
- Year built
- 1997
- Gross tonnage
- 26,897
- Size (length × beam)
- 190 m × 30 m
- Registered owner
- —
Watch this ship
Get an email when Jin Hai Ou 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 Jin Hai Ou.
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
No AIS position on record for this vessel. Identity and particulars are below.
A year of history in the Terminal (Plus) · the full archive since June 1, 2026 (Pro)
Try the live demo, no sign-upIdentity & particulars
- Name
- Jin Hai Ou
- IMO numberWhat is an IMO number?
- 9125578
- MMSIWhat is an MMSI?
- —
- Call signWhat is a call sign?
- —
- Flag
- —
- Vessel type
- Bulk carrier
- Gross tonnageGross tonnage vs deadweight
- 26,897
- Deadweight (DWT)
- Source: Wikidata, record Q117011763. Added to Seadar on September 23, 2026. Licence: CC0 1.0.43,764 t
- Length overall
- 190 m
- Beam
- 30 m
- Year built
- 1997
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.
- Builder
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
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.
| 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 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 SAN JOAQUIN RIVER, CA (INCLUDING COMMERCE OF PORT OF STOCKTON, CA)Authority-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.
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.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Hong Kong HKHKG | Arrival | Sep 2, 2025, 14:32 UTC | SOUTH WEST LAMMA ANCHORAGE | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Mar 3, 2025, 19:36 UTC | SWLA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| SAN JOAQUIN RIVER, CA (INCLUDING COMMERCE OF PORT OF STOCKTON, CA) | Departure | Apr 6, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| SAN JOAQUIN RIVER, CA (INCLUDING COMMERCE OF PORT OF STOCKTON, CA) | Arrival | Apr 3, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORT OF PLAQUEMINES, LA | Departure | May 14, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORT OF PLAQUEMINES, LA | Arrival | May 3, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Port Arthur USPOA | Departure | Jul 25, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Port Arthur USPOA | Arrival | Jul 24, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Gulfport USGPT | Departure | Jul 20, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Gulfport USGPT | Arrival | Jul 18, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Departure | Apr 19, 2006(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Arrival | Apr 17, 2006(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: February 26, 2002.
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 Jin Hai Ou now?
- Seadar has no displayable AIS position for Jin Hai Ou in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
- What kind of ship is Jin Hai Ou?
- Jin Hai Ou is a bulk carrier, built in 1997 by Hanwha Ocean. The vessel is 190 m long with a beam of 30 m and has a gross tonnage of 26,897.
- What sanctions and inspection records does Seadar hold for Jin Hai Ou?
- Seadar has no matched sanctions record displayed for Jin Hai Ou 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 Jin Hai Ou. 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/9125578Using 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.