FUTURE OCEAN
Cargo ship · Bahamas · built 2005 · AIS Class A
In short
FUTURE OCEAN (Cargo ship, Bahamas flag) was last seen on AIS on , under way at 9.3 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 IND-CCU, with an ETA of Oct 16, 2026, 02:00 UTC; its reported draught is 8.1 m (voyage report via AISstream.io global terrestrial AIS, received Sep 27, 2026, 05:51 UTC).
- Vessel type
- Cargo ship
- Flag
- Bahamas
- Year built
- 2005
- Gross tonnage
- 9,873
- Size (length × beam)
- 128 m × 20 m
- Registered owner
- —
Watch this ship
Get an email when FUTURE OCEAN 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 FUTURE OCEAN.
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
- 25.1012° N, 120.0147° E
- Area
- East China Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 9.3 kn
- Course
- 231°
- Heading
- 237°
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-upIdentity & particulars
- Name
- FUTURE OCEAN
- IMO numberWhat is an IMO number?
- 9309863
- MMSIWhat is an MMSI?
- 311002179
- Call signWhat is a call sign?
- C6KV6
- Flag
- Bahamas
- Vessel type
- Cargo ship
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 9,873
- Deadweight (DWT)
- Source: Wikidata, record Q105321697. Added to Voydar on September 27, 2026. Licence: CC0 1.0.14,514 t
- Length overall
- 127.6 m
- Beam
- 19.6 m
- Year built
- 2005
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.
| Date | Event | Source |
|---|---|---|
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong 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.
Incidents & investigations Authority-reported
Accident and incident reports by national investigation boards, and casualty warnings, that concern this ship. Each links to the original.
- Occurred May 5, 2020衝突 · 貨物船運輸安全委員会 船舶事故等調査報告書 (JTSB marine accident and incident reports)鹿児島県沖永良部島南東方沖 国頭岬灯台から真方位148°21.2海里付近
貨物船CSC ZHONG HAI漁船第八光洋丸衝突Report published Oct 29, 2020
貨物船CSC ZHONG HAIは、南西進中、また、漁船第八光洋丸は、漂泊中、両船が衝突した。
Source: 運輸安全委員会 船舶事故等調査報告書 (JTSB marine accident and incident reports). 出典:運輸安全委員会「船舶事故等調査報告書」(https://jtsb.mlit.go.jp/)。Seadar が項目を抽出・加工して作成 (Source: Japan Transport Safety Board marine accident reports; fields extracted and edited by Seadar). Licence: Public Data License 1.0 (公共データ利用規約 第1.0版, PDL1.0; compatible with CC BY 4.0).
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 |
|---|---|---|---|---|
| Hong Kong HKHKG | Arrival(matched by call sign) | May 2, 2026, 12:48 UTC | SWLA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Jun 18, 2025, 00:27 UTC | SWLA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Jun 2, 2024, 18:37 UTC | SELA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Dec 10, 2023, 22:32 UTC | CC | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | May 3, 2023, 22:31 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Jan 1, 2023, 02:39 UTC | PT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Dec 5, 2021, 14:46 UTC | NLA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Jun 26, 2020, 00:03 UTC | PT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Oct 7, 2019, 21:22 UTC | SELA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Jul 15, 2019, 09:41 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Jan 5, 2019, 21:37 UTC | SELA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Long Beach USLGB | Departure | Mar 26, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: April 24, 2006.
Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.
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 FUTURE OCEAN now?
- FUTURE OCEAN (Cargo ship, Bahamas flag) was last seen on AIS on Sep 27, 2026, 18:04 UTC, under way at 9.3 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 IND-CCU (voyage report via AISstream.io global terrestrial AIS, received Sep 27, 2026, 05:51 UTC). This report does not confirm the ship’s current route.
- What kind of ship is FUTURE OCEAN?
- FUTURE OCEAN is a cargo ship sailing under the flag of Bahamas, built in 2005. The vessel is 127.6 m long with a beam of 19.6 m and has a gross tonnage of 9,873.
- What sanctions and inspection records does Voydar hold for FUTURE OCEAN?
- Voydar has no matched sanctions record displayed for FUTURE OCEAN 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 FUTURE OCEAN. 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/9309863Using 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.