Voydar has no displayable AIS position for Sakura in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.

What kind of ship is Sakura?

Sakura is a tanker, built in 1998 by Shin Kurushima Dockyard. The vessel is 147 m long with a beam of 24 m and has a gross tonnage of 12,044.

What sanctions and inspection records does Voydar hold for Sakura?

Voydar has no matched sanctions record displayed for Sakura 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 Sakura. Missing records do not establish whether the ship has been detained.

Sakura

Tanker · built 1998

IMO9161895No AIS position on record

Open in Terminal

In short

Sakura (Tanker) has no AIS position on record with Voydar.

Vessel type: Tanker
Flag: —
Year built: 1998
Gross tonnage: 12,044
Size (length × beam): 147 m × 24 m
Registered owner: —

Watch this ship

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

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

No AIS position on record for this vessel. Identity and particulars are 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: Sakura
IMO numberWhat is an IMO number?: 9161895
MMSIWhat is an MMSI?: —
Call signWhat is a call sign?: —
Flag: —
Vessel type: Tanker
Gross tonnageGross tonnage vs deadweight: 12,044
Deadweight (DWT): Source: Wikidata, record Q117019752. Added to Voydar on September 23, 2026. Licence: CC0 1.0.19,365 t
Length overall: 147 m
Beam: 24 m
Year built: 1998

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: Shin Kurushima Dockyard
Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026

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.

Date	Event	Source
Oct 31, 2016	Reported departure from Long BeachAuthority-reported	USACE foreign traffic vessel entrances & clearances
Oct 31, 2016	Reported arrival at Long BeachAuthority-reported	USACE foreign traffic vessel entrances & clearances
Jul 28, 2016	Reported arrival at ANACORTES HARBOR, WAAuthority-reported	USACE 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

Port	Record	Date (UTC)	Berth	Source
Long Beach USLGB	Departure	Oct 31, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Long Beach USLGB	Arrival	Oct 31, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
ANACORTES HARBOR, WA	Arrival	Jul 28, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
ANACORTES HARBOR, WA	Departure	Jul 28, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Richmond USRCH	Departure	Jul 22, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Richmond USRCH	Arrival	Jul 20, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Richmond USRCH	Departure	May 1, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Richmond USRCH	Arrival	Apr 29, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Richmond USRCH	Departure	Feb 1, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Stockton USSCK	Arrival	Jan 27, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Seattle USSEA	Departure	Jan 23, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Seattle USSEA	Arrival	Jan 20, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances

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

Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.

Frequently asked questions

Where is Sakura now?: Voydar has no displayable AIS position for Sakura in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is Sakura?: Sakura is a tanker, built in 1998 by Shin Kurushima Dockyard. The vessel is 147 m long with a beam of 24 m and has a gross tonnage of 12,044.
What sanctions and inspection records does Voydar hold for Sakura?: Voydar has no matched sanctions record displayed for Sakura 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 Sakura. 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/9161895

View JSON API documentationFree without a key for occasional use; use an API key for more.

Follow by RSS Open data

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