CSL Thames
Bulk carrier · Malta · built 2010 · AIS Class A
In short
CSL Thames (Bulk carrier, Malta flag) was last seen on AIS on , moored, in the North Sea. Its crew-entered AIS destination is NO JEL (Jelsa), with an ETA of Nov 16, 2026, 04:30 UTC; its reported draught is 6.4 m (voyage report via BarentsWatch AIS API, received Nov 16, 2026, 14:28 UTC). ISM manager: HULL 2227 SHIPPING LTD. (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
Current voyage: from Brevik (departed Nov 14, 2026, 14:14 UTC) to NO JEL (Jelsa)
- Vessel type
- Bulk carrier
- Flag
- Malta
- Year built
- 2010
- Gross tonnage
- 19,711
- Size (length × beam)
- 175 m × 26 m
- ISM manager
- HULL 2227 SHIPPING LTD.

Last reported position: 59.3779° N, 6.0472° E · North Sea · See on the map
Watch this ship
Get an email when CSL Thames reaches Jelsa, and when it 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 16, 2026, 14:57 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for CSL Thames 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: Voydar for iPhone
Last reported position
received- Position
- 59.3779° N, 6.0472° E
- Area
- North Sea
- Status
- MooredWhat do AIS statuses mean?
- Speed
- 0 kn
- Course
- 39°
- Heading
- 223°
- Compass: course over ground 39°, heading 223°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 10 port calls (Brevik, Verdal, Bremen, Jelsa, Wilhelmshaven, IJmuiden/Velsen, and Amsterdam).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Data delivered by BarentsWatch
Pro shows CSL Thames's track before the last 30 days. Voydar has recorded its port calls since October 11, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
Length overall 175 mone tick every 25 m
Beam 26 mPlan outline, to scale
- Name
- CSL Thames
- IMO numberWhat is an IMO number?
- 9440447
- MMSIWhat is an MMSI?
- 249605000
- Call signWhat is a call sign?
- 9HVS9
- Flag
- Malta
- Vessel type
- Detailed type from WikidataBulk carrier
- Gross tonnageGross tonnage vs deadweight
- 19,711
- Deadweight (DWT)
- Source: Wikidata, record Q83631031. Added to Voydar on October 23, 2026. Licence: CC0 1.0.30,000 t
- Length overall
- 175 m
- Beam
- 26 m
- Year built
- 2010
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 · 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.
| Date | Event | Source |
|---|---|---|
| Left BrevikAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at BrevikAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left VerdalAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at VerdalAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left BremenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at BremenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from SeattleAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Inspection at WASHINGTON, District of Columbia | USCG PSIX / CGMIX inspections | |
| Reported arrival at SeattleAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Inspection at Seattle, Washington | USCG PSIX / CGMIX inspections | |
| Reported departure from SeattleAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Inspection at Seattle, Washington | USCG PSIX / CGMIX inspections | |
| Inspection at Seattle, Washington | USCG PSIX / CGMIX inspections | |
| Inspection at Seattle, Washington | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at Seattle, Washington | USCG PSIX / CGMIX inspections | |
| Inspection at Seattle, Washington | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at BOSTON, Massachusetts | USCG PSIX / CGMIX inspections |
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 Aug 9, 2011merchant-vessel-100-gross-tons-or-overUK MAIB investigation reports (index)Sound of Mull, Scotland
Grounding of bulk carrier CSL ThamesReport published Feb 29, 2016
Location: Sound of Mull, Scotland.
Source: UK MAIB investigation reports (index). Contains public sector information licensed under the Open Government Licence v3.0. Licence: Open Government Licence v3.0.
Safety & inspections
| Date | Type | Port | Findings |
|---|---|---|---|
| Jun 29, 2016 | Incident Investigation | WASHINGTON, District of Columbia | clean |
| Jun 11, 2016 | Vessel Operational Control | Seattle, Washington | clean |
| Feb 8, 2016 | Vessel Inspection | Seattle, Washington | clean |
| Feb 7, 2016 | Boarding | Seattle, Washington | clean |
| Jan 12, 2016 | Boarding | Seattle, Washington | clean |
| May 23, 2015 | Vessel InspectionPSC | Seattle, Washington | clean |
| Mar 10, 2015 | Vessel Inspection | Seattle, Washington | clean |
| Feb 1, 2015 | Vessel InspectionPSC | BOSTON, Massachusetts | clean |
Source: U.S. Coast Guard Port State Information Exchange (PSIX) — public domain. Covers inspections recorded in U.S. waters. Free on Voydar; the incumbents charge for this.
Emissions & fuel consumption
Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.
| Year | CO₂ emitted | Fuel burned | Time at sea | CO₂ / n mile |
|---|---|---|---|---|
| 2018 | 11,710 t | 3,666 t | 144 days | 296 kg |
| 2019 | 15,514 t | 4,839 t | 226 days | 270 kg |
| 2021 | 1,041 t | 328 t | 18 days | 239 kg |
| 2022 | 7,914 t | 2,509 t | 94 days | 329 kg |
| 2023 | 12,757 t | 4,017 t | 126 days | 383 kg |
| 2024 | 12,892 t | 4,022 t | 191 days | 279 kg |
| 2025 | 13,292 t | 4,193 t | 226 days | 255 kg |
Technical efficiency: EEDI (5.65 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 “Bulk carrier”. Lower is less CO₂.
- CO₂ per tonne of cargo carried one nautical mile18.97 g per tonne-nautical mile
- Lowest reportedHighest reported
92% of the 3,661 ships in this group reported a lower figure.
Group: lower quartile 6.06 · median 7.94 · upper quartile 10.76
- CO₂ per nautical mile sailed255.5 kg per nautical mile
- Lowest reportedHighest reported
47% of the 3,811 ships in this group reported a lower figure.
Group: lower quartile 222.1 · median 261.2 · upper quartile 303.2
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
| Port | Arrived | Departed | Time in port |
|---|---|---|---|
| Brevik NOBVK | Nov 12, 2026, 19:27 UTC | Nov 14, 2026, 14:14 UTC | 42 h 46 min |
| Verdal NOVER | Nov 7, 2026, 07:31 UTC | Nov 8, 2026, 08:18 UTC | 24 h 47 min |
| Bremen DEBRE | Nov 3, 2026, 06:55 UTC | Nov 4, 2026, 08:43 UTC | 25 h 48 min |
| Jelsa NOJEL | Oct 31, 2026, 09:49 UTC | Nov 1, 2026, 06:28 UTC | 20 h 39 min |
| Wilhelmshaven DEWVN | Oct 28, 2026, 13:30 UTC | Oct 29, 2026, 15:14 UTC | 25 h 44 min |
| Jelsa NOJEL | Oct 24, 2026, 15:03 UTC | Oct 26, 2026, 06:10 UTC | 39 h 6 min |
| IJmuiden/Velsen NLIJM | Oct 23, 2026, 01:05 UTC | Oct 23, 2026, 02:09 UTC | 1 h 4 min |
| Amsterdam NLAMS | Oct 21, 2026, 15:21 UTC | Oct 23, 2026, 00:12 UTC | 32 h 51 min |
| IJmuiden/Velsen NLIJM | Oct 21, 2026, 13:07 UTC | Oct 21, 2026, 14:03 UTC | 56 min |
| Jelsa NOJEL | Oct 18, 2026, 15:44 UTC | Oct 19, 2026, 15:18 UTC | 23 h 34 min |
| Brevik NOBVK | Oct 16, 2026, 02:26 UTC | Oct 17, 2026, 17:29 UTC | 39 h 3 min |
| Verdal NOVER | Oct 11, 2026, 10:50 UTC | Oct 12, 2026, 12:20 UTC | 25 h 31 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
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Seattle USSEA | Departure | Aug 24, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Arrival | Jun 15, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Departure | May 18, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Departure | May 15, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Arrival | May 11, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Oakland USOAK | Departure | Apr 19, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| SAN JOAQUIN RIVER, CA (INCLUDING COMMERCE OF PORT OF STOCKTON, CA) | Arrival | Apr 18, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Departure | Apr 1, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Arrival | Mar 31, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Departure | Mar 24, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Arrival | Mar 23, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Departure | Mar 9, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: February 1, 2015.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
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.
| When | What we observed | Confidence |
|---|---|---|
| Nov 14, 2026, 01:29 UTC | Draught change Reported draught went from 10 m to 6.5 m while in port at Brevik. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Nov 8, 2026, 02:58 UTC | Draught change Reported draught went from 6.5 m to 10 m while in port at Verdal. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Nov 4, 2026, 03:08 UTC | Draught change Reported draught went from 9.9 m to 6.5 m while in port at Bremen. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Oct 22, 2026, 19:55 UTC | Draught change Reported draught went from 10.6 m to 6.5 m while in port at Amsterdam. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Oct 19, 2026, 01:06 UTC | Draught change Reported draught went from 6.5 m to 10.4 m while in port at Jelsa. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Oct 16, 2026, 11:39 UTC | Draught change Reported draught went from 10 m to 6.5 m while in port at Brevik. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Oct 12, 2026, 11:45 UTC | Draught change Reported draught went from 6.5 m to 10 m while in port at Verdal. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Sep 25, 2026, 15:29 UTC | Draught change Reported draught went from 10.5 m to 6.3 m while in port at Bremen. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
Source: BarentsWatch AIS API. Data delivered by BarentsWatch (NLOD 2.0; data owner: Kystverket). Licence: NLOD 2.0 (BarentsWatch API terms 2023-11-02; Live/Historic AIS OpenAPI licence NLOD).
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.
Frequently asked questions
- What kind of ship is CSL Thames?
- CSL Thames is a bulk carrier sailing under the flag of Malta, built in 2010 by Yantai Raffles Shipyard. The vessel is 175 m long with a beam of 26 m and has a gross tonnage of 19,711.
- Who is recorded as the owner or manager of CSL Thames?
- HULL 2227 SHIPPING LTD. is recorded as ISM manager for CSL Thames (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 CSL Thames?
- Voydar has no matched sanctions record displayed for CSL Thames 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. CSL Thames has 8 recorded Port State Control inspections. Detention and deficiency detail is not recorded for these inspections.
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.
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
More Bulk carriers
Other bulk carriers with full Voydar profiles. A different set each day. All bulk carriers
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/9440447Cite this page
CSL Thames. Voydar (voydar.com). https://www.voydar.com/vessel/9440447-csl-thames. Retrieved November 16, 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 adds internal business use; API plans add building the data into your own products.