Skip to content

CT Rotterdam

Container ship · Cyprus · built 2009 · AIS Class A

IMO9395575MMSI209836000Call sign5BSX2Last AIS position Oct 3, 2026, 23:52 UTC

In short

CT Rotterdam (Container ship, Cyprus flag) was last seen on AIS on , under way at 13.7 kn, near Mevagissey (English Channel). Its crew-entered AIS destination is NLRTM (Rotterdam), with an ETA of Oct 5, 2026, 02:00 UTC; its reported draught is 6.5 m (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 10:04 UTC). Its last detected port call was at Rotterdam: arrived Sep 28, 2026, left Sep 30, 2026. ISM manager: Contarga Ltd. (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Vessel type
Container ship
Flag
Cyprus
Year built
2009
Gross tonnage
8,273
Size (length × beam)
140 m × 22 m
ISM manager
Contarga Ltd.

Watch this ship

Get an email when CT Rotterdam 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 CT Rotterdam.

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
50.0871° N, 4.6503° W
Area
English Channel
StatusWhat do AIS statuses mean?
Under way using engine
Speed
13.7 kn
Course
30°
Heading
30°
50.0871° N, 4.6503° W
Open the full live map →

Last 30 days: 1 port call (Rotterdam).

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
CT Rotterdam
IMO numberWhat is an IMO number?
9395575
MMSIWhat is an MMSI?
209836000
Call signWhat is a call sign?
5BSX2
Flag
Cyprus
Vessel type
Container ship
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
8,273
Length overall
139.6 m
Beam
22.2 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
Left RotterdamAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at RotterdamAIS-detectedVoydar port-call detector (AIS geofence)

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
201812,852 t4,094 t115 days349 kg
201910,991 t3,476 t204 days303 kg
202015,714 t4,983 t226 days253 kg
202116,626 t5,313 t190 days262 kg
202214,950 t4,781 t185 days253 kg
202317,795 t5,689 t192 days264 kg
202416,207 t5,181 t188 days258 kg
202516,087 t5,141 t185 days264 kg

Technical efficiency: EEXI (25.1 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.

Detected from AIS AIS-detected

PortArrivedDepartedTime in port
Rotterdam NLRTMSep 28, 2026, 11:47 UTCSep 30, 2026, 02:41 UTC38 h 53 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.

Frequently asked questions

Where is CT Rotterdam now?
CT Rotterdam (Container ship, Cyprus flag) was last seen on AIS on Oct 3, 2026, 23:52 UTC, under way at 13.7 kn, near Mevagissey (English Channel). The crew-entered destination was NLRTM (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 10:04 UTC). This report does not confirm the ship’s current route.
What kind of ship is CT Rotterdam?
CT Rotterdam is a container ship sailing under the flag of Cyprus, built in 2009 by Rolandwerft. The vessel is 139.6 m long with a beam of 22.2 m and has a gross tonnage of 8,273.
Who is recorded as the owner or manager of CT Rotterdam?
Contarga Ltd. is recorded as ISM manager for CT Rotterdam (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 CT Rotterdam?
Voydar has no matched sanctions record displayed for CT Rotterdam 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 CT Rotterdam. 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/9395575
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