Skip to content

STENA EBBA

Ferry · Denmark · built 2022 · AIS Class A

IMO9863003MMSI219031310Call signOZXE2Last AIS position Oct 3, 2026, 10:31 UTC

In short

STENA EBBA (Ferry, Denmark flag) was last seen on AIS on , moored, in the port of Gdynia. Its crew-entered AIS destination is SEKAA->PLGDY->SEKAA, with an ETA of Oct 3, 2026, 06:10 UTC; its reported draught is 5.9 m (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 10:25 UTC). It arrived there on Oct 3, 2026, 06:36 UTC. ISM manager: Stena Rederi AS (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Vessel type
Ferry
Year built
2022
Gross tonnage
48,035
Size (length × beam)
240 m × 28 m
ISM manager
Stena Rederi AS

Watch this ship

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

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 STENA EBBA
Photo: Zalasem1 · Licence: CC BY 4.0 · via Wikimedia Commons

Last reported position

received
Position
54.5336° N, 18.5438° E
Area
Baltic Sea
Speed
0 kn
Course
322°
Heading
57°
54.5336° N, 18.5438° E
Open the full live map →

Last 30 days: at least 12 port calls (Gdynia and Karlskrona).

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
STENA EBBA
IMO numberWhat is an IMO number?
9863003
MMSIWhat is an MMSI?
219031310
Call signWhat is a call sign?
OZXE2
AIS ship type
Passenger (hazardous cat. A)
Gross tonnageGross tonnage vs deadweight
48,035
Length overall
239.7 m
Beam
27.8 m
Year built
2022

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.

Operator
Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
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
Reported arrival at GdyniaAuthority-reportedUrząd Morski w Gdyni: ships in port, expected and departing (Gdynia, Gdańsk)
Arrived at GdyniaAIS-detectedVoydar port-call detector (AIS geofence)
Left KarlskronaAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at KarlskronaAIS-detectedVoydar port-call detector (AIS geofence)
Left GdyniaAIS-detectedVoydar port-call detector (AIS geofence)
Reported arrival at GdyniaAuthority-reportedUrząd Morski w Gdyni: ships in port, expected and departing (Gdynia, Gdańsk)
Arrived at GdyniaAIS-detectedVoydar port-call detector (AIS geofence)
Reported arrival at GdyniaAuthority-reportedUrząd Morski w Gdyni: ships in port, expected and departing (Gdynia, Gdańsk)

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
2022817 t257 t5 days613 kg
202346,040 t14,602 t241 days490 kg
202447,109 t14,937 t255 days489 kg
202544,608 t14,264 t257 days460 kg

Technical efficiency: EEXI (17.08 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
Gdynia PLGDYOct 3, 2026, 06:36 UTCin port—
Karlskrona SEKAAOct 2, 2026, 18:29 UTCOct 2, 2026, 20:40 UTC2 h 12 min
Gdynia PLGDYOct 2, 2026, 04:19 UTCOct 2, 2026, 06:44 UTC2 h 25 min
Karlskrona SEKAAOct 1, 2026, 15:45 UTCOct 1, 2026, 18:18 UTC2 h 32 min
Gdynia PLGDYOct 1, 2026, 03:52 UTCOct 1, 2026, 06:31 UTC2 h 39 min
Karlskrona SEKAASep 30, 2026, 15:42 UTCSep 30, 2026, 18:15 UTC2 h 33 min
Gdynia PLGDYSep 30, 2026, 03:53 UTCSep 30, 2026, 06:25 UTC2 h 32 min
Karlskrona SEKAASep 29, 2026, 15:42 UTCSep 29, 2026, 18:14 UTC2 h 32 min
Karlskrona SEKAASep 28, 2026, 04:58 UTCSep 28, 2026, 06:08 UTC1 h 9 min
Karlskrona SEKAASep 26, 2026, 17:03 UTCSep 26, 2026, 19:12 UTC2 h 9 min
Gdynia PLGDYSep 26, 2026, 04:00 UTCSep 26, 2026, 06:37 UTC2 h 37 min
Karlskrona SEKAASep 25, 2026, 06:35 UTCSep 25, 2026, 18:13 UTC11 h 39 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

PortRecordDate (UTC)BerthSource
Gdynia PLGDYArrivalOct 3, 2026, 06:52 UTCPolskieUrząd Morski w Gdyni: ships in port, expected and departing (Gdynia, Gdańsk)
Gdynia PLGDYArrivalOct 2, 2026, 04:30 UTCPolskieUrząd Morski w Gdyni: ships in port, expected and departing (Gdynia, Gdańsk)
Gdynia PLGDYArrivalOct 1, 2026, 04:40 UTCPolskieUrząd Morski w Gdyni: ships in port, expected and departing (Gdynia, Gdańsk)
Gdynia PLGDYArrivalSep 30, 2026, 04:09 UTCPolskieUrząd Morski w Gdyni: ships in port, expected and departing (Gdynia, Gdańsk)
Gdynia PLGDYArrivalSep 29, 2026, 04:05 UTCPolskieUrząd Morski w Gdyni: ships in port, expected and departing (Gdynia, Gdańsk)
Gdynia PLGDYArrivalSep 27, 2026, 06:50 UTCPolskieUrząd Morski w Gdyni: ships in port, expected and departing (Gdynia, Gdańsk)
Gdynia PLGDYArrivalSep 26, 2026, 04:07 UTCPolskieUrząd Morski w Gdyni: ships in port, expected and departing (Gdynia, Gdańsk)
Gdynia PLGDYArrivalSep 24, 2026, 15:45 UTCPolskieUrząd Morski w Gdyni: ships in port, expected and departing (Gdynia, Gdańsk)

Records published by the authority named on each row. Earliest record for this ship: September 24, 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
Oct 2, 2026, 06:17 UTC
Draught change

Reported draught went from 6.3 m to 5.3 m while in port at Gdynia. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Sep 30, 2026, 18:19 UTC
Draught change

Reported draught went from 5.6 m to 6.2 m after leaving Karlskrona. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (55%)
Sep 30, 2026, 05:59 UTC
Draught change

Reported draught went from 6.2 m to 5.6 m while in port at Gdynia. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Sep 29, 2026, 17:46 UTC
Draught change

Reported draught went from 5.7 m to 6.2 m while in port at Karlskrona. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Sep 25, 2026, 18:13 UTC
Draught change

Reported draught went from 5.7 m to 6.4 m while in port at Karlskrona. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)

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 STENA EBBA now?
STENA EBBA (Ferry, Denmark flag) was last seen on AIS on Oct 3, 2026, 10:31 UTC, moored, in the port of Gdynia. The crew-entered destination was SEKAA->PLGDY->SEKAA (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 10:25 UTC). This report does not confirm the ship’s current route.
What kind of ship is STENA EBBA?
STENA EBBA is a ferry sailing under the flag of Denmark, built in 2022 by China Merchants Jinling Shipyard (Weihai). The vessel is 239.7 m long with a beam of 27.8 m and has a gross tonnage of 48,035.
Who is recorded as the owner or manager of STENA EBBA?
Stena Rederi AS is recorded as ISM manager for STENA EBBA (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 STENA EBBA?
Voydar has no matched sanctions record displayed for STENA EBBA 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 STENA EBBA. 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/9863003
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