Ysaline
Ro-ro ship · Malta · built 2019 · AIS Class A
In short
Ysaline (Ro-ro ship, Malta flag) was last seen on AIS on , moored, near Maassluis (North Sea). Its crew-entered AIS destination is NLRTM (Rotterdam), with an ETA of Oct 2, 2026, 07:00 UTC; its reported draught is 6.8 m (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 14:29 UTC). ISM manager: SHIPLUX XIII S.A. (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
Current voyage: from Immingham (departed Oct 1, 2026, 18:34 UTC) to NLRTM (Rotterdam)
- Vessel type
- Ro-ro ship
- Flag
- Malta
- Year built
- 2019
- Gross tonnage
- —
- Size (length × beam)
- —
- ISM manager
- SHIPLUX XIII S.A.
Watch this ship
Get an email when Ysaline arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
We email you a link and a code. That creates a free account, no password or card, and follows Ysaline.
Free account, no card: follow up to 5 ships and ports. Plus follows 50, Pro 500.
By continuing you accept the Terms and the Privacy policy.
Last reported position
received- Position
- 51.8966° N, 4.2369° E
- Area
- North Sea
- StatusWhat do AIS statuses mean?
- Moored
- Speed
- 0 kn
- Course
- 2°
- Heading
- 287°
Last 30 days: 8 port calls (Immingham, Rozenburg, and Botlek).
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)
Try the live demo, no sign-upIdentity & particulars
- Name
- Ysaline
- IMO numberWhat is an IMO number?
- 9823364
- MMSIWhat is an MMSI?
- 248744000
- Call signWhat is a call sign?
- 9HA4792
- Flag
- Malta
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- —
- Length overall
- —
- Beam
- —
- Year built
- 2019
MaltaA 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 Sep 28, 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 ImminghamAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at ImminghamAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left RozenburgAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at RozenburgAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left ImminghamAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at ImminghamAIS-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 |
|---|---|---|---|---|
| 2019 | 16,824 t | 5,357 t | 164 days | 298 kg |
| 2020 | 26,454 t | 8,400 t | 210 days | 343 kg |
| 2021 | 26,627 t | 8,455 t | 211 days | 341 kg |
| 2022 | 28,526 t | 9,096 t | 271 days | 306 kg |
| 2023 | 27,605 t | 8,803 t | 262 days | 313 kg |
| 2024 | 25,996 t | 8,277 t | 254 days | 289 kg |
| 2025 | 21,400 t | 6,798 t | 201 days | 306 kg |
Technical efficiency: EEXI (7.32 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 |
|---|---|---|---|
| Immingham GBIMM | Oct 1, 2026, 07:25 UTC | Oct 1, 2026, 18:34 UTC | 11 h 9 min |
| Rozenburg NLROZ | Sep 30, 2026, 06:32 UTC | Sep 30, 2026, 17:53 UTC | 11 h 21 min |
| Immingham GBIMM | Sep 29, 2026, 06:51 UTC | Sep 29, 2026, 19:35 UTC | 12 h 44 min |
| Botlek NLBOT | Sep 27, 2026, 08:22 UTC | Sep 28, 2026, 18:44 UTC | 34 h 21 min |
| Immingham GBIMM | Sep 26, 2026, 07:42 UTC | Sep 26, 2026, 20:02 UTC | 12 h 21 min |
| Botlek NLBOT | Sep 25, 2026, 09:12 UTC | Sep 25, 2026, 17:39 UTC | 8 h 27 min |
| Immingham GBIMM | Sep 24, 2026, 06:09 UTC | Sep 24, 2026, 18:23 UTC | 12 h 15 min |
| Botlek NLBOT | Sep 23, 2026, 06:28 UTC | Sep 23, 2026, 17:41 UTC | 11 h 13 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 1, 2026, 17:40 UTC | Draught change Reported draught went from 7.3 m to 6.8 m while in port at Immingham. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 26, 2026, 15:09 UTC | Draught change Reported draught went from 7.3 m to 6.6 m while in port at Immingham. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 25, 2026, 16:43 UTC | Draught change Reported draught went from 6.8 m to 7.3 m while in port at Botlek. 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
- Where is Ysaline now?
- Ysaline (Ro-ro ship, Malta flag) was last seen on AIS on Oct 2, 2026, 15:01 UTC, moored, near Maassluis (North Sea). The crew-entered destination was NLRTM (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 14:29 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Ysaline?
- Ysaline is a ro-ro ship sailing under the flag of Malta, built in 2019 by HD Hyundai Mipo.
- Who is recorded as the owner or manager of Ysaline?
- SHIPLUX XIII S.A. is recorded as ISM manager for Ysaline (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 Ysaline?
- Voydar has no matched sanctions record displayed for Ysaline from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels and the New Zealand Russia Sanctions Register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for Ysaline. Missing records do not establish whether the ship has been detained.
Neighbouring IMO numbers
IMO numbers are issued in sequence. These are the nearest numbers below and above this ship's that have a full Voydar profile.
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/9823364Using 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.