Skip to content

CS STANDARD

Cargo ship · Singapore · built 2009 · AIS Class A

IMO9438509MMSI566041000Call sign9V9354Last AIS position Sep 26, 2026, 06:07 UTC

In short

CS STANDARD (Cargo ship, Singapore flag) was last seen on AIS on , under way at 19.7 kn, in the North Atlantic Ocean. 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 CIABJ (Abidjan); its reported draught is 9.4 m (voyage report via AISstream.io global terrestrial AIS, received Sep 26, 2026, 06:03 UTC). ISM manager: BRIGHT STAR SHIP MANAGEMENT INC. (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025). It can carry up to 436 passengers (source: Wikidata).

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

Watch this ship

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

We email you a link and a code. That creates a free account, no password or card, and follows CS STANDARD.

Free account, no card: follow up to 5 ships and ports. Plus follows 50, Pro 500.

By continuing you accept the Terms and the Privacy policy.

Last reported position

received
Position
23.4218° N, 16.8756° W
Area
North Atlantic Ocean
StatusWhat do AIS statuses mean?
Under way using engine
Speed
19.7 kn
Course
199°
Heading
196°
23.4218° N, 16.8756° W
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)

Try the live demo, no sign-up

Identity & particulars

Name
CS STANDARD
IMO numberWhat is an IMO number?
9438509
MMSIWhat is an MMSI?
566041000
Call signWhat is a call sign?
9V9354
Vessel type
Cargo ship
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
14,030
Length overall
162.5 m
Beam
26 m
Year built
2009

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 years 2024–2025 · reported · confidence 0.9 · retrieved Sep 28, 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 San JuanAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at San JuanAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from San JuanAuthority-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.

YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
20195,331 t1,692 t37 days356 kg
202015,989 t5,062 t120 days332 kg
20223,091 t990 t22 days397 kg
20233,334 t1,070 t18 days458 kg
2024624 t199 t4 days410 kg
20257,860 t2,513 t43 days464 kg

Technical efficiency: EIV (26.89 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
San Juan PRSJUDepartureDec 18, 2009(date only)—USACE foreign traffic vessel entrances & clearances
San Juan PRSJUArrivalDec 18, 2009(date only)—USACE foreign traffic vessel entrances & clearances
San Juan PRSJUDepartureDec 10, 2009(date only)—USACE foreign traffic vessel entrances & clearances
San Juan PRSJUArrivalDec 10, 2009(date only)—USACE foreign traffic vessel entrances & clearances
San Juan PRSJUDepartureNov 21, 2009(date only)—USACE foreign traffic vessel entrances & clearances
San Juan PRSJUArrivalNov 21, 2009(date only)—USACE foreign traffic vessel entrances & clearances
San Juan PRSJUDepartureNov 12, 2009(date only)—USACE foreign traffic vessel entrances & clearances
San Juan PRSJUArrivalNov 12, 2009(date only)—USACE foreign traffic vessel entrances & clearances
San Juan PRSJUDepartureOct 25, 2009(date only)—USACE foreign traffic vessel entrances & clearances
San Juan PRSJUArrivalOct 25, 2009(date only)—USACE foreign traffic vessel entrances & clearances
San Juan PRSJUDepartureOct 15, 2009(date only)—USACE foreign traffic vessel entrances & clearances
San Juan PRSJUArrivalOct 14, 2009(date only)—USACE foreign traffic vessel entrances & clearances

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

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
Sep 23, 2026, 09:07 UTC
Position jump

Reported position moved 61 km in 31 min, faster than any ship can travel. The broadcast position was wrong for a time; GNSS interference, equipment faults and manipulation are all possible causes.

Method seadar.behaviour.position_jump v1

Medium (50%)

Source: AISstream.io global terrestrial AIS. AIS data: AISstream.io. Licence: none published.

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

Where is CS STANDARD now?
CS STANDARD (Cargo ship, Singapore flag) was last seen on AIS on Sep 26, 2026, 06:07 UTC, under way at 19.7 kn, in the North Atlantic Ocean. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was CIABJ (voyage report via AISstream.io global terrestrial AIS, received Sep 26, 2026, 06:03 UTC). This report does not confirm the ship’s current route.
What kind of ship is CS STANDARD?
CS STANDARD is a cargo ship sailing under the flag of Singapore, built in 2009 by Shikoku Dockyard. The vessel is 162.5 m long with a beam of 26 m and has a gross tonnage of 14,030.
Who is recorded as the owner or manager of CS STANDARD?
BRIGHT STAR SHIP MANAGEMENT INC. is recorded as ISM manager for CS STANDARD (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 STANDARD?
Voydar has no matched sanctions record displayed for CS STANDARD 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 STANDARD. 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/9438509
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