Opaline
Ro-ro ship · Malta · built 2010 · AIS Class A
In short
Opaline (Ro-ro ship, Malta flag) was last seen on AIS on , moored, in the port of Zeebrugge. Its crew-entered AIS destination is GBTEE (Teesport), with an ETA of Nov 17, 2026, 14:00 UTC; its reported draught is 6.3 m (voyage report via AISstream.io global terrestrial AIS, received Nov 16, 2026, 15:23 UTC). It arrived there on Nov 15, 2026, 18:44 UTC. ISM manager: SHIPLUX III S.A. (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
- Vessel type
- Ro-ro ship
- Flag
- Malta
- Year built
- 2010
- Gross tonnage
- 33,960
- Size (length × beam)
- 195 m
- ISM manager
- SHIPLUX III S.A.

Last reported position: 51.3436° N, 3.222° E · North Sea · See on the map
Shipping a car on this vessel?
Follow Opaline and Voydar's daily email tells you when it has reached Teesport, and when it leaves or changes its destination.
What you would have been told
Following Opaline over the last 24 hours would have sent 1 message.
- ArrivedZeebrugge
Detected from AIS, as of Nov 16, 2026, 15:34 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for Opaline 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: Voydar for iPhone
Last reported position
received- Position
- 51.3436° N, 3.222° E
- Area
- North Sea
- Status
- MooredWhat do AIS statuses mean?
- Speed
- 0.1 kn
- Course
- 3°
- Heading
- 257°
- Compass: course over ground 3°, heading 257°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: at least 12 port calls (Zeebrugge and Teesport).
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 195.4 mone tick every 25 m
- Name
- Opaline
- IMO numberWhat is an IMO number?
- 9424869
- MMSIWhat is an MMSI?
- 248701000
- Call signWhat is a call sign?
- 9HA2478
- Flag
- Malta
- AIS ship type
- Cargo (hazardous cat. A)
- Gross tonnageGross tonnage vs deadweight
- 33,960
- Length overall
- 195.4 m
- Beam (AIS-reported)
- Broadcast by the ship over AIS, not a register entry. Received via AISstream.io global terrestrial AIS on November 16, 2026.26 m
- Year built
- 2010
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 16, 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 |
|---|---|---|
| Arrived at ZeebruggeAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left TeesportAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at TeesportAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left ZeebruggeAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at ZeebruggeAIS-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 | 25,402 t | 8,053 t | 221 days | 350 kg |
| 2020 | 22,458 t | 7,125 t | 186 days | 357 kg |
| 2021 | 26,236 t | 8,343 t | 231 days | 318 kg |
| 2022 | 21,974 t | 6,984 t | 195 days | 330 kg |
| 2023 | 23,390 t | 7,433 t | 207 days | 326 kg |
| 2024 | 21,420 t | 6,795 t | 190 days | 327 kg |
| 2025 | 17,695 t | 5,606 t | 167 days | 324 kg |
Technical efficiency: EEXI (11.8 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 mile66.46 g per tonne-nautical mile
- Lowest reportedHighest reported
24% 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 sailed323.9 kg per nautical mile
- Lowest reportedHighest reported
49% 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 |
|---|---|---|---|
| Zeebrugge BEZEE | Nov 15, 2026, 18:44 UTC | in port | — |
| Teesport GBTEE | Nov 14, 2026, 13:09 UTC | Nov 14, 2026, 23:37 UTC | 10 h 28 min |
| Zeebrugge BEZEE | Nov 13, 2026, 12:42 UTC | Nov 13, 2026, 20:19 UTC | 7 h 38 min |
| Teesport GBTEE | Nov 12, 2026, 13:52 UTC | Nov 12, 2026, 21:08 UTC | 7 h 17 min |
| Zeebrugge BEZEE | Nov 11, 2026, 12:14 UTC | Nov 11, 2026, 20:33 UTC | 8 h 19 min |
| Teesport GBTEE | Nov 10, 2026, 13:09 UTC | Nov 10, 2026, 21:00 UTC | 7 h 51 min |
| Zeebrugge BEZEE | Nov 8, 2026, 18:14 UTC | Nov 9, 2026, 20:06 UTC | 25 h 51 min |
| Teesport GBTEE | Nov 7, 2026, 13:32 UTC | Nov 7, 2026, 23:17 UTC | 9 h 45 min |
| Zeebrugge BEZEE | Nov 6, 2026, 12:11 UTC | Nov 6, 2026, 20:24 UTC | 8 h 14 min |
| Teesport GBTEE | Nov 5, 2026, 13:51 UTC | Nov 5, 2026, 21:03 UTC | 7 h 13 min |
| Zeebrugge BEZEE | Nov 4, 2026, 12:43 UTC | Nov 4, 2026, 20:05 UTC | 7 h 22 min |
| Teesport GBTEE | Nov 3, 2026, 13:22 UTC | Nov 3, 2026, 21:02 UTC | 7 h 41 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 14, 2026, 13:54 UTC | Draught change Reported draught went from 7 m to 6.5 m while in port at Teesport. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 13, 2026, 19:48 UTC | Draught change Reported draught went from 6.5 m to 7 m while in port at Zeebrugge. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 9, 2026, 19:15 UTC | Draught change Reported draught went from 6.2 m to 6.8 m while in port at Zeebrugge. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 7, 2026, 21:25 UTC | Draught change Reported draught went from 6.8 m to 6.2 m while in port at Teesport. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 31, 2026, 21:32 UTC | Draught change Reported draught went from 7.1 m to 6.5 m while in port at Teesport. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 9, 2026, 19:46 UTC | Draught change Reported draught went from 6.6 m to 7.1 m while in port at Zeebrugge. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 28, 2026, 18:40 UTC | Draught change Reported draught went from 6.4 m to 6.9 m after leaving Zeebrugge. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Sep 26, 2026, 13:57 UTC | Draught change Reported draught went from 7.2 m to 6.6 m after leaving Zeebrugge. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Sep 25, 2026, 18:23 UTC | Draught change Reported draught went from 6.4 m to 7.2 m while in port at Zeebrugge. 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 Opaline?
- Opaline is a ro-ro ship sailing under the flag of Malta, built in 2010 by Flensburger Schiffbau-Gesellschaft. The vessel is 195.4 m long and has a gross tonnage of 33,960.
- Who is recorded as the owner or manager of Opaline?
- SHIPLUX III S.A. is recorded as ISM manager for Opaline (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 Opaline?
- Voydar has no matched sanctions record displayed for Opaline 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 Opaline. 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/9424869Cite this page
Opaline. Voydar (voydar.com). https://www.voydar.com/vessel/9424869-opaline. Retrieved November 16, 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 adds internal business use; API plans add building the data into your own products.