ONE READINESS
Container ship · Singapore · AIS Class A
In short
ONE READINESS (Container ship, Singapore flag) was last seen on AIS on , under way at 19.7 kn, in the 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 USLAX (Los Angeles), with an ETA of Nov 25, 2026, 23:00 UTC; its reported draught is 13.5 m (voyage report via AISstream.io global terrestrial AIS, received Nov 13, 2026, 11:20 UTC). ISM manager: Seaspan Ship Management Ltd. (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
Current voyage: from Yokohama (departed Nov 13, 2026, 06:59 UTC) to USLAX (Los Angeles)
- Vessel type
- Container ship
- Flag
- Singapore
- Year built
- —
- Gross tonnage
- —
- Size, AIS-reported (length × beam)
- 272 m × 43 m
- ISM manager
- Seaspan Ship Management Ltd.
Last reported position: 34.9631° N, 140.972° E · North Pacific Ocean · See on the map
Watch this ship
ONE READINESS has not been received for a while. Follow it for an email update when Voydar receives a new position, and for arrival and departure alerts.
Voydar last heard ONE READINESS on November 13, 2026. Our receivers cover coasts and busy waters, so alerts resume when it is next in range.
What you would have been told
Nothing in the last 24 hours: no arrival or departure at a port. You are told the moment that changes.
Detected from AIS, as of Nov 20, 2026, 19:46 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for ONE READINESS reach you the moment they happen, arrival-time changes included. When it ends you stay on Free, with a daily email, unless you keep Plus (US$7 a month). Compare plans
Get alerts on your phone: the Voydar app
Last reported position
received- Position
- 34.9631° N, 140.972° E
- Area
- North Pacific Ocean
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 19.7 kn
- Course
- 69°
- Heading
- 70°
- Compass: course over ground 69°, heading 70°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 4 port calls (Yokohama, Tokyo, and Oakland).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows ONE READINESS's track before the last 30 days. Voydar has recorded its port calls since July 24, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
- Name
- ONE READINESS
- IMO numberWhat is an IMO number?
- 9952684
- MMSIWhat is an MMSI?
- 563295800
- Call signWhat is a call sign?
- 9V3203
- Flag
- Singapore
- Gross tonnageGross tonnage vs deadweight
- —
- Length (AIS-reported)
- Broadcast by the ship over AIS, not a register entry. Received via AISstream.io global terrestrial AIS on November 13, 2026.272 m
- Beam (AIS-reported)
- Broadcast by the ship over AIS, not a register entry. Received via AISstream.io global terrestrial AIS on November 13, 2026.43 m
- Year built
- —
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.
AIS-reported: the size the ship itself broadcasts over AIS, in whole metres, as entered on board. It is not a register entry. Received via AISstream.io global terrestrial AIS on November 13, 2026.
Ownership & management
Each line shows where the fact comes from. Links backed by an identifier point to the company page.
- ISM manager
- Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–2025 · reported · high confidence · retrieved Nov 16, 2026
Checking ownership or sanctions for your business? Teams screen fleets by IMO, keep watch with alerts and keep a dated record. Voydar for business →
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 |
|---|---|---|
| Left YokohamaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at YokohamaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left TokyoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at TokyoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left TokyoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at TokyoAIS-detected | Voydar 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.
Emissions & fuel consumption
Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.
| Year | CO₂ emitted | Fuel burned | Time at sea | CO₂ / n mile |
|---|---|---|---|---|
| 2023 | 3,172 t | 1,007 t | 11 days | 652 kg |
| 2024 | 34,169 t | 10,929 t | 187 days | 509 kg |
| 2025 | 7,034 t | 2,249 t | 38 days | 561 kg |
Technical efficiency: EEXI (8.34 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.
Compared with ships of its type
Where this ship’s reported CO₂ intensity for 2025 sits among the ships EU MRV lists as “Container ship”. Lower is less CO₂.
- CO₂ per tonne of cargo carried one nautical mile8.83 g per tonne-nautical mile
- Lowest reportedHighest reported
20% of the 2,233 ships in this group reported a lower figure.
Group: lower quartile 9.85 · median 16.45 · upper quartile 29.35
- CO₂ per nautical mile sailed561.2 kg per nautical mile
- Lowest reportedHighest reported
52% of the 2,256 ships in this group reported a lower figure.
Group: lower quartile 313.5 · median 541.9 · upper quartile 768.9
Calculated by Voydar from the figures ships report under EU MRV. This is not a rating and not the IMO Carbon Intensity Indicator (CII). EU MRV covers ships over 5,000 gross tonnage on voyages to, from and within the EU/EEA, so the group is those ships, not the world fleet. How this is calculated
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
| Port | Arrived | Departed | Time in port |
|---|---|---|---|
| Yokohama JPYOK | Nov 12, 2026, 21:52 UTC | Nov 13, 2026, 06:59 UTC | 9 h 7 min |
| Tokyo JPTYO | Nov 11, 2026, 22:30 UTC | Nov 12, 2026, 20:53 UTC | 22 h 23 min |
| Tokyo JPTYO | Nov 3, 2026, 08:51 UTC | Nov 4, 2026, 09:51 UTC | 24 h 59 min |
| Oakland USOAK | Oct 22, 2026, 00:09 UTC | Oct 23, 2026, 03:56 UTC | 27 h 47 min |
| Los Angeles USLAX | Oct 15, 2026, 12:46 UTC | Oct 20, 2026, 13:08 UTC | 5 d 0 h |
| Aomi JPOMA | Sep 30, 2026, 22:31 UTC | Oct 1, 2026, 21:52 UTC | 23 h 22 min |
| Chiba JPCHB | Sep 29, 2026, 23:52 UTC | Sep 30, 2026, 21:58 UTC | 22 h 6 min |
| Zandvliet BEZVT | Aug 2, 2026, 09:47 UTC | Aug 3, 2026, 02:18 UTC | 16 h 31 min |
| Hamburg DEHAM | Jul 27, 2026, 07:12 UTC | Jul 28, 2026, 15:26 UTC | 32 h 13 min |
| Helgoland DEHGL | Jul 24, 2026, 08:10 UTC | Jul 26, 2026, 22:41 UTC | 2 d 14 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.
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.
Predicted arrival
Voydar estimates arrival at Los Angeles around Dec 1, 2026, 11:04 UTC, most likely between Nov 25, 2026, 02:33 UTC and Dec 8, 2026, 22:54 UTC. Based on 20 past transits between JPYOK and Los Angeles seen in our port calls. The crew-reported ETA is Nov 25, 2026, 23:00 UTC.
Medium (51%) · Method seadar.behaviour.eta_prediction v1
| When | What we observed | Confidence |
|---|---|---|
| Nov 12, 2026, 15:28 UTC | Draught change Reported draught went from 12.2 m to 13.5 m while in port at Tokyo. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 4, 2026, 08:22 UTC | Draught change Reported draught went from 11.9 m to 10.8 m while in port at Tokyo. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 23, 2026, 02:00 UTC | Draught change Reported draught went from 11.1 m to 12.1 m while in port at Oakland. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 20, 2026, 00:05 UTC | Draught change Reported draught went from 12.6 m to 11.2 m while in port at Los Angeles. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 1, 2026, 08:02 UTC | Draught change Reported draught went from 11.6 m to 13.4 m while in port at Aomi. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
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.
Frequently asked questions
- What kind of ship is ONE READINESS?
- ONE READINESS is a container ship sailing under the flag of Singapore.
- Who is recorded as the owner or manager of ONE READINESS?
- Seaspan Ship Management Ltd. is recorded as ISM manager for ONE READINESS (source: EU MRV (THETIS-MRV) emissions; reporting years 2024–2025). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for ONE READINESS?
- Voydar has no matched sanctions record displayed for ONE READINESS from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels, the New Zealand Russia Sanctions Register and the French national asset-freeze register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for ONE READINESS. Missing records do not establish whether the ship has been detained.
Full Vessel Report
A dated PDF with the complete track since June 2026, every port call, ownership and flag changes, inspections, a sanctions and dark-activity screening snapshot, emissions, companies and every source.
Sample: a real report for EVER GIVEN (IMO 9811000), built from public data and marked SAMPLE on every page.
Every fact on this page stays free.
Know this ship?
Help other readers. Member posts are shown as member content, never as sourced data.
- Date, place and an optional note
- Members who know her can answer
- Suggest a correctionChecked against sources before anything changes
More Container ships
Other container ships with full Voydar profiles. A different set each day. All container ships
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/9952684Cite this page
ONE READINESS. Voydar (voydar.com). https://www.voydar.com/vessel/9952684-one-readiness. Retrieved November 20, 2026.
Each fact above names its own source and date. Cite that primary source too when you rely on a fact.
Using this data in code?
Every account gets a personal API allowance: 2,500 credits a month free, 25,000 with Pro. Pro includes use in your own product. Growth and Scale add volume, and each includes one Pro membership.