Finncanopus
Ferry · Finland · built 2023 · AIS Class A
In short
Finncanopus (Ferry, Finland flag) was last seen on AIS on , under way at 13.5 kn, in the Baltic Sea. Its crew-entered AIS destination is FINLI >FILAN >SEKAP; its reported draught is 6.7 m (voyage report via Digitraffic marine AIS, received Oct 6, 2026, 10:44 UTC). Registered owner: Finnlines (source: Wikidata). It can carry up to 1,100 passengers (source: Wikidata).
Current voyage: from Naantali (Nadendal) (departed Oct 6, 2026, 07:58 UTC) to FINLI >FILAN >SEKAP
- Vessel type
- Ferry
- Flag
- Finland
- Year built
- 2023
- Gross tonnage
- 64,600
- Size (length × beam)
- 235 m × 33 m
- Registered owner
- Finnlines
Watch this ship
Get an email when Finncanopus arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
Free forever. No card. A free account follows up to 5 ships and ports.

Last reported position
received- Position
- 60.0789° N, 20.8788° E
- Area
- Baltic Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 13.5 kn
- Course
- 269°
- Heading
- 270°
Last 30 days: at least 12 port calls (Naantali (Nadendal) and Kapellskar).
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
- Finncanopus
- IMO numberWhat is an IMO number?
- 9902421
- MMSIWhat is an MMSI?
- 230704000
- Call signWhat is a call sign?
- OJUL
- Flag
- Finland
- Vessel type
- Detailed type from WikidataFerry
- AIS ship type
- Passenger
- Gross tonnageGross tonnage vs deadweight
- 64,600
- Length overall
- 235 m
- Beam
- 33.3 m
- Year built
- 2023
- Passengers (maximum)
- Source: Wikidata, record Q124461314. Added to Voydar on September 23, 2026. Licence: CC0 1.0.1,100
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.
- Registered owner
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
- 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 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 Naantali (Nadendal)AIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Naantali (Nadendal)AIS-detected | Voydar port-call detector (AIS geofence) | |
| Left KapellskarAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at KapellskarAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Naantali (Nadendal)AIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Naantali (Nadendal)AIS-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 |
|---|---|---|---|---|
| 2024 | 34,355 t | 11,010 t | 224 days | 459 kg |
| 2025 | 34,134 t | 10,944 t | 245 days | 426 kg |
Technical efficiency: EEDI (16.75 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 |
|---|---|---|---|
| Naantali (Nadendal) FINLI | Oct 6, 2026, 04:03 UTC | Oct 6, 2026, 07:58 UTC | 3 h 55 min |
| Kapellskar SEKPS | Oct 5, 2026, 16:17 UTC | Oct 5, 2026, 19:49 UTC | 3 h 32 min |
| Naantali (Nadendal) FINLI | Oct 5, 2026, 04:06 UTC | Oct 5, 2026, 07:46 UTC | 3 h 40 min |
| Naantali (Nadendal) FINLI | Oct 4, 2026, 04:03 UTC | Oct 4, 2026, 07:17 UTC | 3 h 14 min |
| Kapellskar SEKPS | Oct 3, 2026, 15:35 UTC | Oct 3, 2026, 19:51 UTC | 4 h 16 min |
| Naantali (Nadendal) FINLI | Oct 3, 2026, 04:10 UTC | Oct 3, 2026, 06:53 UTC | 2 h 43 min |
| Kapellskar SEKPS | Oct 2, 2026, 15:34 UTC | Oct 2, 2026, 19:42 UTC | 4 h 8 min |
| Naantali (Nadendal) FINLI | Oct 2, 2026, 04:02 UTC | Oct 2, 2026, 07:28 UTC | 3 h 26 min |
| Kapellskar SEKPS | Oct 1, 2026, 15:35 UTC | Oct 1, 2026, 19:47 UTC | 4 h 12 min |
| Naantali (Nadendal) FINLI | Oct 1, 2026, 04:03 UTC | Oct 1, 2026, 07:17 UTC | 3 h 15 min |
| Naantali (Nadendal) FINLI | Sep 30, 2026, 04:03 UTC | Sep 30, 2026, 07:09 UTC | 3 h 7 min |
| Kapellskar SEKPS | Sep 29, 2026, 16:18 UTC | Sep 29, 2026, 19:47 UTC | 3 h 29 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, 06:48 UTC | Draught change Reported draught went from 6.8 m to 6.3 m while in port at Naantali (Nadendal). Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 2, 2026, 19:49 UTC | Draught change Reported draught went from 6.2 m to 6.8 m after leaving Kapellskar. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Oct 2, 2026, 07:26 UTC | Draught change Reported draught went from 7 m to 6.2 m while in port at Naantali (Nadendal). Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 1, 2026, 19:51 UTC | Draught change Reported draught went from 6.4 m to 7 m after leaving Kapellskar. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Oct 1, 2026, 07:10 UTC | Draught change Reported draught went from 7 m to 6.4 m while in port at Naantali (Nadendal). Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 30, 2026, 19:59 UTC | Draught change Reported draught went from 6.4 m to 7 m after leaving Naantali (Nadendal). Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Sep 30, 2026, 07:02 UTC | Draught change Reported draught went from 6.9 m to 6.4 m while in port at Naantali (Nadendal). Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 25, 2026, 07:06 UTC | Draught change Reported draught went from 7 m to 6.3 m while in port at Naantali (Nadendal). Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 24, 2026, 19:54 UTC | Draught change Reported draught went from 6.3 m to 7 m after leaving Naantali (Nadendal). Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Sep 24, 2026, 07:08 UTC | Draught change Reported draught went from 6.8 m to 6.3 m while in port at Naantali (Nadendal). Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
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.
Frequently asked questions
- Where is Finncanopus now?
- Finncanopus (Ferry, Finland flag) was last seen on AIS on Oct 6, 2026, 11:05 UTC, under way at 13.5 kn, in the Baltic Sea. The crew-entered destination was FINLI >FILAN >SEKAP (voyage report via Digitraffic marine AIS, received Oct 6, 2026, 10:44 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Finncanopus?
- Finncanopus is a ferry sailing under the flag of Finland, built in 2023 by China Merchants Heavy Industry. The vessel is 235 m long with a beam of 33.3 m and has a gross tonnage of 64,600.
- Who is recorded as the owner or manager of Finncanopus?
- Finnlines is recorded as Registered owner for Finncanopus (source: Wikidata). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for Finncanopus?
- Voydar has no matched sanctions record displayed for Finncanopus 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 Finncanopus. 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/9902421Using 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.