Skip to content

Ken Goh

Bulk carrier · Panama · built 2001 · AIS Class A

IMO9236066MMSI356347000Call signHP7161Last AIS position Aug 4, 2026, 16:18 UTC

In short

Ken Goh (Bulk carrier, Panama flag) was last seen on AIS on , moored, near Nelson (South Pacific Ocean). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report.

Vessel type
Bulk carrier
Flag
Panama
Year built
2001
Gross tonnage
19,707
Size (length × beam)
172 m
Registered owner
—

Watch this ship

Get an email when Ken Goh 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 Ken Goh.

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.

Photo of KEN GOH
Photo: Farid mernissi · Licence: CC BY-SA 4.0 · via Wikimedia Commons

Last reported position

received
Position
41.2585° S, 173.2763° E
Area
South Pacific Ocean
Speed
0 kn
Course
154°
Heading
261°
41.2585° S, 173.2763° 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
Ken Goh
IMO numberWhat is an IMO number?
9236066
MMSIWhat is an MMSI?
356347000
Call signWhat is a call sign?
HP7161
Flag
Panama
Vessel type
Bulk carrier
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
19,707
Length overall
171.6 m
Beam
—
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.

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 PORT OF HOPEWELL, VA (INCLUDED IN JAMES RIVER VA CONSOLIDATED REPORT)Authority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at 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.

Reported by authorities Authority-reported

PortRecordDate (UTC)BerthSource
Hong Kong HKHKGArrivalJul 24, 2023, 13:35 UTCSWLAHong Kong vessel arrivals & departures (incl. VTMS daily reports)
PORT OF HOPEWELL, VA (INCLUDED IN JAMES RIVER VA CONSOLIDATED REPORT)DepartureOct 15, 2016(date only)—USACE foreign traffic vessel entrances & clearances
ELIZABETH RIVER, VAArrivalOct 3, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Panama City USPFNDepartureMay 22, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Panama City USPFNArrivalMay 17, 2015(date only)—USACE foreign traffic vessel entrances & clearances
New Orleans USMSYDepartureSep 5, 2014(date only)—USACE foreign traffic vessel entrances & clearances
New Orleans USMSYArrivalAug 27, 2014(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)DepartureAug 24, 2014(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)ArrivalAug 16, 2014(date only)—USACE foreign traffic vessel entrances & clearances
New Orleans USMSYDepartureAug 12, 2014(date only)—USACE foreign traffic vessel entrances & clearances
New Orleans USMSYArrivalAug 10, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Savannah USSAVDepartureAug 6, 2014(date only)—USACE foreign traffic vessel entrances & clearances

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

Frequently asked questions

Where is Ken Goh now?
Ken Goh (Bulk carrier, Panama flag) was last seen on AIS on Aug 4, 2026, 16:18 UTC, moored, near Nelson (South Pacific Ocean). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report.
What kind of ship is Ken Goh?
Ken Goh is a bulk carrier sailing under the flag of Panama, built in 2001. The vessel is 171.6 m long and has a gross tonnage of 19,707.
What sanctions and inspection records does Voydar hold for Ken Goh?
Voydar has no matched sanctions record displayed for Ken Goh 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 Ken Goh. 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/9236066
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