LAKEWAY EXPRESS
Ro-ro ship · Sweden · built 1999 · AIS Class A
In short
LAKEWAY EXPRESS (Ro-ro ship, Sweden flag) was last seen on AIS on , in the Baltic Sea. Its crew-entered AIS destination is SE IGG (Iggesund), with an ETA of Nov 20, 2026, 11:00 UTC; its reported draught is 5.7 m (voyage report via Digitraffic marine AIS, received Nov 20, 2026, 04:31 UTC). ISM manager: Wallenius Marine (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
Current voyage: from Ellerbek (departed Nov 19, 2026, 00:18 UTC) to SE IGG (Iggesund)
- Vessel type
- Ro-ro ship
- Flag
- Sweden
- Year built
- 1999
- Gross tonnage
- 10,471
- Size (length × beam)
- 154 m × 24 m
- ISM manager
- Wallenius Marine

Last reported position: 61.6207° N, 17.1377° E · Baltic Sea · See on the map
Shipping a car on this vessel?
Follow LAKEWAY EXPRESS and Voydar's daily email tells you when it has reached Iggesund, and when it leaves or changes its destination.
What you would have been told
Nothing in the last 24 hours: no arrival or departure at a port. You are told the moment that changes.
Detected from AIS, as of Nov 20, 2026, 12:06 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for LAKEWAY EXPRESS 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
- 61.6207° N, 17.1377° E
- Area
- Baltic Sea
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 0.6 kn
- Course
- 348°
- Heading
- 136°
- Compass: course over ground 348°, heading 136°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 9 port calls (Ellerbek and Alholmen).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows LAKEWAY EXPRESS's track before the last 30 days. Voydar has recorded its port calls since July 24, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
Length overall 153.5 mone tick every 25 m
Beam 23.6 mPlan outline, to scale
- Name
- LAKEWAY EXPRESS
- IMO numberWhat is an IMO number?
- 9183790
- MMSIWhat is an MMSI?
- 265052000
- Call signWhat is a call sign?
- SBAV
- Flag
- Sweden
- Vessel type
- Ro-ro ship
- Gross tonnageGross tonnage vs deadweight
- 10,471
- Deadweight (DWT)
- Source: Wikidata, record Q15622496. Added to Voydar on November 19, 2026. Licence: CC0 1.0.7,440 t
- Length overall
- 153.5 m
- Beam
- 23.6 m
- Year built
- 1999
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 · high confidence · retrieved Nov 16, 2026Source: EU MRV (THETIS-MRV) emissions · reporting year 2024 · reported · high confidence · retrieved Nov 16, 2026
- Builder
- Source: Wikidata · reported · high confidence · retrieved Nov 15, 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.
| Date | Event | Source |
|---|---|---|
| Left EllerbekAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at EllerbekAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left EllerbekAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at EllerbekAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left EllerbekAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at EllerbekAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported arrival at Jakobstad (Pietarsaari)Authority-reported | Digitraffic Port Call API | |
| ISM manager: Wallenius Marine AB (previously DFDS Iberia S.L.U.) | Voydar relationship-change derivation (derived by Voydar from EU MRV (THETIS-MRV) emissions) |
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 |
|---|---|---|---|---|
| 2019 | 17,577 t | 5,638 t | 216 days | 240 kg |
| 2020 | 6,360 t | 2,031 t | 74 days | 310 kg |
| 2021 | 5,042 t | 1,609 t | 58 days | 376 kg |
| 2022 | 5,139 t | 1,639 t | 62 days | 356 kg |
| 2024 | 12,579 t | 3,944 t | 196 days | 210 kg |
| 2025 | 17,484 t | 5,468 t | 265 days | 204 kg |
Technical efficiency: EEXI (12.18 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 mile400.37 g per tonne-nautical mile
- Lowest reportedHighest reported
92% 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 sailed204.3 kg per nautical mile
- Lowest reportedHighest reported
13% 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
| Port | Arrived | Departed | Time in port |
|---|---|---|---|
| Ellerbek DEELB | Nov 18, 2026, 20:55 UTC | Nov 19, 2026, 00:18 UTC | 3 h 23 min |
| Ellerbek DEELB | Nov 15, 2026, 09:45 UTC | Nov 15, 2026, 13:16 UTC | 3 h 32 min |
| Ellerbek DEELB | Nov 11, 2026, 22:01 UTC | Nov 12, 2026, 02:15 UTC | 4 h 14 min |
| Ellerbek DEELB | Nov 8, 2026, 10:00 UTC | Nov 8, 2026, 14:04 UTC | 4 h 4 min |
| Ellerbek DEELB | Nov 4, 2026, 19:41 UTC | Nov 4, 2026, 23:23 UTC | 3 h 42 min |
| Ellerbek DEELB | Nov 1, 2026, 05:15 UTC | Nov 1, 2026, 13:23 UTC | 8 h 8 min |
| Alholmen FIAHL | Oct 29, 2026, 04:38 UTC | Oct 29, 2026, 11:23 UTC | 6 h 45 min |
| Ellerbek DEELB | Oct 26, 2026, 10:03 UTC | Oct 26, 2026, 14:07 UTC | 4 h 5 min |
| Ellerbek DEELB | Oct 22, 2026, 04:00 UTC | Oct 22, 2026, 08:25 UTC | 4 h 25 min |
| Ellerbek DEELB | Oct 11, 2026, 06:52 UTC | Oct 14, 2026, 13:30 UTC | 3 d 6 h |
| Lindo Havn DKLIN | Sep 26, 2026, 22:29 UTC | Oct 1, 2026, 21:15 UTC | 4 d 22 h |
| Kopparverkshamnen SEKVH | Jul 24, 2026, 15:25 UTC | Aug 21, 2026, 18:20 UTC | 28 d 2 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.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Jakobstad (Pietarsaari) FIPRS | Arrival | Oct 29, 2026, 05:00 UTC | Buskön laituri | Digitraffic Port Call API |
Records published by the authority named on each row. Earliest record for this ship: October 29, 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 Kiel around Nov 29, 2026, 12:14 UTC, most likely between Nov 21, 2026, 11:34 UTC and Dec 4, 2026, 15:35 UTC. Based on 44 past transits between DEELB and Kiel seen in our port calls. The crew-reported ETA is Nov 18, 2026, 21:00 UTC.
Medium (60%) · Method seadar.behaviour.eta_prediction v1
| When | What we observed | Confidence |
|---|---|---|
| Nov 4, 2026, 22:37 UTC | Draught change Reported draught went from 6.7 m to 5.5 m while in port at Ellerbek. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 1, 2026, 15:50 UTC | Draught change Reported draught went from 7 m to 5.8 m after leaving Ellerbek. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Oct 26, 2026, 13:38 UTC | Draught change Reported draught went from 6.8 m to 5.6 m while in port at Ellerbek. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 22, 2026, 07:52 UTC | Draught change Reported draught went from 6.8 m to 5.8 m while in port at Ellerbek. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 14, 2026, 16:16 UTC | Draught change Reported draught went from 6.6 m to 5.8 m after leaving Ellerbek. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
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.
Frequently asked questions
- What kind of ship is LAKEWAY EXPRESS?
- LAKEWAY EXPRESS is a ro-ro ship sailing under the flag of Sweden, built in 1999 by Pella Sietas. The vessel is 153.5 m long with a beam of 23.6 m and has a gross tonnage of 10,471.
- Who is recorded as the owner or manager of LAKEWAY EXPRESS?
- Wallenius Marine is recorded as ISM manager for LAKEWAY EXPRESS (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 LAKEWAY EXPRESS?
- Voydar has no matched sanctions record displayed for LAKEWAY EXPRESS 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 LAKEWAY EXPRESS. 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.
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/9183790Cite this page
LAKEWAY EXPRESS. Voydar (voydar.com). https://www.voydar.com/vessel/9183790-lakeway-express. Retrieved November 20, 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.