Skip to content

Seaspan Breeze

Container ship · Singapore · built 2014 · AIS Class A

IMO9685358MMSI563279500Call sign9VMX2Last AIS position Oct 4, 2026, 04:46 UTC

In short

Seaspan Breeze (Container ship, Singapore flag) was last seen on AIS on , under way at 10.9 kn, in the 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 SGSIN PEBG A, with an ETA of Oct 11, 2026, 20:15 UTC; its reported draught is 14.8 m (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 03:51 UTC).

Vessel type
Container ship
Year built
2014
Gross tonnage
113,042
Size (length × beam)
337 m
Registered owner
—

Watch this ship

Seaspan Breeze 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
21.9806° N, 114.4156° E
Area
South China Sea
StatusWhat do AIS statuses mean?
Under way sailing
Speed
10.9 kn
Course
169°
Heading
169°
21.9806° N, 114.4156° 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
Seaspan Breeze
IMO numberWhat is an IMO number?
9685358
MMSIWhat is an MMSI?
563279500
Call signWhat is a call sign?
9VMX2
Vessel type
Container ship
AIS ship type
Cargo (hazardous cat. A)
Gross tonnageGross tonnage vs deadweight
113,042
Length overall
337 m
Beam
—
Year built
2014

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.

Operator
Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
ISM manager
Source: EU MRV (THETIS-MRV) emissions · reporting year 2025 · reported · confidence 0.9 · retrieved Oct 5, 2026
Source: EU MRV (THETIS-MRV) emissions · reporting year 2025 · reported · confidence 0.9 · retrieved Oct 5, 2026
Builder
Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 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 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)
Former name: MOL BreezeWikidata

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.

Former and other names

Names attested for this ship other than its current name.

NameEvidenceDateSource
MOL BreezeFormer nameJan 1, 2014Wikidata

A sanctions list's date is the earliest date the list shows the name, not when the ship took it. A name on a list is shown as a former name only where AIS shows the ship using another name after that date; otherwise it is listed as a name the list uses. AIS name changes are dated when Voydar saw them.

Source: Wikidata. Licence: CC0 1.0.

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 Sep 27, 2015衝突(単) · 貨物船運輸安全委員会 船舶事故等調査報告書 (JTSB marine accident and incident reports)愛知県名古屋港飛島ふ頭TS2岸壁 名古屋港高潮防波堤中央堤西灯台から真方位048°1.6海里(M)付近

    コンテナ船MOL BREEZE衝突(岸壁)Report published Feb 23, 2017

    コンテナ船MOL BREEZEは、左回頭中、岸壁に衝突した。 MOL BREEZEは、球状船首右舷側に凹損を生じ、また、岸壁の上部部材の変形等を生じた。

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).

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
201824,504 t7,835 t81 days800 kg
202513,476 t4,307 t64 days579 kg

Technical efficiency: EEXI (10.5 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 HKHKGArrival(matched by call sign)Oct 30, 2019, 06:48 UTCPTHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalSep 16, 2019, 12:34 UTCKC5Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Aug 6, 2019, 03:49 UTCWLHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalJun 24, 2019, 12:47 UTCKC5Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalApr 2, 2019, 15:39 UTCKC10Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalDec 31, 2018, 20:26 UTCSELAHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Jun 3, 2018, 00:55 UTCWLHong Kong vessel arrivals & departures (incl. VTMS daily reports)

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

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

Frequently asked questions

Where is Seaspan Breeze now?
Seaspan Breeze (Container ship, Singapore flag) was last seen on AIS on Oct 4, 2026, 04:46 UTC, under way at 10.9 kn, in the 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 SGSIN PEBG A (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 03:51 UTC). This report does not confirm the ship’s current route.
What kind of ship is Seaspan Breeze?
Seaspan Breeze is a container ship sailing under the flag of Singapore, built in 2014 by Jiangsu Yangzi Xinfu Shipbuilding. The vessel is 337 m long and has a gross tonnage of 113,042.
What sanctions and inspection records does Voydar hold for Seaspan Breeze?
Voydar has no matched sanctions record displayed for Seaspan Breeze 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 Seaspan Breeze. 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/9685358
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