Skip to content
voydar.com

CS STRATOS

Cargo ship · Singapore · built 2007 · AIS Class A

IMO9350991MMSI566029000Call sign9V9356Last AIS position Nov 21, 2026, 03:14 UTC

In short

CS STRATOS (Cargo ship, Singapore flag) was last seen on AIS on , under way at 10 kn, in the North Pacific Ocean. Its last detected port call was at Saint Petersburg (ex Leningrad): arrived Oct 24, 2026, left Oct 24, 2026. ISM manager: BRIGHT STAR SHIP MANAGEMENT INC. (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Data: AISHub contributors

Vessel type
Cargo ship
Year built
2007
Gross tonnage
14,030
Size (length × beam)
163 m

Last reported position: 8.5784° N, 79.3695° W · North Pacific Ocean · See on the map

Watch this ship

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

What you would have been told

Nothing in the last 24 hours: no arrival or departure at a port. You are told the moment that changes.

Detected from AIS, as of Nov 21, 2026, 03:20 UTC.

Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for CS STRATOS reach you the moment they happen, arrival-time changes included. When it ends you stay on Free, with a daily email, unless you keep Plus (US$7 a month). Compare plans

Get alerts on your phone: the Voydar app

Last reported position

received
Position
8.5784° N, 79.3695° W
Area
North Pacific Ocean
Status
Under way using engineWhat do AIS statuses mean?
Speed
10 kn
Course
349°
Heading
350°
Compass: course over ground 349°, heading 350°
NArrow: course. Hull: heading. As broadcast on AIS.
8.5784° N, 79.3695° W. Reference map only, not for navigation.
Locator map: Natural Earth (public domain)
8.5784° N, 79.3695° W
See it live in 3D →

Last 30 days: 4 port calls (Saint Petersburg (ex Leningrad)).

Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.

Data: AISHub contributors

Pro shows CS STRATOS's track before the last 30 days. Voydar has recorded its port calls since October 19, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.

Try the live demo, no sign-up

Identity & particulars

Length overall 162.5 mone tick every 25 m

Drawn by Voydar from the recorded type, length and beam. The side view is a drawing of the ship type, not of this ship; the length rule and the plan outline's proportions are to scale, the hull shape is not surveyed.
Name
CS STRATOS
IMO numberWhat is an IMO number?
9350991
MMSIWhat is an MMSI?
566029000
Call signWhat is a call sign?
9V9356
Vessel type
Cargo ship
Gross tonnageGross tonnage vs deadweight
14,030
Length overall
162.5 m
Year built
2007

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.

AIS-reported: the size the ship itself broadcasts over AIS, in whole metres, as entered on board. It is not a register entry. Received via AISstream.io global terrestrial AIS on November 9, 2026.

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 years 2024–2025 · reported · high confidence · retrieved Nov 16, 2026
Builder
Source: Wikidata · reported · high confidence · retrieved Nov 15, 2026

Checking ownership or sanctions for your business? Teams screen fleets by IMO, keep watch with alerts and keep a dated record. Voydar for business →

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
Left Saint Petersburg (ex Leningrad)AIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Saint Petersburg (ex Leningrad)AIS-detectedVoydar port-call detector (AIS geofence)
Left Saint Petersburg (ex Leningrad)AIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Saint Petersburg (ex Leningrad)AIS-detectedVoydar port-call detector (AIS geofence)
Left Saint Petersburg (ex Leningrad)AIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Saint Petersburg (ex Leningrad)AIS-detectedVoydar port-call detector (AIS geofence)
Reported departure from CANAVERAL HARBOR, FLAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at CANAVERAL HARBOR, FLAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from San DiegoAuthority-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.

Emissions & fuel consumption

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

CO₂ emitted per reporting year, tonnes (EU MRV, as reported and verified). The table below has every figure.
YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
201840,788 t13,064 t241 days400 kg
201921,255 t6,803 t132 days382 kg
202011,069 t3,530 t79 days358 kg
202110,264 t3,292 t60 days404 kg
20222,468 t791 t18 days324 kg
20232,643 t848 t21 days343 kg
20241,120 t359 t11 days368 kg
20255,659 t1,813 t33 days443 kg

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

Compared with ships of its type

Where this ship’s reported CO₂ intensity for 2025 sits among the ships EU MRV lists as “Other ship types”. Lower is less CO₂.

CO₂ per tonne of cargo carried one nautical mile68.71 g per tonne-nautical mile
Lowest reportedHighest reported

38% of the 163 ships in this group reported a lower figure.

Group: lower quartile 44.47 · median 86.9 · upper quartile 239.85

CO₂ per nautical mile sailed442.9 kg per nautical mile
Lowest reportedHighest reported

83% of the 366 ships in this group reported a lower figure.

Group: lower quartile 180.8 · median 237.4 · upper quartile 381.7

Calculated by Voydar from the figures ships report under EU MRV. This is not a rating and not the IMO Carbon Intensity Indicator (CII). EU MRV covers ships over 5,000 gross tonnage on voyages to, from and within the EU/EEA, so the group is those ships, not the world fleet. How this is calculated

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.

Detected from AIS AIS-detected

Time in port over the last 34 days, drawn by Voydar from the AIS-detected calls listed below. Each bar runs from arrival to departure; gaps are time away from a detected port or without reception.
PortArrivedDepartedTime in port
Saint Petersburg (ex Leningrad) RULEDOct 24, 2026, 13:58 UTCOct 24, 2026, 20:28 UTC6 h 30 min
Saint Petersburg (ex Leningrad) RULEDOct 23, 2026, 08:17 UTCOct 23, 2026, 14:57 UTC6 h 39 min
Saint Petersburg (ex Leningrad) RULEDOct 22, 2026, 15:45 UTCOct 22, 2026, 16:25 UTC39 min
Saint Petersburg (ex Leningrad) RULEDOct 22, 2026, 07:43 UTCOct 22, 2026, 15:30 UTC7 h 48 min
Saint Petersburg (ex Leningrad) RULEDOct 21, 2026, 15:45 UTCOct 21, 2026, 16:16 UTC31 min
Saint Petersburg (ex Leningrad) RULEDOct 21, 2026, 10:06 UTCOct 21, 2026, 15:17 UTC5 h 11 min
Saint Petersburg (ex Leningrad) RULEDOct 21, 2026, 06:10 UTCOct 21, 2026, 08:20 UTC2 h 9 min
Saint Petersburg (ex Leningrad) RULEDOct 20, 2026, 17:05 UTCOct 20, 2026, 22:08 UTC5 h 2 min
Saint Petersburg (ex Leningrad) RULEDOct 20, 2026, 15:54 UTCOct 20, 2026, 16:25 UTC31 min
Saint Petersburg (ex Leningrad) RULEDOct 20, 2026, 09:00 UTCOct 20, 2026, 15:23 UTC6 h 23 min
Saint Petersburg (ex Leningrad) RULEDOct 19, 2026, 08:13 UTCOct 19, 2026, 15:20 UTC7 h 7 min
Saint Petersburg (ex Leningrad) RULEDOct 19, 2026, 04:01 UTCOct 19, 2026, 08:10 UTC4 h 8 min

Detected by Voydar when the ship's AIS positions stayed slow inside a harbour area. Calls shorter than 30 minutes are not shown. Depends on AIS reception; detection started on June 8, 2026.

Reported by authorities Authority-reported

PortRecordDate (UTC)BerthSource
CANAVERAL HARBOR, FLDepartureFeb 14, 2016(date only)—USACE foreign traffic vessel entrances & clearances
CANAVERAL HARBOR, FLArrivalFeb 14, 2016(date only)—USACE foreign traffic vessel entrances & clearances
San Diego USSANDepartureAug 21, 2007(date only)—USACE foreign traffic vessel entrances & clearances
San Diego USSANArrivalAug 21, 2007(date only)—USACE foreign traffic vessel entrances & clearances
San Diego USSANDepartureJul 13, 2007(date only)—USACE foreign traffic vessel entrances & clearances
San Diego USSANArrivalJul 10, 2007(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: July 10, 2007.

Behaviour at sea Voydar-derived

Patterns Voydar derived from this ship's AIS broadcasts. They are inferences, not reports: each one shows how it was computed and how confident we are, and none of them says why a ship behaved this way.

WhenWhat we observedConfidence
Oct 25, 2026, 11:28 UTC
Draught change

Reported draught went from 8 m to 8.5 m after leaving Saint Petersburg (ex Leningrad). Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (55%)
Oct 25, 2026, 01:53 UTC
Draught change

Reported draught went from 9.7 m to 8 m after leaving Saint Petersburg (ex Leningrad). Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (55%)
Oct 21, 2026, 15:47 UTC
Two positions

This MMSI was reported in two places 69 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 21, 2026, 15:35 UTC
Two positions

This MMSI was reported in two places 67 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 21, 2026, 15:22 UTC
Two positions

This MMSI was reported in two places 69 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 21, 2026, 15:12 UTC
Two positions

This MMSI was reported in two places 68 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 20, 2026, 16:48 UTC
Two positions

This MMSI was reported in two places 67 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 20, 2026, 16:21 UTC
Two positions

This MMSI was reported in two places 67 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 20, 2026, 16:16 UTC
Two positions

This MMSI was reported in two places 69 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 20, 2026, 16:11 UTC
Two positions

This MMSI was reported in two places 68 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 20, 2026, 15:48 UTC
Two positions

This MMSI was reported in two places 68 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 20, 2026, 15:32 UTC
Two positions

This MMSI was reported in two places 67 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 20, 2026, 15:22 UTC
Two positions

This MMSI was reported in two places 67 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 20, 2026, 14:47 UTC
Two positions

This MMSI was reported in two places 69 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 20, 2026, 14:41 UTC
Two positions

This MMSI was reported in two places 67 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 20, 2026, 14:37 UTC
Two positions

This MMSI was reported in two places 69 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)

Source: Fintraffic / digitraffic.fi, license CC 4.0 BY. Licence: CC BY 4.0.

Derived from AIS positions of feeds whose terms allow display on Voydar. Coverage is terrestrial: gaps are reported only where our receivers kept hearing other ships. Detections below medium confidence are not shown.

How these are computed →

Frequently asked questions

What kind of ship is CS STRATOS?
CS STRATOS is a cargo ship sailing under the flag of Singapore, built in 2007 by Shikoku Dockyard. The vessel is 162.5 m long and has a gross tonnage of 14,030.
Who is recorded as the owner or manager of CS STRATOS?
BRIGHT STAR SHIP MANAGEMENT INC. is recorded as ISM manager for CS STRATOS (source: EU MRV (THETIS-MRV) emissions; reporting years 2024–2025). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for CS STRATOS?
Voydar has no matched sanctions record displayed for CS STRATOS 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 CS STRATOS. Missing records do not establish whether the ship has been detained.

Full Vessel Report

A dated PDF with the complete track since June 2026, every port call, ownership and flag changes, inspections, a sanctions and dark-activity screening snapshot, emissions, companies and every source.

See a sample report (PDF)

Sample: a real report for EVER GIVEN (IMO 9811000), built from public data and marked SAMPLE on every page.

Every fact on this page stays free.

Know this ship?

Help other readers. Member posts are shown as member content, never as sourced data.

  • Date, place and an optional note
  • Members who know her can answer
  • Suggest a correctionChecked against sources before anything changes

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/9350991
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

Cite this page

CS STRATOS. Voydar (voydar.com). https://www.voydar.com/vessel/9350991-cs-stratos. Retrieved November 21, 2026.

Each fact above names its own source and date. Cite that primary source too when you rely on a fact.

Using this data in code?

Every account gets a personal API allowance: 2,500 credits a month free, 25,000 with Pro. Pro includes use in your own product. Growth and Scale add volume, and each includes one Pro membership.

See plans

Sources and attribution

  • Data: AISHub contributors (AISHub Terms of Use (2026-10-08))
  • Wikidata (CC0 1.0)

Each fact above names its source and the date it was retrieved. Each source's licence applies to its data.

Compiled by Voydar from the sources named on this page.

Page: https://www.voydar.com/vessel/9350991-cs-stratos

Generated from voydar.com on Nov 21, 2026, 03:20 UTC