Skip to content

SUNNY SAILOR

Bulk carrier · Hong Kong · built 2008 · AIS Class A

IMO9439125MMSI477267100Call signVRYI3Last AIS position Oct 6, 2026, 15:10 UTC

In short

SUNNY SAILOR (Bulk carrier, Hong Kong flag) was last seen on AIS on , under way at 10.6 kn, in the South Atlantic Ocean. Its crew-entered AIS destination is YANTAI; its reported draught is 18.6 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 15:09 UTC).

Vessel type
Bulk carrier
Year built
2008
Gross tonnage
90,091
Size (length × beam)
289 m
Registered owner
—

Watch this ship

Get an email when SUNNY SAILOR arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.

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

Photo of SUNNY SAILOR
Photo: Alf van Beem · Licence: CC0 · via Wikimedia Commons

Last reported position

received
Position
34.4383° S, 18.2661° E
Area
South Atlantic Ocean
StatusWhat do AIS statuses mean?
Under way using engine
Speed
10.6 kn
Course
115°
Heading
116°
34.4383° S, 18.2661° 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
SUNNY SAILOR
IMO numberWhat is an IMO number?
9439125
MMSIWhat is an MMSI?
477267100
Call signWhat is a call sign?
VRYI3
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
90,091
Length overall
288.9 m
Beam
—
Year built
2008

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.

DateEventSource
Reported departure from BaltimoreAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at BaltimoreAuthority-reportedUSACE foreign traffic vessel entrances & clearances

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 13, 2018死傷等 · 貨物船運輸安全委員会 船舶事故等調査報告書 (JTSB marine accident and incident reports)福山港 JFEスチール福山港導灯(前灯)から真方位178°1.3海里付近~181°1.4海里付近

    貨物船OCEAN CAESAR乗組員負傷Report published Jun 27, 2019

    貨物船OCEAN CAESARは、右舷に引船日福丸のタグラインを係止して南進中、甲板手がタグラインに当たって負傷した。

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
201810,930 t3,496 t112 days437 kg
20194,565 t1,458 t24 days587 kg
20204,522 t1,432 t35 days460 kg
20222,471 t791 t17 days539 kg

Technical efficiency: EIV (3.15 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
Baltimore USBALDepartureJun 8, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Baltimore USBALArrivalJun 2, 2012(date only)—USACE foreign traffic vessel entrances & clearances

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

Frequently asked questions

Where is SUNNY SAILOR now?
SUNNY SAILOR (Bulk carrier, Hong Kong flag) was last seen on AIS on Oct 6, 2026, 15:10 UTC, under way at 10.6 kn, in the South Atlantic Ocean. The crew-entered destination was YANTAI (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 15:09 UTC). This report does not confirm the ship’s current route.
What kind of ship is SUNNY SAILOR?
SUNNY SAILOR is a bulk carrier sailing under the flag of Hong Kong, built in 2008. The vessel is 288.9 m long and has a gross tonnage of 90,091.
What sanctions and inspection records does Voydar hold for SUNNY SAILOR?
Voydar has no matched sanctions record displayed for SUNNY SAILOR 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 SUNNY SAILOR. 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/9439125
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