Skip to content

Victoria Seaways

Ro-ro ship · Lithuania · built 2009 · AIS Class A

IMO9350721MMSI277408000Call signLYTDLast AIS position Oct 6, 2026, 16:02 UTC

In short

Victoria Seaways (Ro-ro ship, Lithuania flag) was last seen on AIS on , under way at 18.9 kn, in the English Channel. Its crew-entered AIS destination is FRDKK (Dunkerque), with an ETA of Oct 6, 2026, 19:00 UTC; its reported draught is 5.5 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 15:29 UTC). ISM manager: AB DFDS Seaways (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Current voyage: from Rosslare (departed Oct 5, 2026, 19:56 UTC) to FRDKK (Dunkerque)

Vessel type
Ro-ro ship
Year built
2009
Gross tonnage
25,675
Size (length × beam)
199 m
ISM manager
AB DFDS Seaways

Watch this ship

Get an email when Victoria Seaways reaches Dunkerque, and when it 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.

Photo of VICTORIA SEAWAYS
Photo: Bin im Garten · Licence: CC BY-SA 3.0 · via Wikimedia Commons

Last reported position

received
Position
50.657° N, 1.2189° E
Area
English Channel
StatusWhat do AIS statuses mean?
Under way using engine
Speed
18.9 kn
Course
47°
Heading
48°
50.657° N, 1.2189° E
Open the full live map →

Last 30 days: 4 port calls (Rosslare).

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-up

Identity & particulars

Name
Victoria Seaways
IMO numberWhat is an IMO number?
9350721
MMSIWhat is an MMSI?
277408000
AIS ship type
Passenger (hazardous cat. C)
Gross tonnageGross tonnage vs deadweight
25,675
Length overall
199 m
Beam
—
Year built
2009

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.

DateEventSource
Left RosslareAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at RosslareAIS-detectedVoydar port-call detector (AIS geofence)
Left RosslareAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at RosslareAIS-detectedVoydar port-call detector (AIS geofence)
Left RosslareAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at RosslareAIS-detectedVoydar port-call detector (AIS geofence)
Former name: ForzaWikidata
Former name: Lisco MaximaWikidata

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.

Former and other names

Names attested for this ship other than its current name.

NameEvidenceDateSource
ForzaFormer nameJan 1, 2009Wikidata
Lisco MaximaFormer nameJan 1, 2009Wikidata

A sanctions list's date is the earliest date the list shows the name, not when the ship took it. A name on a list is shown as a former name only where AIS shows the ship using another name after that date; otherwise it is listed as a name the list uses. AIS name changes are dated when Voydar saw them.

Source: Wikidata. Licence: CC0 1.0.

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
201865,918 t21,164 t290 days469 kg
201954,902 t17,626 t274 days456 kg
202063,526 t20,397 t284 days469 kg
202161,879 t19,818 t278 days468 kg
202257,682 t18,475 t277 days435 kg
202357,515 t18,421 t283 days428 kg
202446,353 t14,836 t250 days401 kg
202548,366 t15,485 t252 days413 kg

Technical efficiency: EEXI (27.15 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

PortArrivedDepartedTime in port
Rosslare IEROEOct 5, 2026, 02:49 UTCOct 5, 2026, 19:56 UTC17 h 8 min
Rosslare IEROEOct 2, 2026, 02:55 UTCOct 2, 2026, 20:56 UTC18 h 1 min
Rosslare IEROESep 26, 2026, 18:41 UTCSep 26, 2026, 22:45 UTC4 h 3 min
Rosslare IEROESep 23, 2026, 21:50 UTCSep 24, 2026, 01:51 UTC4 h 1 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.

WhenWhat we observedConfidence
Oct 5, 2026, 06:55 UTC
Draught change

Reported draught went from 5.6 m to 5.1 m while in port at Rosslare. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Sep 22, 2026, 17:52 UTC
AIS gap

No AIS position received for 6 h 10 min while our receivers kept hearing other ships there (5 of 6 hours in coverage). Heard again 14 km away.

Method seadar.behaviour.ais_gap v1

High (80%)

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

Where is Victoria Seaways now?
Victoria Seaways (Ro-ro ship, Lithuania flag) was last seen on AIS on Oct 6, 2026, 16:02 UTC, under way at 18.9 kn, in the English Channel. The crew-entered destination was FRDKK (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 15:29 UTC). This report does not confirm the ship’s current route.
What kind of ship is Victoria Seaways?
Victoria Seaways is a ro-ro ship sailing under the flag of Lithuania, built in 2009 by Nuovi Cantieri Apuania. The vessel is 199 m long and has a gross tonnage of 25,675.
Who is recorded as the owner or manager of Victoria Seaways?
AB DFDS Seaways is recorded as ISM manager for Victoria Seaways (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 Victoria Seaways?
Voydar has no matched sanctions record displayed for Victoria Seaways 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 Victoria Seaways. 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/9350721
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

Using 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.

See plans