Skip to content

ONE THESEUS

Cargo ship · Japan · built 2008 · AIS Class A

IMO9356701MMSI431027000Call sign7KILLast AIS position Sep 26, 2026, 03:29 UTC

In short

ONE THESEUS (Cargo ship, Japan flag) was last seen on AIS on , under way at 15.4 kn, in the East China Sea. 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 CNTXG (Tianjin Xingang Pt); its reported draught is 12.8 m (voyage report via AISstream.io global terrestrial AIS, received Sep 25, 2026, 08:09 UTC).

Vessel type
Cargo ship
Flag
Japan
Year built
2008
Gross tonnage
76,789
Size (length × beam)
304 m
Registered owner
—

Watch this ship

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

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 ONE THESEUS
Photo: SteKrueBe · Licence: CC BY-SA 3.0 · via Wikimedia Commons

Last reported position

received
Position
29.7218° N, 123.4913° E
Area
East China Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
15.4 kn
Course
4°
Heading
0°
29.7218° N, 123.4913° 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
ONE THESEUS
IMO numberWhat is an IMO number?
9356701
MMSIWhat is an MMSI?
431027000
Flag
Japan
Vessel type
Cargo ship
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
76,789
Length overall
304.1 m
Beam
—
Year built
2008

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 Voydar holds, newest first. Each line names its source; derived items say how they were derived.

DateEventSource
Reported arrival at OaklandAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from OaklandAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from Los AngelesAuthority-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
Oakland USOAKArrivalDec 20, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Oakland USOAKDepartureDec 20, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXDepartureDec 17, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXArrivalDec 15, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Oakland USOAKArrivalOct 26, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Oakland USOAKDepartureOct 26, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXDepartureOct 24, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXArrivalOct 22, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Oakland USOAKArrivalAug 4, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Oakland USOAKDepartureAug 4, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Long Beach USLGBDepartureAug 1, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Long Beach USLGBArrivalJul 30, 2016(date only)—USACE foreign traffic vessel entrances & clearances

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

Frequently asked questions

Where is ONE THESEUS now?
ONE THESEUS (Cargo ship, Japan flag) was last seen on AIS on Sep 26, 2026, 03:29 UTC, under way at 15.4 kn, in the East China Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was CNTXG (voyage report via AISstream.io global terrestrial AIS, received Sep 25, 2026, 08:09 UTC). This report does not confirm the ship’s current route.
What kind of ship is ONE THESEUS?
ONE THESEUS is a cargo ship sailing under the flag of Japan, built in 2008 by HD Hyundai Heavy Industries. The vessel is 304.1 m long and has a gross tonnage of 76,789.
What sanctions and inspection records does Voydar hold for ONE THESEUS?
Voydar has no matched sanctions record displayed for ONE THESEUS 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 ONE THESEUS. 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/9356701
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