Skip to content

ELBWAVE

Container ship · Cyprus · built 2011 · AIS Class A

IMO9504035MMSI209276000Call sign5BZP4Last AIS position Oct 2, 2026, 09:46 UTC

In short

ELBWAVE (Container ship, Cyprus flag) was last seen on AIS on , moored, in the port of Europoort. Its crew-entered AIS destination is NLRTM (Rotterdam); its reported draught is 6.6 m (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 09:29 UTC). It arrived there on Oct 1, 2026, 21:32 UTC. ISM manager: MS "Elbwave" GmbH & Co. KG (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Vessel type
Container ship
Flag
Cyprus
Year built
2011
Gross tonnage
10,585
Size (length × beam)
152 m × 24 m

Watch this ship

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

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 IMO 9504035
Photo: Wolfgang Fricke · Licence: CC BY 3.0 · via Wikimedia Commons

Last reported position

received
Position
51.9641° N, 4.0547° E
Area
North Sea
Speed
0 kn
Course
111°
Heading
111°
51.9641° N, 4.0547° E
Open the full live map →

Last 30 days: at least 12 port calls (Europoort, Rotterdam, Hamburg, Achterwehr, Kiel, Muuga, Oti, Kiel Canal, and Poortugaal).

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
ELBWAVE
IMO numberWhat is an IMO number?
9504035
MMSIWhat is an MMSI?
209276000
Call signWhat is a call sign?
5BZP4
Flag
Cyprus
Vessel type
Container ship
AIS ship type
Cargo (hazardous cat. A)
Gross tonnageGross tonnage vs deadweight
10,585
Length overall
151.7 m
Beam
23.8 m
Year built
2011

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

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
Arrived at EuropoortAIS-detectedVoydar port-call detector (AIS geofence)
Left RotterdamAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at RotterdamAIS-detectedVoydar port-call detector (AIS geofence)
Left HamburgAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at HamburgAIS-detectedVoydar port-call detector (AIS geofence)
Former name: Amisia JWikidata
Former name: Wes CarinaWikidata

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.

Former and other names

Names attested for this ship other than its current name.

NameEvidenceDateSource
Amisia JFormer nameJan 1, 2011Wikidata
Wes CarinaFormer nameJan 1, 2011Wikidata

A sanctions list's date is the earliest date the list shows the name, not when the ship took it. A name on a list is shown as a former name only where AIS shows the ship using another name after that date; otherwise it is listed as a name the list uses. AIS name changes are dated when Voydar saw them.

Source: Wikidata. Licence: CC0 1.0.

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
201815,049 t4,740 t237 days282 kg
201918,099 t5,732 t213 days273 kg
202016,967 t5,369 t205 days270 kg
202116,586 t5,276 t194 days268 kg
202213,959 t4,467 t178 days257 kg
202314,209 t4,503 t191 days260 kg
202414,199 t4,464 t199 days251 kg
202514,214 t4,491 t197 days248 kg

Technical efficiency: EEXI (22.48 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
Europoort NLEUROct 1, 2026, 21:32 UTCin port—
Rotterdam NLRTMSep 29, 2026, 21:08 UTCSep 30, 2026, 04:59 UTC7 h 51 min
Hamburg DEHAMSep 27, 2026, 19:49 UTCSep 28, 2026, 18:45 UTC22 h 56 min
Achterwehr DEAWRSep 27, 2026, 04:41 UTCSep 27, 2026, 05:47 UTC1 h 5 min
Kiel DEKELSep 27, 2026, 02:36 UTCSep 27, 2026, 04:01 UTC1 h 25 min
Muuga EEMUGSep 22, 2026, 17:16 UTCSep 23, 2026, 12:36 UTC19 h 20 min
Oti EEOTISep 22, 2026, 12:08 UTCSep 22, 2026, 15:43 UTC3 h 35 min
Kiel Canal DECKLSep 19, 2026, 09:05 UTCSep 19, 2026, 10:03 UTC58 min
Poortugaal NLPTGSep 18, 2026, 08:59 UTCSep 18, 2026, 09:34 UTC35 min
Poortugaal NLPTGSep 18, 2026, 01:31 UTCSep 18, 2026, 08:54 UTC7 h 23 min
Poortugaal NLPTGSep 17, 2026, 20:46 UTCSep 18, 2026, 01:15 UTC4 h 29 min
Poortugaal NLPTGSep 15, 2026, 08:00 UTCSep 15, 2026, 13:45 UTC5 h 45 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.

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 28, 2026, 09:13 UTC
Draught change

Reported draught went from 7.8 m to 6.9 m while in port at Hamburg. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)

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 ELBWAVE now?
ELBWAVE (Container ship, Cyprus flag) was last seen on AIS on Oct 2, 2026, 09:46 UTC, moored, in the port of Europoort. The crew-entered destination was NLRTM (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 09:29 UTC). This report does not confirm the ship’s current route.
What kind of ship is ELBWAVE?
ELBWAVE is a container ship sailing under the flag of Cyprus, built in 2011. The vessel is 151.7 m long with a beam of 23.8 m and has a gross tonnage of 10,585.
Who is recorded as the owner or manager of ELBWAVE?
MS "Elbwave" GmbH & Co. KG is recorded as ISM manager for ELBWAVE (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 ELBWAVE?
Voydar has no matched sanctions record displayed for ELBWAVE 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 ELBWAVE. 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/9504035
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