Skip to content

Tsukasa

Oil tanker · Japan · built 2013 · AIS Class A

IMO9691242MMSI431004957Call signJD3561Last AIS position Sep 30, 2026, 22:12 UTC

In short

Tsukasa (Oil tanker, Japan flag) was last seen on AIS on , under way at 1.4 kn, near Chiba (North Pacific Ocean). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its crew-entered AIS destination is >JP CHB DEZU A, with an ETA of Oct 1, 2026, 07:30 UTC; its reported draught is 5.3 m (voyage report via AISstream.io global terrestrial AIS, received Sep 30, 2026, 22:14 UTC).

Current voyage: from Kawasaki (departed Sep 25, 2026, 04:19 UTC) to >JP CHB DEZU A

Vessel type
Oil tanker
Flag
Japan
Year built
2013
Gross tonnage
3,615
Size (length × beam)
104 m × 16 m
Registered owner
—

Watch this ship

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

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.5926° N, 140.1117° E
Area
North Pacific Ocean
StatusWhat do AIS statuses mean?
Under way using engine
Speed
1.4 kn
Course
40°
Heading
5°
35.5926° N, 140.1117° E
Open the full live map →

Last 30 days: 2 port calls (Kawasaki).

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
Tsukasa
IMO numberWhat is an IMO number?
9691242
MMSIWhat is an MMSI?
431004957
Call signWhat is a call sign?
JD3561
Flag
Japan
Vessel type
Oil tanker
AIS ship type
Tanker
Gross tonnageGross tonnage vs deadweight
3,615
Length overall
104 m
Beam
16 m
Year built
2013

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
Left KawasakiAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at KawasakiAIS-detectedVoydar port-call detector (AIS geofence)
Left KawasakiAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at KawasakiAIS-detectedVoydar 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 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
Kawasaki JPKWSSep 24, 2026, 23:54 UTCSep 25, 2026, 04:19 UTC4 h 25 min
Kawasaki JPKWSSep 22, 2026, 22:31 UTCSep 23, 2026, 03:02 UTC4 h 31 min

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.

Behaviour at sea Voydar-derived

Patterns Voydar 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
Sep 25, 2026, 03:28 UTC
Draught change

Reported draught went from 6.3 m to 5.3 m while in port at Kawasaki. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Sep 23, 2026, 03:31 UTC
Draught change

Reported draught went from 6.3 m to 5.3 m after leaving Kawasaki. Voydar 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 Voydar. 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 Tsukasa now?
Tsukasa (Oil tanker, Japan flag) was last seen on AIS on Sep 30, 2026, 22:12 UTC, under way at 1.4 kn, near Chiba (North Pacific Ocean). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was >JP CHB DEZU A (voyage report via AISstream.io global terrestrial AIS, received Sep 30, 2026, 22:14 UTC). This report does not confirm the ship’s current route.
What kind of ship is Tsukasa?
Tsukasa is an oil tanker sailing under the flag of Japan, built in 2013. The vessel is 104 m long with a beam of 16 m and has a gross tonnage of 3,615.
What sanctions and inspection records does Voydar hold for Tsukasa?
Voydar has no matched sanctions record displayed for Tsukasa 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 Tsukasa. 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/9691242
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