Skip to content

ONE MATRIX

Container ship · Japan · built 2010 · AIS Class A

IMO9424924MMSI431510000Call sign7KSSLast AIS position Oct 1, 2026, 21:04 UTC

In short

ONE MATRIX (Container ship, Japan flag) was last seen on AIS on , moored, in the port of Oakland. Its crew-entered AIS destination is >JP TYO (Tokyo), with an ETA of Oct 13, 2026, 06:00 UTC; its reported draught is 10.4 m (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 20:57 UTC). It arrived there on Sep 30, 2026, 13:54 UTC.

Vessel type
Container ship
Flag
Japan
Year built
2010
Gross tonnage
78,316
Size (length × beam)
302 m
Registered owner
—

Watch this ship

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

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 MATRIX
Photo: dforseckorive · Licence: CC BY 2.0 · via Wikimedia Commons

Last reported position

received
Position
37.8112° N, 122.322° W
Area
North Pacific Ocean
Speed
0 kn
Course
212°
Heading
39°
37.8112° N, 122.322° W
Open the full live map →

Last 30 days: 2 port calls (Oakland and Los Angeles).

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 MATRIX
IMO numberWhat is an IMO number?
9424924
MMSIWhat is an MMSI?
431510000
Flag
Japan
Vessel type
Container ship
AIS ship type
Cargo (hazardous cat. C)
Gross tonnageGross tonnage vs deadweight
78,316
Length overall
302 m
Beam
—
Year built
2010

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 OaklandAIS-detectedVoydar port-call detector (AIS geofence)
Left Los AngelesAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Los AngelesAIS-detectedVoydar port-call detector (AIS geofence)
Reported departure from Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported arrival at Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported departure from Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported arrival at Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported departure from Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported arrival at Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)

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
Oakland USOAKSep 30, 2026, 13:54 UTCin port—
Los Angeles USLAXSep 24, 2026, 13:01 UTCSep 28, 2026, 16:51 UTC4 d 3 h

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
Hong Kong HKHKGArrivalMay 24, 2024, 21:41 UTCKC8Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalApr 8, 2024, 18:14 UTCKC10Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalMar 12, 2023, 01:44 UTCYLDHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalMar 9, 2023, 12:47 UTCKC2Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Dec 12, 2022, 22:14 UTCPTHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalSep 14, 2022, 14:47 UTCKC2Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalJun 28, 2022, 17:39 UTCMBHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalApr 5, 2022, 18:59 UTCPTHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Jan 19, 2022, 18:19 UTCKWAICHUNG CONTR. BERTH NO. 2 (TERMINAL 2)Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalNov 4, 2021, 07:53 UTCKC2Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalJun 7, 2021, 19:08 UTCKC2Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalJul 23, 2020, 03:30 UTCSELAHong Kong vessel arrivals & departures (incl. VTMS daily reports)

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

Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.

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 28, 2026, 14:47 UTC
Draught change

Reported draught went from 13.1 m to 10.4 m while in port at Los Angeles. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

High (75%)

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 ONE MATRIX now?
ONE MATRIX (Container ship, Japan flag) was last seen on AIS on Oct 1, 2026, 21:04 UTC, moored, in the port of Oakland. The crew-entered destination was >JP TYO (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 20:57 UTC). This report does not confirm the ship’s current route.
What kind of ship is ONE MATRIX?
ONE MATRIX is a container ship sailing under the flag of Japan, built in 2010. The vessel is 302 m long and has a gross tonnage of 78,316.
What sanctions and inspection records does Voydar hold for ONE MATRIX?
Voydar has no matched sanctions record displayed for ONE MATRIX 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 MATRIX. 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/9424924
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