Skip to content

Tulipa Seaways

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

IMO9809100MMSI277548000Call signLYBCLast AIS position Oct 5, 2026, 09:58 UTC

In short

Tulipa Seaways (Ro-ro ship, Lithuania flag) was last seen on AIS on , moored, in the port of Vlaardingen. Its crew-entered AIS destination is NLVLA-GBFXT-NLVLA, with an ETA of Oct 5, 2026, 05:10 UTC; its reported draught is 5.8 m (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 10:07 UTC). It arrived there on Oct 5, 2026, 04:50 UTC. ISM manager: AB DFDS Seaways (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Vessel type
Ro-ro ship
Year built
2017
Gross tonnage
32,336
Size (length × beam)
210 m
ISM manager
AB DFDS Seaways

Watch this ship

Get an email when Tulipa Seaways 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.

Photo of TULIPA SEAWAYS
Photo: kees torn · Licence: CC BY-SA 2.0 · via Wikimedia Commons

Last reported position

received
Position
51.9078° N, 4.3623° E
Area
North Sea
Speed
0 kn
Course
239°
Heading
156°
51.9078° N, 4.3623° E
Open the full live map →

Last 30 days: at least 12 port calls (Vlaardingen and Felixstowe).

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
Tulipa Seaways
IMO numberWhat is an IMO number?
9809100
MMSIWhat is an MMSI?
277548000
AIS ship type
Cargo (hazardous cat. A)
Gross tonnageGross tonnage vs deadweight
32,336
Length overall
209.6 m
Beam
—
Year built
2017

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
Arrived at VlaardingenAIS-detectedVoydar port-call detector (AIS geofence)
Left FelixstoweAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at FelixstoweAIS-detectedVoydar port-call detector (AIS geofence)
Left VlaardingenAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at VlaardingenAIS-detectedVoydar 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.

YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
201826,944 t8,648 t157 days435 kg
201926,364 t8,461 t160 days426 kg
202027,340 t8,774 t166 days433 kg
202135,082 t11,192 t198 days434 kg
202222,417 t7,187 t147 days407 kg
202320,790 t6,672 t160 days361 kg
202424,569 t7,873 t184 days379 kg
202522,343 t7,156 t172 days370 kg

Technical efficiency: EEXI (12.1 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
Vlaardingen NLVLAOct 5, 2026, 04:50 UTCin port—
Felixstowe GBFXTOct 3, 2026, 21:05 UTCOct 4, 2026, 20:22 UTC23 h 17 min
Vlaardingen NLVLAOct 3, 2026, 01:14 UTCOct 3, 2026, 13:16 UTC12 h 2 min
Felixstowe GBFXTOct 2, 2026, 13:57 UTCOct 2, 2026, 18:22 UTC4 h 25 min
Vlaardingen NLVLAOct 2, 2026, 01:14 UTCOct 2, 2026, 06:18 UTC5 h 4 min
Felixstowe GBFXTOct 1, 2026, 14:02 UTCOct 1, 2026, 18:39 UTC4 h 37 min
Vlaardingen NLVLAOct 1, 2026, 01:27 UTCOct 1, 2026, 06:28 UTC5 h 2 min
Felixstowe GBFXTSep 30, 2026, 14:00 UTCSep 30, 2026, 18:23 UTC4 h 24 min
Vlaardingen NLVLASep 30, 2026, 01:28 UTCSep 30, 2026, 06:02 UTC4 h 34 min
Vlaardingen NLVLASep 29, 2026, 01:16 UTCSep 29, 2026, 06:00 UTC4 h 44 min
Felixstowe GBFXTSep 27, 2026, 21:00 UTCSep 28, 2026, 18:22 UTC21 h 23 min
Felixstowe GBFXTSep 26, 2026, 02:44 UTCSep 26, 2026, 19:54 UTC17 h 9 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
Sep 26, 2026, 19:09 UTC
Draught change

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

Method seadar.behaviour.draught_change v1

Medium (65%)
Sep 25, 2026, 18:44 UTC
Draught change

Reported draught went from 5.7 m to 6.2 m while in port at Vlaardingen. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Sep 25, 2026, 07:10 UTC
Draught change

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

Method seadar.behaviour.draught_change v1

Medium (65%)
Sep 24, 2026, 19:15 UTC
Draught change

Reported draught went from 5.8 m to 6.3 m after leaving Felixstowe. 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.

How these are computed →

Frequently asked questions

Where is Tulipa Seaways now?
Tulipa Seaways (Ro-ro ship, Lithuania flag) was last seen on AIS on Oct 5, 2026, 09:58 UTC, moored, in the port of Vlaardingen. The crew-entered destination was NLVLA-GBFXT-NLVLA (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 10:07 UTC). This report does not confirm the ship’s current route.
What kind of ship is Tulipa Seaways?
Tulipa Seaways is a ro-ro ship sailing under the flag of Lithuania, built in 2017 by Flensburger Schiffbau-Gesellschaft. The vessel is 209.6 m long and has a gross tonnage of 32,336.
Who is recorded as the owner or manager of Tulipa Seaways?
AB DFDS Seaways is recorded as ISM manager for Tulipa 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 Tulipa Seaways?
Voydar has no matched sanctions record displayed for Tulipa 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 Tulipa 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/9809100
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