Skip to content
voydar.com

BALTIC ENABLER

Ro-ro ship · Sweden · AIS Class A

IMO9884681MMSI265039000Call signSBTPLast AIS position Nov 19, 2026, 17:57 UTC

In short

BALTIC ENABLER (Ro-ro ship, Sweden flag) was last seen on AIS on , under way at 2.5 kn, in the port of Kallo. Its crew-entered AIS destination is BEANR (Antwerpen), with an ETA of Nov 19, 2026, 04:00 UTC; its reported draught is 7.3 m (voyage report via AISstream.io global terrestrial AIS, received Nov 19, 2026, 17:29 UTC). It arrived there on Nov 19, 2026, 02:05 UTC. ISM manager: Wallenius Marine (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Data: AISHub contributors

Vessel type
Ro-ro ship
Flag
Sweden
Year built
—
Gross tonnage
—
Size, AIS-reported (length × beam)
242 m × 36 m
ISM manager
Wallenius Marine

Last reported position: 51.2542° N, 4.2329° E · North Sea · See on the map

Shipping a car on this vessel?

Follow BALTIC ENABLER and Voydar's daily email tells you when it has reached Antwerpen, and when it leaves or changes its destination.

What you would have been told

Following BALTIC ENABLER over the last 24 hours would have sent 2 messages.

  • ArrivedKallo
  • LeftZeebrugge

Detected from AIS, as of Nov 19, 2026, 17:59 UTC.

Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for BALTIC ENABLER 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: the Voydar app

Last reported position

received
Position
51.2542° N, 4.2329° E
Area
North Sea
Status
Under way using engineWhat do AIS statuses mean?
Speed
2.5 kn
Course
11°
Heading
13°
Compass: course over ground 11°, heading 13°
NArrow: course. Hull: heading. As broadcast on AIS.
51.2542° N, 4.2329° E. Reference map only, not for navigation.
Locator map: Natural Earth (public domain)
51.2542° N, 4.2329° E
See it live in 3D →

Last 30 days: at least 12 port calls (Kallo, Zeebrugge, Oulu (Uleaborg), Ajos, Yxpila, and Husum).

Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.

Data: AISHub contributors

A year of history in the Terminal (Plus) · the full archive since June 1, 2026 (Pro)Free forever. No card. Follow a ship and Plus is free for 14 days.

Try the live demo, no sign-up

Identity & particulars

Name
BALTIC ENABLER
IMO numberWhat is an IMO number?
9884681
MMSIWhat is an MMSI?
265039000
Flag
Sweden
Year built
—

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.

AIS-reported: the size the ship itself broadcasts over AIS, in whole metres, as entered on board. It is not a register entry. Received via AISstream.io global terrestrial AIS on November 19, 2026.

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

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.

DateEventSource
Arrived at KalloAIS-detectedVoydar port-call detector (AIS geofence)
Left ZeebruggeAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at ZeebruggeAIS-detectedVoydar port-call detector (AIS geofence)
Left Oulu (Uleaborg)AIS-detectedVoydar port-call detector (AIS geofence)
Reported departure from Oulu (Uleaborg)Authority-reportedDigitraffic Port Call API
Reported arrival at Oulu (Uleaborg)Authority-reportedDigitraffic Port Call API
Arrived at Oulu (Uleaborg)AIS-detectedVoydar port-call detector (AIS geofence)
Reported departure from Kemi/Tornea (Kemi/Tornio)Authority-reportedDigitraffic Port Call API
Reported arrival at Kemi/Tornea (Kemi/Tornio)Authority-reportedDigitraffic Port Call API
Reported departure from Karleby (Kokkola)Authority-reportedDigitraffic Port Call API
Reported arrival at Karleby (Kokkola)Authority-reportedDigitraffic Port Call API

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.

CO₂ emitted per reporting year, tonnes (EU MRV, as reported and verified). The table below has every figure.
YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
202214,543 t4,581 t120 days368 kg
202334,768 t11,557 t247 days398 kg
202435,923 t12,453 t253 days421 kg
202536,568 t12,307 t246 days420 kg

Technical efficiency: EEXI (6.71 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 “Ro-ro ship”. Lower is less CO₂.

CO₂ per tonne of cargo carried one nautical mile30.18 g per tonne-nautical mile
Lowest reportedHighest reported

1% of the 238 ships in this group reported a lower figure.

Group: lower quartile 69.33 · median 95.91 · upper quartile 184.71

CO₂ per nautical mile sailed419.9 kg per nautical mile
Lowest reportedHighest reported

82% of the 242 ships in this group reported a lower figure.

Group: lower quartile 271 · median 326.7 · upper quartile 406.8

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

Time in port over the last 30 days, drawn by Voydar from the AIS-detected calls listed below. Each bar runs from arrival to departure; gaps are time away from a detected port or without reception.
PortArrivedDepartedTime in port
Kallo BEKOUNov 19, 2026, 02:05 UTCin port—
Zeebrugge BEZEENov 18, 2026, 13:02 UTCNov 18, 2026, 21:36 UTC8 h 34 min
Oulu (Uleaborg) FIOULNov 12, 2026, 14:05 UTCNov 13, 2026, 20:15 UTC30 h 10 min
Ajos FIAJONov 12, 2026, 03:21 UTCNov 12, 2026, 10:38 UTC7 h 18 min
Yxpila FIYXPNov 11, 2026, 04:21 UTCNov 11, 2026, 13:40 UTC9 h 19 min
Kallo BEKOUNov 5, 2026, 02:10 UTCNov 6, 2026, 09:25 UTC31 h 14 min
Zeebrugge BEZEENov 4, 2026, 12:37 UTCNov 4, 2026, 22:04 UTC9 h 27 min
Oulu (Uleaborg) FIOULOct 29, 2026, 15:25 UTCOct 30, 2026, 21:10 UTC29 h 45 min
Ajos FIAJOOct 28, 2026, 21:31 UTCOct 29, 2026, 11:26 UTC13 h 55 min
Yxpila FIYXPOct 27, 2026, 20:03 UTCOct 28, 2026, 13:43 UTC17 h 40 min
Husum SEHUSOct 27, 2026, 04:48 UTCOct 27, 2026, 10:25 UTC5 h 37 min
Kallo BEKOUOct 22, 2026, 03:44 UTCOct 23, 2026, 06:10 UTC26 h 27 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
Oulu (Uleaborg) FIOULArrivalNov 12, 2026, 14:40 UTC102Digitraffic Port Call API
Kemi/Tornea (Kemi/Tornio) FIKEMArrivalNov 12, 2026, 03:45 UTCLAITURI 4 LP1Digitraffic Port Call API
Karleby (Kokkola) FIKOKArrivalNov 11, 2026, 04:30 UTCHopeakiven laituri 3Digitraffic Port Call API
Oulu (Uleaborg) FIOULArrivalOct 29, 2026, 15:55 UTC102Digitraffic Port Call API
Kemi/Tornea (Kemi/Tornio) FIKEMArrivalOct 28, 2026, 22:06 UTCLAITURI 4 LP1Digitraffic Port Call API
Karleby (Kokkola) FIKOKArrivalOct 27, 2026, 20:00 UTCHopeakiven laituri 3Digitraffic Port Call API
Jakobstad (Pietarsaari) FIPRSArrivalOct 17, 2026, 04:00 UTCLaukko IDigitraffic Port Call API
Oulu (Uleaborg) FIOULArrivalOct 16, 2026, 05:55 UTC102Digitraffic Port Call API
Kemi/Tornea (Kemi/Tornio) FIKEMArrivalOct 14, 2026, 21:00 UTCLAITURI 4 LP1Digitraffic Port Call API
Karleby (Kokkola) FIKOKArrivalOct 14, 2026, 04:00 UTCHopeakiven laituri 1Digitraffic Port Call API

Records published by the authority named on each row. Earliest record for this ship: October 14, 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.

Predicted arrival

Voydar estimates arrival at Antwerpen around Nov 19, 2026, 17:48 UTC, most likely between Nov 19, 2026, 03:40 UTC and Nov 22, 2026, 22:11 UTC. Based on 74 past transits between BEZEE and Antwerpen seen in our port calls. The crew-reported ETA is Nov 19, 2026, 04:00 UTC.

Medium (56%) · Method seadar.behaviour.eta_prediction v1

WhenWhat we observedConfidence
Oct 15, 2026, 17:06 UTC
Draught change

Reported draught went from 7.6 m to 8.4 m while in port at Ajos. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Oct 9, 2026, 03:36 UTC
Draught change

Reported draught went from 7.1 m to 7.6 m while in port at Kallo. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Oct 5, 2026, 16:00 UTC
Draught change

Reported draught went from 8.6 m to 7.4 m after leaving Travemunde. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (55%)
Oct 1, 2026, 11:41 UTC
Draught change

Reported draught went from 7.3 m to 8.3 m while in port at Ajos. 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

What kind of ship is BALTIC ENABLER?
BALTIC ENABLER is a ro-ro ship sailing under the flag of Sweden.
Who is recorded as the owner or manager of BALTIC ENABLER?
Wallenius Marine is recorded as ISM manager for BALTIC ENABLER (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 BALTIC ENABLER?
Voydar has no matched sanctions record displayed for BALTIC ENABLER 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 BALTIC ENABLER. Missing records do not establish whether the ship has been detained.

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.

See a sample report (PDF)

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 Ro-ro ships

Other ro-ro ships with full Voydar profiles. A different set each day. All ro-ro ships

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/9884681
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

Cite this page

BALTIC ENABLER. Voydar (voydar.com). https://www.voydar.com/vessel/9884681-baltic-enabler. Retrieved November 19, 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 includes use in your own product. Growth and Scale add volume, and each includes one Pro membership.

See plans

Sources and attribution

  • Data: AISHub contributors (AISHub Terms of Use (2026-10-08))

Each fact above names its source and the date it was retrieved. Each source's licence applies to its data.

Compiled by Voydar from the sources named on this page.

Page: https://www.voydar.com/vessel/9884681-baltic-enabler

Generated from voydar.com on Nov 19, 2026, 17:59 UTC