Skip to content

Jin Hai Ping

Bulk carrier · China · built 2014 · AIS Class A

IMO9591040MMSI413700260Call signBPAI7Last AIS position Oct 6, 2026, 09:13 UTC

In short

Jin Hai Ping (Bulk carrier, China flag) was last seen on AIS on , under way at 12.4 kn, in the Sea of Japan. Its crew-entered AIS destination is TIAN JIN, with an ETA of Oct 11, 2026, 05:00 UTC; its reported draught is 6.7 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 08:25 UTC).

Vessel type
Bulk carrier
Flag
China
Year built
2014
Gross tonnage
29,476
Size (length × beam)
189 m × 32 m
Registered owner
—

Watch this ship

Get an email when Jin Hai Ping 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
39.7051° N, 139.8437° E
Area
Sea of Japan
StatusWhat do AIS statuses mean?
Under way using engine
Speed
12.4 kn
Course
235°
Heading
238°
39.7051° N, 139.8437° 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
Jin Hai Ping
IMO numberWhat is an IMO number?
9591040
MMSIWhat is an MMSI?
413700260
Call signWhat is a call sign?
BPAI7
Flag
China
Vessel type
Bulk carrier
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
29,476
Length overall
189 m
Beam
32 m
Year built
2014

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 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 HKHKGArrival(matched by call sign)Jun 30, 2025, 08:34 UTCSWLAHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalApr 11, 2023, 21:38 UTCWLHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Sep 14, 2022, 13:57 UTCPTHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalApr 3, 2021, 17:33 UTCPSSAHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Mar 20, 2020, 00:51 UTCPTHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Sep 3, 2019, 08:39 UTCSHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Jul 23, 2019, 09:11 UTCPTHong Kong vessel arrivals & departures (incl. VTMS daily reports)

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

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

Frequently asked questions

Where is Jin Hai Ping now?
Jin Hai Ping (Bulk carrier, China flag) was last seen on AIS on Oct 6, 2026, 09:13 UTC, under way at 12.4 kn, in the Sea of Japan. The crew-entered destination was TIAN JIN (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 08:25 UTC). This report does not confirm the ship’s current route.
What kind of ship is Jin Hai Ping?
Jin Hai Ping is a bulk carrier sailing under the flag of China, built in 2014. The vessel is 189 m long with a beam of 32 m and has a gross tonnage of 29,476.
What sanctions and inspection records does Voydar hold for Jin Hai Ping?
Voydar has no matched sanctions record displayed for Jin Hai Ping 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 Jin Hai Ping. 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/9591040
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