Skip to content

KS SUNGLORY

Cargo ship · Belize · built 2006 · AIS Class A

IMO9392585MMSI312000095Call signV3VE6Last AIS position Oct 2, 2026, 19:59 UTC

In short

KS SUNGLORY (Cargo ship, Belize flag) was last seen on AIS on , under way at 6.4 kn, near Wakayama (North Pacific Ocean). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Registered owner: 비너스해운(주) (source: 해양수산부 국제선박등록정보 (Korean International Ship Register)).

Vessel type
Cargo ship
Flag
Belize
Year built
2006
Gross tonnage
1,972
Size (length × beam)
81 m × 14 m
Registered owner
비너스해운(주)

Watch this ship

KS SUNGLORY 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
34.2093° N, 134.985° E
Area
North Pacific Ocean
StatusWhat do AIS statuses mean?
Under way using engine
Speed
6.4 kn
Course
9°
Heading
9°
34.2093° N, 134.985° 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
KS SUNGLORY
IMO numberWhat is an IMO number?
9392585
MMSIWhat is an MMSI?
312000095
Call signWhat is a call sign?
V3VE6
Flag
Belize
Vessel type
Cargo ship
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
1,972
Length overall
81 m
Beam
13.6 m
Year built
2006

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.

Registered owner
비너스해운(주)(not linked to a company record)
Source: 해양수산부 국제선박등록정보 (Korean International Ship Register) · reported · confidence 0.9 · retrieved Oct 6, 2026
Builder
청도 헤šœ조선소(QINGDAO HESHUN SHIPYARD CO., LTD.)(not linked to a company record)
Source: 해양수산부 국제선박등록정보 (Korean International Ship Register) · reported · confidence 0.9 · retrieved Oct 6, 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)

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 Dec 9, 2021乗揚 · 貨物船運輸安全委員会 船舶事故等調査報告書 (JTSB marine accident and incident reports)鳴門海峡(大鳴門橋直下の浅所) 門埼灯台から真方位242°650m付近

    貨物船ANNA乗揚Report published Oct 27, 2022

    貨物船ANNAは、南東進中、浅所に乗り揚げた。 ANNAは、船首部船底に擦過傷を生じた。

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

PortRecordDate (UTC)BerthSource
Hong Kong HKHKGArrivalMar 1, 2020, 18:50 UTCNWLAHong Kong vessel arrivals & departures (incl. VTMS daily reports)

Records published by the authority named on each row. Earliest record for this ship: March 1, 2020.

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

Frequently asked questions

Where is KS SUNGLORY now?
KS SUNGLORY (Cargo ship, Belize flag) was last seen on AIS on Oct 2, 2026, 19:59 UTC, under way at 6.4 kn, near Wakayama (North Pacific Ocean). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report.
What kind of ship is KS SUNGLORY?
KS SUNGLORY is a cargo ship sailing under the flag of Belize, built in 2006. The vessel is 81 m long with a beam of 13.6 m and has a gross tonnage of 1,972.
Who is recorded as the owner or manager of KS SUNGLORY?
비너스해운(주) is recorded as Registered owner for KS SUNGLORY (source: 해양수산부 국제선박등록정보 (Korean International Ship Register)). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for KS SUNGLORY?
Voydar has no matched sanctions record displayed for KS SUNGLORY 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 KS SUNGLORY. 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/9392585
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