SKS Mosel
Bulk carrier · built 2003
In short
SKS Mosel (Bulk carrier) has no AIS position on record with Seadar.
- Vessel type
- Bulk carrier
- Flag
- —
- Year built
- 2003
- Gross tonnage
- 70,933
- Size (length × beam)
- 250 m
- Registered owner
- —
Watch this ship
Get an email when SKS Mosel 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 SKS Mosel.
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
No AIS position on record for this vessel. Identity and particulars are below.
A year of history in the Terminal (Plus) · the full archive since June 1, 2026 (Pro)
Try the live demo, no sign-upIdentity & particulars
- Name
- SKS Mosel
- IMO numberWhat is an IMO number?
- 9240433
- MMSIWhat is an MMSI?
- —
- Call signWhat is a call sign?
- —
- Flag
- —
- Gross tonnageGross tonnage vs deadweight
- 70,933
- Length overall
- 250 m
- Beam
- —
- Year built
- 2003
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.
- Builder
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
Timeline
Dated events for this ship from every source Seadar holds, newest first. Each line names its source; derived items say how they were derived.
| Date | Event | Source |
|---|---|---|
| Reported departure from ELIZABETH RIVER, VAAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at CHESAPEAKE BAY, MD AND VAAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from MobileAuthority-reported | USACE 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.
| Year | CO₂ emitted | Fuel burned | Time at sea | CO₂ / n mile |
|---|---|---|---|---|
| 2018 | 19,456 t | 6,217 t | 308 days | 437 kg |
| 2019 | 13,299 t | 4,251 t | 203 days | 428 kg |
| 2020 | 9,452 t | 2,979 t | 87 days | 564 kg |
Technical efficiency: EIV (3.59 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 Seadar detected from the ship's AIS positions, and arrivals and departures published by port authorities and customs records.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| ELIZABETH RIVER, VA | Departure | Oct 28, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| CHESAPEAKE BAY, MD AND VA | Arrival | Oct 19, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Mobile USMOB | Departure | Jan 22, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Mobile USMOB | Arrival | Jan 20, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Jan 10, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Jan 9, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New York USNYC | Departure | Nov 15, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New York USNYC | Arrival | Oct 23, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Mobile USMOB | Departure | May 4, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Mobile USMOB | Arrival | May 2, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Apr 28, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Apr 28, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: August 3, 2003.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
Frequently asked questions
- Where is SKS Mosel now?
- Seadar has no displayable AIS position for SKS Mosel in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
- What kind of ship is SKS Mosel?
- SKS Mosel is a bulk carrier, built in 2003 by HD Hyundai Heavy Industries. The vessel is 250 m long and has a gross tonnage of 70,933.
- What sanctions and inspection records does Seadar hold for SKS Mosel?
- Seadar has no matched sanctions record displayed for SKS Mosel from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels and the New Zealand Russia Sanctions Register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for SKS Mosel. 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/9240433Using 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.