Skip to content

Elbstrom

Container ship · Portugal · built 2008 · AIS Class A

IMO9369007MMSI255805577Call signCQHBLast AIS position Oct 2, 2026, 13:08 UTC

In short

Elbstrom (Container ship, Portugal flag) was last seen on AIS on , under way at 9.6 kn, in the Baltic Sea. 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 LTKLJ (Klaipeda); its reported draught is 7 m (voyage report via Digitraffic marine AIS, received Oct 2, 2026, 13:01 UTC). ISM manager: MS "ELBSURFER" GmbH & Co, KG (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Current voyage: from Vuosaari (Nordsjo) (departed Sep 29, 2026, 17:00 UTC) to LTKLJ (Klaipeda)

Vessel type
Container ship
Year built
2008
Gross tonnage
8,273
Size (length × beam)
140 m × 22 m

Watch this ship

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

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.

Photo of ELBSTROM
Photo: Niels Johannes · Licence: CC BY-SA 4.0 · via Wikimedia Commons

Last reported position

received
Position
55.8703° N, 20.7612° E
Area
Baltic Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
9.6 kn
Course
146°
Heading
146°
55.8703° N, 20.7612° E
Open the full live map →

Last 30 days: 5 port calls (Vuosaari (Nordsjo), Kiel, Rotterdam, Salt End, and Kiel Canal).

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
Elbstrom
IMO numberWhat is an IMO number?
9369007
MMSIWhat is an MMSI?
255805577
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
8,273
Length overall
139.6 m
Beam
22.2 m
Year built
2008

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 Vuosaari (Nordsjo)AIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Vuosaari (Nordsjo)AIS-detectedVoydar port-call detector (AIS geofence)
Left KielAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at KielAIS-detectedVoydar port-call detector (AIS geofence)
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
201913,222 t4,173 t187 days270 kg
202012,841 t4,038 t158 days280 kg
20217,181 t2,251 t98 days268 kg
202214,122 t4,525 t215 days238 kg
202313,621 t4,361 t191 days232 kg
202413,533 t4,271 t216 days214 kg
202514,652 t4,699 t251 days195 kg

Technical efficiency: EEXI (25 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
Vuosaari (Nordsjo) FIVSSSep 29, 2026, 02:42 UTCSep 29, 2026, 17:00 UTC14 h 17 min
Kiel DEKELSep 27, 2026, 02:08 UTCSep 27, 2026, 03:09 UTC1 h 1 min
Rotterdam NLRTMSep 24, 2026, 04:08 UTCSep 25, 2026, 12:07 UTC31 h 58 min
Salt End GBSEDSep 22, 2026, 01:59 UTCSep 22, 2026, 21:51 UTC19 h 52 min
Kiel Canal DECKLSep 20, 2026, 08:34 UTCSep 22, 2026, 01:43 UTC41 h 9 min
Salt End GBSEDJun 16, 2026, 03:20 UTCJun 19, 2026, 08:05 UTC3 d 4 h

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.

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 29, 2026, 23:06 UTC
Draught change

Reported draught went from 5 m to 5.8 m after leaving Vuosaari (Nordsjo). Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (55%)
Sep 25, 2026, 11:25 UTC
Draught change

Reported draught went from 5.9 m to 6.7 m while in port at Rotterdam. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Sep 23, 2026, 17:16 UTC
Draught change

Reported draught went from 7.3 m to 5.9 m after leaving Salt End. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (55%)

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

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 Elbstrom now?
Elbstrom (Container ship, Portugal flag) was last seen on AIS on Oct 2, 2026, 13:08 UTC, under way at 9.6 kn, in the Baltic Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was LTKLJ (voyage report via Digitraffic marine AIS, received Oct 2, 2026, 13:01 UTC). This report does not confirm the ship’s current route.
What kind of ship is Elbstrom?
Elbstrom is a container ship sailing under the flag of Portugal, built in 2008 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 Elbstrom?
MS "ELBSURFER" GmbH & Co, KG is recorded as ISM manager for Elbstrom (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 Elbstrom?
Voydar has no matched sanctions record displayed for Elbstrom 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 Elbstrom. 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/9369007
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