Skip to content
voydar.com

Tornedalen

General cargo ship · Portugal · built 2000 · AIS Class A

IMO9190808MMSI255620000Call signCQCJLast AIS position Nov 18, 2026, 18:15 UTC

In short

Tornedalen (General cargo ship, Portugal flag) was last seen on AIS on , under way at 10.7 kn, near Tolkis (Tolkkinen) (Baltic Sea). Its crew-entered AIS destination is LVRIX (Riga), with an ETA of Nov 19, 2026, 17:00 UTC; its reported draught is 4.1 m (voyage report via AISstream.io global terrestrial AIS, received Nov 18, 2026, 17:56 UTC). ISM manager: Schiffahrtskontor tom Worden GmbH & Co. KG (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).

Current voyage: from Lakulahti (departed Nov 18, 2026, 13:34 UTC) to LVRIX (Riga)

Year built
2000
Gross tonnage
4,211
Size (length × beam)
100 m × 17 m
Photo of Tornedalen
Photo: Niels Johannes · Licence: CC BY-SA 4.0 · via Wikimedia Commons

Last reported position: 59.9778° N, 25.9558° E · Baltic Sea · See on the map

Watch this ship

Get an email when Tornedalen reaches Riga, and when it leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.

What you would have been told

Following Tornedalen over the last 24 hours would have sent 1 message.

Detected from AIS, as of Nov 18, 2026, 18:15 UTC.

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

Last reported position

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

Last 30 days: 7 port calls (Lakulahti and Parnu).

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

Pro shows Tornedalen's track before the last 30 days. Voydar has recorded its port calls since September 25, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.

Try the live demo, no sign-up

Identity & particulars

Length overall 99.9 mone tick every 10 m

Beam 16.5 mPlan outline, to scale

Drawn by Voydar from the recorded type, length and beam. The side view is a drawing of the ship type, not of this ship; the length rule and the plan outline's proportions are to scale, the hull shape is not surveyed.
Name
Tornedalen
IMO numberWhat is an IMO number?
9190808
MMSIWhat is an MMSI?
255620000
Gross tonnageGross tonnage vs deadweight
4,211
Length overall
99.9 m
Beam
16.5 m
Year built
2000

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 year 2025 · 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.

DateEventSource
Left LakulahtiAIS-detectedVoydar port-call detector (AIS geofence)
Reported arrival at KotkaAuthority-reportedDigitraffic Port Call API
Arrived at LakulahtiAIS-detectedVoydar port-call detector (AIS geofence)
Left LakulahtiAIS-detectedVoydar port-call detector (AIS geofence)
Reported departure from KotkaAuthority-reportedDigitraffic Port Call API
Reported arrival at KotkaAuthority-reportedDigitraffic Port Call API
Arrived at LakulahtiAIS-detectedVoydar port-call detector (AIS geofence)
Left ParnuAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at ParnuAIS-detectedVoydar port-call detector (AIS geofence)
Reported departure from KotkaAuthority-reportedDigitraffic Port Call API
Reported arrival at KotkaAuthority-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.

YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
20255,941 t1,853 t201 days127 kg

