TAVASTLAND
Ro-ro ship · Sweden · built 2006 · AIS Class A
In short
TAVASTLAND (Ro-ro ship, Sweden flag) was last seen on AIS on , under way at 16.4 kn, near Travemunde (Baltic Sea). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its reported AIS draught is 6.6 m (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 06:06 UTC). Its last detected port call was at Holtenau: arrived Oct 4, 2026, left Oct 4, 2026. ISM manager: Wallenius Marine (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
- Vessel type
- Ro-ro ship
- Flag
- Sweden
- Year built
- 2006
- Gross tonnage
- 23,128
- Size (length × beam)
- 191 m
- ISM manager
- Wallenius Marine
Watch this ship
TAVASTLAND has not been received for a while. Follow it and we will email you as soon as it is heard again, then when it reaches or leaves port.
Free forever. No card. A free account follows up to 5 ships and ports.

Last reported position
received- Position
- 54.1175° N, 11.1618° E
- Area
- Baltic Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 16.4 kn
- Course
- 227°
- Heading
- 227°
Last 30 days: 9 port calls (Holtenau, Borgstedt, Tilbury, Zeebrugge, 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)Free forever. No card. New accounts include 14 days of Pro.
Try the live demo, no sign-upIdentity & particulars
- Name
- TAVASTLAND
- IMO numberWhat is an IMO number?
- 9334959
- MMSIWhat is an MMSI?
- 266232000
- Call signWhat is a call sign?
- SKEC
- Flag
- Sweden
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 23,128
- Length overall
- 191 m
- Beam
- —
- Year built
- 2006
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 Oct 5, 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.
| Date | Event | Source |
|---|---|---|
| Left HoltenauAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at HoltenauAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left BorgstedtAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at BorgstedtAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left TilburyAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at TilburyAIS-detected | Voydar 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.
| Year | CO₂ emitted | Fuel burned | Time at sea | CO₂ / n mile |
|---|---|---|---|---|
| 2018 | 32,972 t | 10,574 t | 292 days | 337 kg |
| 2019 | 32,056 t | 10,267 t | 282 days | 343 kg |
| 2020 | 31,188 t | 9,776 t | 272 days | 342 kg |
| 2021 | 36,815 t | 11,483 t | 282 days | 399 kg |
| 2022 | 33,325 t | 10,552 t | 264 days | 379 kg |
| 2023 | 19,982 t | 6,326 t | 256 days | 354 kg |
| 2024 | 23,345 t | 7,397 t | 261 days | 323 kg |
| 2025 | 20,905 t | 6,621 t | 194 days | 353 kg |
Technical efficiency: EEXI (11.06 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
| Port | Arrived | Departed | Time in port |
|---|---|---|---|
| Holtenau DEHTU | Oct 4, 2026, 03:17 UTC | Oct 4, 2026, 04:23 UTC | 1 h 6 min |
| Borgstedt DEBYT | Oct 4, 2026, 00:28 UTC | Oct 4, 2026, 01:23 UTC | 56 min |
| Tilbury GBTIL | Oct 2, 2026, 07:46 UTC | Oct 2, 2026, 15:49 UTC | 8 h 3 min |
| Tilbury GBTIL | Oct 2, 2026, 03:14 UTC | Oct 2, 2026, 07:39 UTC | 4 h 25 min |
| Zeebrugge BEZEE | Oct 1, 2026, 11:46 UTC | Oct 1, 2026, 16:35 UTC | 4 h 49 min |
| Kiel Canal DECKL | Sep 26, 2026, 15:54 UTC | Sep 26, 2026, 22:36 UTC | 6 h 42 min |
| Tilbury GBTIL | Sep 25, 2026, 06:46 UTC | Sep 25, 2026, 17:57 UTC | 11 h 11 min |
| Zeebrugge BEZEE | Sep 24, 2026, 15:39 UTC | Sep 24, 2026, 19:24 UTC | 3 h 46 min |
| Zeebrugge BEZEE | Sep 24, 2026, 11:52 UTC | Sep 24, 2026, 15:18 UTC | 3 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.
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.
| When | What we observed | Confidence |
|---|---|---|
| Oct 3, 2026, 08:33 UTC | Draught change Reported draught went from 7.5 m to 6.6 m after leaving Tilbury. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Sep 26, 2026, 15:19 UTC | Draught change Reported draught went from 7.7 m to 6.7 m after leaving Tilbury. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Sep 26, 2026, 05:08 UTC | Draught change Reported draught went from 6.7 m to 7.7 m after leaving Tilbury. Voydar infers the ship probably loaded 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
- Where is TAVASTLAND now?
- TAVASTLAND (Ro-ro ship, Sweden flag) was last seen on AIS on Oct 4, 2026, 09:04 UTC, under way at 16.4 kn, near Travemunde (Baltic Sea). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report.
- What kind of ship is TAVASTLAND?
- TAVASTLAND is a ro-ro ship sailing under the flag of Sweden, built in 2006 by Meyer Wismar. The vessel is 191 m long and has a gross tonnage of 23,128.
- Who is recorded as the owner or manager of TAVASTLAND?
- Wallenius Marine is recorded as ISM manager for TAVASTLAND (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 TAVASTLAND?
- Voydar has no matched sanctions record displayed for TAVASTLAND 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 TAVASTLAND. 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/9334959Using 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.