Corona Sea
Ro-ro ship · Portugal · built 2008 · AIS Class A
In short
Corona Sea (Ro-ro ship, Portugal flag) was last seen on AIS on , moored, near Travemunde (North Atlantic Ocean). Its crew-entered AIS destination is DELBC (Lubeck); its reported draught is 6.8 m (voyage report via AISstream.io global terrestrial AIS, received Nov 19, 2026, 05:46 UTC). ISM manager: AdMare Ship Management AB (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
Current voyage: from Hango (Hanko) (departed Nov 17, 2026, 23:51 UTC) to DELBC (Lubeck)
- Vessel type
- Ro-ro ship
- Flag
- Portugal
- Year built
- 2008
- Gross tonnage
- 25,609
- Size (length × beam)
- 187 m × 27 m
- ISM manager
- AdMare Ship Management AB

Last reported position: 53.8985° N, 10.7818° E · North Atlantic Ocean · See on the map
Shipping a car on this vessel?
Follow Corona Sea and Voydar's daily email tells you when it has reached Lubeck, and when it leaves or changes its destination.
What you would have been told
Nothing in the last 24 hours: no arrival or departure at a port. You are told the moment that changes.
Detected from AIS, as of Nov 20, 2026, 11:59 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for Corona Sea 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
- 53.8985° N, 10.7818° E
- Area
- North Atlantic Ocean
- Status
- MooredWhat do AIS statuses mean?
- Speed
- 0 kn
- Course
- 40°
- Heading
- 307°
- Compass: course over ground 40°, heading 307°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: at least 12 port calls (Hango (Hanko), Paldiski Lounasadam, and Sunila).
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 187 mone tick every 25 m
Beam 26.5 mPlan outline, to scale
- Name
- Corona Sea
- IMO numberWhat is an IMO number?
- 9357597
- MMSIWhat is an MMSI?
- 255814000
- Call signWhat is a call sign?
- CQUR
- Flag
- Portugal
- Vessel type
- Detailed type from WikidataRo-ro ship
- AIS ship type
- Cargo (hazardous cat. A)
- Gross tonnageGross tonnage vs deadweight
- 25,609
- Length overall
- 187 m
- Beam
- 26.5 m
- Year built
- 2008
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 · 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 Hango (Hanko)AIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from Hango (Hanko)Authority-reported | Digitraffic Port Call API | |
| Reported arrival at Hango (Hanko)Authority-reported | Digitraffic Port Call API | |
| Arrived at Hango (Hanko)AIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Paldiski LounasadamAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Paldiski LounasadamAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Hango (Hanko)AIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from Hango (Hanko)Authority-reported | Digitraffic Port Call API | |
| Reported arrival at Hango (Hanko)Authority-reported | Digitraffic Port Call API | |
| Arrived at Hango (Hanko)AIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from Hango (Hanko)Authority-reported | Digitraffic Port Call API | |
| Reported arrival at Hango (Hanko)Authority-reported | Digitraffic Port Call API |
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.
Incidents & investigations Authority-reported
Accident and incident reports by national investigation boards, and casualty warnings, that concern this ship. Each links to the original.
- Occurred Dec 4, 2013merchant-vessel-100-gross-tons-or-overUK MAIB investigation reports (index)The Kattegat, Scandinavia
Fire started by used vehicle's electrical defect on main deck of ro-ro cargo ferry Corona SeawaysReport published Feb 29, 2016
Location: The Kattegat, Scandinavia.
Source: UK MAIB investigation reports (index). Contains public sector information licensed under the Open Government Licence v3.0. Licence: Open Government Licence v3.0.
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 | 41,211 t | 13,197 t | 210 days | 484 kg |
| 2019 | 45,579 t | 14,597 t | 236 days | 472 kg |
| 2020 | 46,148 t | 14,779 t | 232 days | 489 kg |
| 2021 | 46,024 t | 14,737 t | 233 days | 483 kg |
| 2022 | 42,905 t | 13,740 t | 233 days | 456 kg |
| 2023 | 35,314 t | 11,305 t | 222 days | 431 kg |
| 2024 | 36,806 t | 11,782 t | 233 days | 420 kg |
| 2025 | 38,842 t | 12,555 t | 248 days | 410 kg |
Technical efficiency: EEXI (15 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 mile85.63 g per tonne-nautical mile
- Lowest reportedHighest reported
41% 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 sailed409.6 kg per nautical mile
- Lowest reportedHighest reported
77% 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 |
|---|---|---|---|
| Hango (Hanko) FIHKO | Nov 17, 2026, 17:55 UTC | Nov 17, 2026, 23:51 UTC | 5 h 56 min |
| Paldiski Lounasadam EEPLS | Nov 17, 2026, 12:22 UTC | Nov 17, 2026, 15:27 UTC | 3 h 5 min |
| Hango (Hanko) FIHKO | Nov 17, 2026, 04:50 UTC | Nov 17, 2026, 09:46 UTC | 4 h 56 min |
| Hango (Hanko) FIHKO | Nov 13, 2026, 04:49 UTC | Nov 13, 2026, 21:33 UTC | 16 h 44 min |
| Hango (Hanko) FIHKO | Nov 8, 2026, 22:40 UTC | Nov 9, 2026, 20:53 UTC | 22 h 13 min |
| Paldiski Lounasadam EEPLS | Nov 8, 2026, 16:46 UTC | Nov 8, 2026, 20:03 UTC | 3 h 17 min |
| Hango (Hanko) FIHKO | Nov 8, 2026, 07:50 UTC | Nov 8, 2026, 14:21 UTC | 6 h 31 min |
| Hango (Hanko) FIHKO | Nov 4, 2026, 09:59 UTC | Nov 4, 2026, 21:01 UTC | 11 h 2 min |
| Sunila FISUL | Nov 2, 2026, 17:40 UTC | Nov 3, 2026, 18:54 UTC | 25 h 14 min |
| Hango (Hanko) FIHKO | Nov 2, 2026, 04:49 UTC | Nov 2, 2026, 09:25 UTC | 4 h 36 min |
| Hango (Hanko) FIHKO | Oct 29, 2026, 17:58 UTC | Oct 29, 2026, 21:38 UTC | 3 h 40 min |
| Paldiski Lounasadam EEPLS | Oct 29, 2026, 12:22 UTC | Oct 29, 2026, 15:20 UTC | 2 h 58 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.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Hango (Hanko) FIHKO | Arrival | Nov 17, 2026, 18:10 UTC | Roro 2 | Digitraffic Port Call API |
| Hango (Hanko) FIHKO | Arrival | Nov 17, 2026, 05:03 UTC | Roro 2 | Digitraffic Port Call API |
| Hango (Hanko) FIHKO | Arrival | Nov 13, 2026, 05:28 UTC | Roro 1 | Digitraffic Port Call API |
| Hango (Hanko) FIHKO | Arrival | Nov 8, 2026, 22:55 UTC | Roro 2 | Digitraffic Port Call API |
| Hango (Hanko) FIHKO | Arrival | Nov 8, 2026, 07:57 UTC | Roro 2 | Digitraffic Port Call API |
| Hango (Hanko) FIHKO | Arrival | Nov 4, 2026, 10:10 UTC | Roro 2 | Digitraffic Port Call API |
| Kotka FIKTK | Arrival | Nov 2, 2026, 17:55 UTC | HIEH3 | Digitraffic Port Call API |
| Hango (Hanko) FIHKO | Arrival | Nov 2, 2026, 05:00 UTC | Roro 1 | Digitraffic Port Call API |
| Hango (Hanko) FIHKO | Arrival | Oct 29, 2026, 18:03 UTC | Roro 2 | Digitraffic Port Call API |
| Hango (Hanko) FIHKO | Arrival | Oct 29, 2026, 04:56 UTC | Roro 2 | Digitraffic Port Call API |
| Hango (Hanko) FIHKO | Arrival | Oct 24, 2026, 04:04 UTC | Roro 2 | Digitraffic Port Call API |
| Hango (Hanko) FIHKO | Arrival | Oct 20, 2026, 17:51 UTC | Roro 2 | Digitraffic Port Call API |
Records published by the authority named on each row. Earliest record for this ship: October 10, 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 20, 2026, 19:56 UTC | Draught change Reported draught went from 6 m to 6.5 m while in port at Hango (Hanko). Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 12, 2026, 07:12 UTC | Draught change Reported draught went from 6.9 m to 6.4 m while in port at Warnemunde. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
Source: Fintraffic / digitraffic.fi, license CC 4.0 BY. Licence: CC BY 4.0.
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.
About Corona Sea
Corona Seaways (formerly named Tor Corona) is a Roll-on/Roll-off Cargo ship that was built in 2008 for DFDS Seaways (Freight Division) to operate on the Tor Line. This continued until major restructuring within DFDS with the Tor Line brand being merged into DFDS Seaways. The ship was operated by DFDS Seaways until 2018 when it was moved to Transfennica and renamed Corona Sea.
Summary from Wikipedia, licensed CC BY-SA.
Frequently asked questions
- What kind of ship is Corona Sea?
- Corona Sea is a ro-ro ship sailing under the flag of Portugal, built in 2008 by CSC Jinling. The vessel is 187 m long with a beam of 26.5 m and has a gross tonnage of 25,609.
- Who is recorded as the owner or manager of Corona Sea?
- AdMare Ship Management AB is recorded as ISM manager for Corona Sea (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 Corona Sea?
- Voydar has no matched sanctions record displayed for Corona Sea 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 Corona Sea. 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/9357597Cite this page
Corona Sea. Voydar (voydar.com). https://www.voydar.com/vessel/9357597-corona-sea. 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.