Technical efficiency: EEXI (11.61 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 “General cargo ship”. Lower is less CO₂.

CO₂ per nautical mile sailed127.4 kg per nautical mile
Lowest reportedHighest reported

58% of the 2,956 ships in this group reported a lower figure.

Group: lower quartile 74.8 · median 110.6 · upper quartile 185.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 55 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
Lakulahti FILAKNov 17, 2026, 09:11 UTCNov 18, 2026, 13:34 UTC28 h 23 min
Lakulahti FILAKNov 12, 2026, 06:38 UTCNov 13, 2026, 18:34 UTC35 h 56 min
Parnu EEPRNNov 9, 2026, 18:18 UTCNov 11, 2026, 12:00 UTC41 h 43 min
Lakulahti FILAKNov 7, 2026, 16:49 UTCNov 8, 2026, 17:19 UTC24 h 30 min
Lakulahti FILAKNov 2, 2026, 15:13 UTCNov 3, 2026, 19:13 UTC27 h 59 min
Lakulahti FILAKOct 28, 2026, 06:45 UTCOct 29, 2026, 11:30 UTC28 h 45 min
Lakulahti FILAKOct 20, 2026, 16:03 UTCOct 22, 2026, 21:16 UTC2 d 5 h
Lakulahti FILAKOct 15, 2026, 11:58 UTCOct 16, 2026, 18:05 UTC30 h 7 min
Oulu (Uleaborg) FIOULOct 8, 2026, 13:47 UTCOct 9, 2026, 07:13 UTC17 h 26 min
Kunda EEKNDOct 3, 2026, 15:10 UTCOct 3, 2026, 22:02 UTC6 h 52 min
Lakulahti FILAKOct 1, 2026, 05:18 UTCOct 3, 2026, 08:33 UTC2 d 3 h
Lakulahti FILAKSep 25, 2026, 08:53 UTCSep 26, 2026, 17:36 UTC32 h 43 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
Kotka FIKTKArrivalNov 17, 2026, 09:30 UTCEU3Digitraffic Port Call API
Kotka FIKTKArrivalNov 12, 2026, 06:55 UTCEU3Digitraffic Port Call API
Kotka FIKTKArrivalNov 7, 2026, 17:00 UTCEU4Digitraffic Port Call API
Kotka FIKTKArrivalNov 2, 2026, 15:20 UTCEU4Digitraffic Port Call API
Kotka FIKTKArrivalOct 28, 2026, 06:50 UTCEU4Digitraffic Port Call API
Kotka FIKTKArrivalOct 20, 2026, 16:10 UTCEU4Digitraffic Port Call API
Kotka FIKTKArrivalOct 15, 2026, 12:00 UTCEU4Digitraffic Port Call API

Records published by the authority named on each row. Earliest record for this ship: October 15, 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
Nov 18, 2026, 11:28 UTC
Draught change

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

Method seadar.behaviour.draught_change v1

High (75%)
Nov 13, 2026, 17:10 UTC
Draught change

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

Method seadar.behaviour.draught_change v1

High (75%)
Nov 11, 2026, 13:04 UTC
Draught change

Reported draught went from 4.1 m to 6.3 m after leaving Parnu. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Nov 8, 2026, 16:25 UTC
Draught change

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

Method seadar.behaviour.draught_change v1

High (75%)
Nov 3, 2026, 17:58 UTC
Draught change

Reported draught went from 6.4 m to 4.1 m while in port at Lakulahti. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

High (75%)
Oct 29, 2026, 10:41 UTC
Draught change

Reported draught went from 6.4 m to 4 m while in port at Lakulahti. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

High (75%)
Oct 16, 2026, 15:08 UTC
Draught change

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

Method seadar.behaviour.draught_change v1

High (75%)
Oct 9, 2026, 05:40 UTC
Draught change

Reported draught went from 6.3 m to 4.3 m while in port at Oulu (Uleaborg). Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

High (75%)
Oct 3, 2026, 21:39 UTC
Draught change

Reported draught went from 4.1 m to 5.5 m while in port at Kunda. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Oct 3, 2026, 07:24 UTC
Draught change

Reported draught went from 6.4 m to 4.1 m while in port at Lakulahti. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

High (75%)
Sep 26, 2026, 16:34 UTC
Draught change

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

Method seadar.behaviour.draught_change v1

High (75%)

Source: Fintraffic / digitraffic.fi, license CC 4.0 BY. Licence: CC BY 4.0.

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 Tornedalen?
Tornedalen is a general cargo ship sailing under the flag of Portugal, built in 2000 by SLKB Komarno – Slovak Shipyard Komárno. The vessel is 99.9 m long with a beam of 16.5 m and has a gross tonnage of 4,211.
Who is recorded as the owner or manager of Tornedalen?
Schiffahrtskontor tom Worden GmbH & Co. KG is recorded as ISM manager for Tornedalen (source: EU MRV (THETIS-MRV) emissions; reporting year 2025). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for Tornedalen?
Voydar has no matched sanctions record displayed for Tornedalen 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 Tornedalen. 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

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

Cite this page

Tornedalen. Voydar (voydar.com). https://www.voydar.com/vessel/9190808-tornedalen. Retrieved November 18, 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

  • Source: Fintraffic / digitraffic.fi, license CC 4.0 BY (CC BY 4.0)
  • Wikidata (CC0 1.0)

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/9190808-tornedalen

Generated from voydar.com on Nov 18, 2026, 18:15 UTC