Skip to content

Aikou Maru

Oil tanker · Japan · built 2012 · AIS Class A

IMO9658836MMSI431003751Call signJD3395Last AIS position Oct 1, 2026, 13:05 UTC

In short

Aikou Maru (Oil tanker, Japan flag) was last seen on AIS on , at anchor, in the port of Chiba. Its crew-entered AIS destination is >JP CHB OFF, with an ETA of Oct 1, 2026, 16:30 UTC; its reported draught is 4.7 m (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 13:39 UTC). It arrived there on Oct 1, 2026, 07:15 UTC.

Vessel type
Oil tanker
Flag
Japan
Year built
2012
Gross tonnage
1,960
Size (length × beam)
89 m × 14 m
Registered owner
—

Watch this ship

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

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
35.5878° N, 140.0428° E
Area
North Pacific Ocean
Speed
0 kn
Course
190°
Heading
317°
35.5878° N, 140.0428° E
Open the full live map →

Last 30 days: 3 port calls (Chiba and Kawasaki).

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
Aikou Maru
IMO numberWhat is an IMO number?
9658836
MMSIWhat is an MMSI?
431003751
Call signWhat is a call sign?
JD3395
Flag
Japan
Vessel type
Oil tanker
AIS ship type
Tanker
Gross tonnageGross tonnage vs deadweight
1,960
Length overall
89 m
Beam
14 m
Year built
2012

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.

DateEventSource
Arrived at ChibaAIS-detectedSeadar port-call detector (AIS geofence)
Left KawasakiAIS-detectedSeadar port-call detector (AIS geofence)
Arrived at KawasakiAIS-detectedSeadar port-call detector (AIS geofence)
Left ChibaAIS-detectedSeadar port-call detector (AIS geofence)
Arrived at ChibaAIS-detectedSeadar port-call detector (AIS geofence)

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
Chiba JPCHBOct 1, 2026, 07:15 UTCin port—
Kawasaki JPKWSSep 29, 2026, 09:07 UTCOct 1, 2026, 01:34 UTC40 h 27 min
Chiba JPCHBSep 25, 2026, 09:24 UTCSep 26, 2026, 03:19 UTC17 h 55 min

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.

Behaviour at sea Seadar-derived

Patterns Seadar derived from this ship's AIS broadcasts. They are inferences, not reports: each one shows how it was computed and how confident we are, and none of them says why a ship behaved this way.

WhenWhat we observedConfidence
Oct 1, 2026, 07:09 UTC
Draught change

Reported draught went from 5.7 m to 4.7 m after leaving Kawasaki. Seadar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (55%)
Oct 1, 2026, 00:41 UTC
Draught change

Reported draught went from 4.7 m to 5.7 m while in port at Kawasaki. Seadar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Sep 27, 2026, 02:37 UTC
Draught change

Reported draught went from 5.6 m to 4.6 m after leaving Chiba. Seadar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (55%)

Source: AISstream.io global terrestrial AIS. AIS data: AISstream.io. Licence: none published.

Derived from AIS positions of feeds whose terms allow display on Seadar. Coverage is terrestrial: gaps are reported only where our receivers kept hearing other ships. Detections below medium confidence are not shown.

How these are computed →

Frequently asked questions

Where is Aikou Maru now?
Aikou Maru (Oil tanker, Japan flag) was last seen on AIS on Oct 1, 2026, 13:05 UTC, at anchor, in the port of Chiba. The crew-entered destination was >JP CHB OFF (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 13:39 UTC). This report does not confirm the ship’s current route.
What kind of ship is Aikou Maru?
Aikou Maru is an oil tanker sailing under the flag of Japan, built in 2012 by Yamanaka Shipbuilding. The vessel is 89 m long with a beam of 14 m and has a gross tonnage of 1,960.
What sanctions and inspection records does Seadar hold for Aikou Maru?
Seadar has no matched sanctions record displayed for Aikou Maru 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 Aikou 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/9658836
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