Skip to content

SEACON TOKYO

Bulk carrier · Singapore · AIS Class A

IMO9941958MMSI563189400Call sign9V8846Last AIS position Sep 24, 2026, 05:52 UTC

In short

SEACON TOKYO (Bulk carrier, Singapore flag) was last seen on AIS on , under way at 3.7 kn, near Hong Kong (South 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 HK HKG (Hong Kong); its reported draught is 12.9 m (voyage report via AISstream.io global terrestrial AIS, received Sep 23, 2026, 23:59 UTC). ISM manager: SEACON SHIPS MANAGEMENT PTE. LTD. (source: EU MRV (THETIS-MRV) emissions, reporting year 2024).

Vessel type
Bulk carrier
Year built
—
Gross tonnage
—
Size (length × beam)
200 m × 32 m

Watch this ship

SEACON TOKYO has not been received for a while. Follow it and we will email you as soon as it is heard again, then when it reaches or leaves port.

Free forever. No card. A free account follows up to 5 ships and ports.

Last reported position

received
Position
22.166° N, 114.1104° E
Area
South China Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
3.7 kn
Course
189°
Heading
189°
22.166° N, 114.1104° 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)Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name
SEACON TOKYO
IMO numberWhat is an IMO number?
9941958
MMSIWhat is an MMSI?
563189400
Call signWhat is a call sign?
9V8846
AIS ship type
Cargo
Length overall
200 m
Beam
32 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.

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 year 2024 · reported · confidence 0.9 · retrieved Oct 5, 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 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.

Emissions & fuel consumption

Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.

YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
20243,553 t1,132 t63 days206 kg

Technical efficiency: EEDI (3.13 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.

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
Hong Kong HKHKGArrivalSep 24, 2026, 01:34 UTCSWLAHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalJun 23, 2026, 19:44 UTCSELAHong Kong vessel arrivals & departures (incl. VTMS daily reports)

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

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

Frequently asked questions

Where is SEACON TOKYO now?
SEACON TOKYO (Bulk carrier, Singapore flag) was last seen on AIS on Sep 24, 2026, 05:52 UTC, under way at 3.7 kn, near Hong Kong (South 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 HK HKG (voyage report via AISstream.io global terrestrial AIS, received Sep 23, 2026, 23:59 UTC). This report does not confirm the ship’s current route.
What kind of ship is SEACON TOKYO?
SEACON TOKYO is a bulk carrier sailing under the flag of Singapore. The vessel is 200 m long with a beam of 32 m.
Who is recorded as the owner or manager of SEACON TOKYO?
SEACON SHIPS MANAGEMENT PTE. LTD. is recorded as ISM manager for SEACON TOKYO (source: EU MRV (THETIS-MRV) emissions; reporting year 2024). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for SEACON TOKYO?
Voydar has no matched sanctions record displayed for SEACON TOKYO 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 SEACON TOKYO. 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/9941958
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