Tulipa Seaways
Ro-ro ship · Lithuania · built 2017 · AIS Class A
In short
Tulipa Seaways (Ro-ro ship, Lithuania flag) was last seen on AIS on , under way at 16.2 kn, in the North Sea. Its crew-entered AIS destination is NLVLA-GBFXT-NLVLA, with an ETA of Nov 20, 2026, 17:00 UTC; its reported draught is 5.6 m (voyage report via AISstream.io global terrestrial AIS, received Nov 20, 2026, 08:21 UTC). Its last detected port call was at Felixstowe: arrived Nov 20, 2026, left Nov 20, 2026. ISM manager: AB DFDS Seaways (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
- Vessel type
- Ro-ro ship
- Flag
- Lithuania
- Year built
- 2017
- Gross tonnage
- 32,336
- Size (length × beam)
- 210 m
- ISM manager
- AB DFDS Seaways

Last reported position: 51.8765° N, 2.1387° E · North Sea · See on the map
Shipping a car on this vessel?
Follow Tulipa Seaways and Voydar's daily email tells you when it has arrived in port, left again, or changed its destination.
What you would have been told
Following Tulipa Seaways over the last 24 hours would have sent 4 messages.
- LeftFelixstowe
- ArrivedFelixstowe
- LeftVlaardingen
Detected from AIS, as of Nov 20, 2026, 11:01 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for Tulipa Seaways 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: the Voydar app
Last reported position
received- Position
- 51.8765° N, 2.1387° E
- Area
- North Sea
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 16.2 kn
- Course
- 74°
- Heading
- 81°
- Compass: course over ground 74°, heading 81°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: at least 12 port calls (Felixstowe and Vlaardingen).
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. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
Length overall 209.6 mone tick every 25 m
- Name
- Tulipa Seaways
- IMO numberWhat is an IMO number?
- 9809100
- MMSIWhat is an MMSI?
- 277548000
- Call signWhat is a call sign?
- LYBC
- Flag
- Lithuania
- AIS ship type
- Cargo (hazardous cat. A)
- Gross tonnageGross tonnage vs deadweight
- 32,336
- Length overall
- 209.6 m
- Beam (AIS-reported)
- Broadcast by the ship over AIS, not a register entry. Received via AISstream.io global terrestrial AIS on November 20, 2026.26 m
- 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.
AIS-reported: the size the ship itself broadcasts over AIS, in whole metres, as entered on board. It is not a register entry. Received via AISstream.io global terrestrial AIS on November 20, 2026.
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 · 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.
| Date | Event | Source |
|---|---|---|
| Left FelixstoweAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at FelixstoweAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left VlaardingenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at VlaardingenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left FelixstoweAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at FelixstoweAIS-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 | 26,944 t | 8,648 t | 157 days | 435 kg |
| 2019 | 26,364 t | 8,461 t | 160 days | 426 kg |
| 2020 | 27,340 t | 8,774 t | 166 days | 433 kg |
| 2021 | 35,082 t | 11,192 t | 198 days | 434 kg |
| 2022 | 22,417 t | 7,187 t | 147 days | 407 kg |
| 2023 | 20,790 t | 6,672 t | 160 days | 361 kg |
| 2024 | 24,569 t | 7,873 t | 184 days | 379 kg |
| 2025 | 22,343 t | 7,156 t | 172 days | 370 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.
Compared with ships of its type
Where this ship’s reported CO₂ intensity for 2025 sits among the ships EU MRV lists as “Ro-ro ship”. Lower is less CO₂.
- CO₂ per tonne of cargo carried one nautical mile131.2 g per tonne-nautical mile
- Lowest reportedHighest reported
61% of the 238 ships in this group reported a lower figure.
Group: lower quartile 69.33 · median 95.91 · upper quartile 184.71
- CO₂ per nautical mile sailed370.2 kg per nautical mile
- Lowest reportedHighest reported
67% of the 242 ships in this group reported a lower figure.
Group: lower quartile 271 · median 326.7 · upper quartile 406.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
| Port | Arrived | Departed | Time in port |
|---|---|---|---|
| Felixstowe GBFXT | Nov 20, 2026, 03:50 UTC | Nov 20, 2026, 09:08 UTC | 5 h 17 min |
| Vlaardingen NLVLA | Nov 19, 2026, 16:41 UTC | Nov 19, 2026, 20:45 UTC | 4 h 4 min |
| Felixstowe GBFXT | Nov 19, 2026, 03:55 UTC | Nov 19, 2026, 09:00 UTC | 5 h 5 min |
| Vlaardingen NLVLA | Nov 18, 2026, 16:37 UTC | Nov 18, 2026, 21:00 UTC | 4 h 24 min |
| Felixstowe GBFXT | Nov 18, 2026, 03:42 UTC | Nov 18, 2026, 09:15 UTC | 5 h 34 min |
| Vlaardingen NLVLA | Nov 17, 2026, 16:32 UTC | Nov 17, 2026, 21:02 UTC | 4 h 30 min |
| Felixstowe GBFXT | Nov 17, 2026, 03:54 UTC | Nov 17, 2026, 10:58 UTC | 7 h 5 min |
| Vlaardingen NLVLA | Nov 14, 2026, 02:42 UTC | Nov 16, 2026, 20:55 UTC | 2 d 18 h |
| Felixstowe GBFXT | Nov 13, 2026, 15:04 UTC | Nov 13, 2026, 19:32 UTC | 4 h 29 min |
| Vlaardingen NLVLA | Nov 13, 2026, 02:22 UTC | Nov 13, 2026, 07:05 UTC | 4 h 43 min |
| Felixstowe GBFXT | Nov 12, 2026, 14:56 UTC | Nov 12, 2026, 20:09 UTC | 5 h 12 min |
| Vlaardingen NLVLA | Nov 12, 2026, 02:33 UTC | Nov 12, 2026, 06:56 UTC | 4 h 23 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 |
|---|---|---|
| Nov 19, 2026, 08:07 UTC | Draught change Reported draught went from 6.3 m to 5.8 m while in port at Felixstowe. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 17, 2026, 09:11 UTC | Draught change Reported draught went from 6.3 m to 5.8 m while in port at Felixstowe. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 6, 2026, 19:54 UTC | Draught change Reported draught went from 5.8 m to 6.3 m while in port at Vlaardingen. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 5, 2026, 20:06 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%) |
| Nov 5, 2026, 08:41 UTC | Draught change Reported draught went from 6.4 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%) |
| Nov 4, 2026, 20:07 UTC | Draught change Reported draught went from 5.9 m to 6.4 m while in port at Vlaardingen. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 2, 2026, 20:13 UTC | Draught change Reported draught went from 5.8 m to 6.4 m while in port at Vlaardingen. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 26, 2026, 18:56 UTC | Draught change Reported draught went from 5.2 m to 5.9 m while in port at Felixstowe. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 26, 2026, 01:55 UTC | Draught change Reported draught went from 6 m to 5.2 m while in port at Felixstowe. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 24, 2026, 20:12 UTC | Draught change Reported draught went from 6.4 m to 5.9 m while in port at Felixstowe. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 22, 2026, 07:34 UTC | Draught change Reported draught went from 6.4 m to 5.9 m while in port at Felixstowe. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 21, 2026, 19:15 UTC | Draught change Reported draught went from 5.7 m to 6.4 m while in port at Vlaardingen. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 21, 2026, 07:13 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%) |
| Oct 18, 2026, 19:27 UTC | Draught change Reported draught went from 5.4 m to 5.9 m while in port at Felixstowe. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 18, 2026, 06:35 UTC | Draught change Reported draught went from 6.4 m to 5.4 m while in port at Felixstowe. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 17, 2026, 12:40 UTC | Draught change Reported draught went from 5.9 m to 6.4 m while in port at Vlaardingen. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 10, 2026, 19:16 UTC | Draught change Reported draught went from 6.4 m to 5.8 m while in port at Felixstowe. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 9, 2026, 19:50 UTC | Draught change Reported draught went from 5.7 m to 6.4 m while in port at Vlaardingen. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 9, 2026, 07:36 UTC | Draught change Reported draught went from 6.3 m to 5.7 m after leaving Felixstowe. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Oct 8, 2026, 18:39 UTC | Draught change Reported draught went from 5.8 m to 6.3 m while in port at Vlaardingen. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
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
- 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.
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.
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
More Ro-ro ships
Other ro-ro ships with full Voydar profiles. A different set each day. All ro-ro ships
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/9809100Cite this page
Tulipa Seaways. Voydar (voydar.com). https://www.voydar.com/vessel/9809100-tulipa-seaways. Retrieved November 20, 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.