Skip to content

Hakuho Maru

Other · Japan · built 1988 · AIS Class A

IMO8714700MMSI431010000Call signJDSSLast AIS position Oct 5, 2026, 16:00 UTC

In short

Hakuho Maru (Other, Japan flag) was last seen on AIS on , moored, in the port of Tokyo. Its crew-entered AIS destination is >JP TYO M; its reported draught is 6.3 m (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 15:50 UTC). It arrived there on Oct 3, 2026, 00:24 UTC.

Vessel type
Other
Flag
Japan
Year built
1988
Gross tonnage
3,987
Size (length × beam)
100 m
Registered owner
—

Watch this ship

Get an email when Hakuho Maru 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.

Photo of Hakuho Maru
Photo: Bahnfrend · Licence: CC BY-SA 4.0 · via Wikimedia Commons

Last reported position

received
Position
35.6252° N, 139.7959° E
Area
North Pacific Ocean
Speed
0 kn
Course
45°
Heading
147°
35.6252° N, 139.7959° E
Open the full live map →

Last 30 days: 1 port call (Tokyo).

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
Hakuho Maru
IMO numberWhat is an IMO number?
8714700
MMSIWhat is an MMSI?
431010000
Flag
Japan
Vessel type
Other
Gross tonnageGross tonnage vs deadweight
3,987
Length overall
100 m
Beam
—
Year built
1988

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
Arrived at TokyoAIS-detectedVoydar port-call detector (AIS geofence)
Reported departure from HonoluluAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from San DiegoAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from PonceAuthority-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
Tokyo JPTYOOct 3, 2026, 00:24 UTCin port—

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
Honolulu USHNLDepartureJul 17, 2014(date only)—USACE foreign traffic vessel entrances & clearances
San Diego USSANDepartureOct 25, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Ponce PRPSEDepartureSep 17, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Ponce PRPSEArrivalSep 13, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Honolulu USHNLDepartureFeb 22, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Honolulu USHNLDepartureDec 23, 2011(date only)—USACE foreign traffic vessel entrances & clearances
San Francisco USSFODepartureSep 7, 2011(date only)—USACE foreign traffic vessel entrances & clearances
San Francisco USSFOArrivalSep 5, 2011(date only)—USACE foreign traffic vessel entrances & clearances
Honolulu USHNLDepartureSep 17, 2010(date only)—USACE foreign traffic vessel entrances & clearances
Honolulu USHNLArrivalSep 14, 2010(date only)—USACE foreign traffic vessel entrances & clearances
Ponce PRPSEDepartureSep 6, 2009(date only)—USACE foreign traffic vessel entrances & clearances
Ponce PRPSEArrivalSep 3, 2009(date only)—USACE foreign traffic vessel entrances & clearances

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

Frequently asked questions

Where is Hakuho Maru now?
Hakuho Maru (Other, Japan flag) was last seen on AIS on Oct 5, 2026, 16:00 UTC, moored, in the port of Tokyo. The crew-entered destination was >JP TYO M (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 15:50 UTC). This report does not confirm the ship’s current route.
What kind of ship is Hakuho Maru?
Hakuho Maru is a other sailing under the flag of Japan, built in 1988. The vessel is 100 m long and has a gross tonnage of 3,987.
What sanctions and inspection records does Voydar hold for Hakuho Maru?
Voydar has no matched sanctions record displayed for Hakuho Maru 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 Hakuho Maru. 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/8714700
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