VIKING YIDUN
Cruise ship · Norway · built 2017 · AIS Class A
In short
VIKING YIDUN (Cruise ship, Norway flag) was last seen on AIS on , under way at 12.5 kn, in the Mediterranean Sea. Its crew-entered AIS destination is GR SUD (Suda Bay), with an ETA of Nov 20, 2026, 06:00 UTC; its reported draught is 6.6 m (voyage report via AISstream.io global terrestrial AIS, received Nov 19, 2026, 18:25 UTC). It can carry up to 1,443 passengers (source: Wikidata).
Current voyage: from Piraeus (departed Nov 19, 2026, 16:58 UTC) to GR SUD (Suda Bay)
- Vessel type
- Cruise ship
- Flag
- Norway
- Year built
- 2017
- Gross tonnage
- 47,800
- Size (length × beam)
- 228 m × 29 m
- Registered owner
- —

Last reported position: 37.3808° N, 23.8152° E · Mediterranean Sea · See on the map
Travelling on VIKING YIDUN, or someone you know is?
Follow it and Voydar's daily email tells you when it has reached Suda Bay, then each port after that.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for VIKING YIDUN 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
In the news Press-reported
Reports that name VIKING YIDUN, newest first: the headline, the outlet and a link to the original. Voydar does not copy articles. A report tied to this ship by its IMO number in the text says so; a report that only prints the name is a possible match, because other ships can carry the same name.
What our data shows around Nov 7, 2026
- VIKING YIDUN’s last AIS position before the report: 45.383° N, 12.2591° E (Mediterranean Sea), received Nov 7, 2026, 19:04 UTC. AIS-detected
- VIKING YIDUN was in port at Fusina, having arrived on Nov 6, 2026.
See the position and 30-day track and the port calls below.
- corriereadriatico.itNov 7, 2026Possible match
Source: GDELT DOC 2.0 news index. News index: The GDELT Project (https://www.gdeltproject.org/). Licence: GDELT terms (unrestricted use with citation).
Headlines belong to their publishers; Voydar shows the headline and links to the original.
Last reported position
received- Position
- 37.3808° N, 23.8152° E
- Area
- Mediterranean Sea
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 12.5 kn
- Course
- 160°
- Heading
- 159°
- Compass: course over ground 160°, heading 159°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 10 port calls (Piraeus, Fusina, Napoli, Livorno, Monaco, Marseille, Tarragona, and Villefranche-sur-Saone).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows VIKING YIDUN's track before the last 30 days. Voydar has recorded its port calls since October 14, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
Length overall 228.3 mone tick every 25 m
Beam 28.8 mPlan outline, to scale
- Name
- VIKING YIDUN
- IMO numberWhat is an IMO number?
- 9725433
- MMSIWhat is an MMSI?
- 258234000
- Call signWhat is a call sign?
- LADM9
- Flag
- Norway
- Vessel type
- Cruise ship
- Gross tonnageGross tonnage vs deadweight
- 47,800
- Length overall
- 228.3 m
- Beam
- 28.8 m
- Year built
- 2017
- Passengers (maximum)
- Source: Wikidata, record Q57313095. Added to Voydar on November 17, 2026. Licence: CC0 1.0.1,443
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.
- Operator
- Source: Wikidata · since 2021 · reported · high confidence · retrieved Nov 15, 2026Viking Ocean Cruises(Former)Source: Wikidata · until 2021 · reported · high confidence · retrieved Nov 15, 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 PiraeusAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at PiraeusAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left PiraeusAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at PiraeusAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left FusinaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at FusinaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
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.
Former and other names
Names attested for this ship other than its current name.
| Name | Evidence | Date | Source |
|---|---|---|---|
| Viking Sun | Former name | — | Wikidata |
A sanctions list's date is the earliest date the list shows the name, not when the ship took it. A name on a list is shown as a former name only where AIS shows the ship using another name after that date; otherwise it is listed as a name the list uses. AIS name changes are dated when Voydar saw them.
Source: Wikidata. Licence: CC0 1.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 | 24,630 t | 7,880 t | 252 days | 554 kg |
| 2019 | 23,637 t | 7,555 t | 118 days | 840 kg |
| 2020 | 16,411 t | 5,152 t | 126 days | 1,690 kg |
Technical efficiency: EIV (9.2 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 2020 sits among the ships EU MRV lists as “Passenger ship”. Lower is less CO₂.
- CO₂ per nautical mile sailed1,690.1 kg per nautical mile
- Lowest reportedHighest reported
74% of the 105 ships in this group reported a lower figure.
Group: lower quartile 611.5 · median 1,120.9 · upper quartile 1,758.9
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 |
|---|---|---|---|
| Piraeus GRPIR | Nov 19, 2026, 04:39 UTC | Nov 19, 2026, 16:58 UTC | 12 h 19 min |
| Piraeus GRPIR | Nov 13, 2026, 04:10 UTC | Nov 13, 2026, 17:23 UTC | 13 h 14 min |
| Fusina ITFSA | Nov 6, 2026, 10:41 UTC | Nov 7, 2026, 19:19 UTC | 32 h 38 min |
| Napoli ITNAP | Nov 1, 2026, 06:09 UTC | Nov 1, 2026, 17:18 UTC | 11 h 8 min |
| Livorno ITLIV | Oct 30, 2026, 06:34 UTC | Oct 31, 2026, 03:53 UTC | 21 h 20 min |
| Monaco MCMON | Oct 29, 2026, 06:13 UTC | Oct 29, 2026, 20:24 UTC | 14 h 11 min |
| Marseille FRMRS | Oct 28, 2026, 10:52 UTC | Oct 28, 2026, 17:11 UTC | 6 h 18 min |
| Tarragona ESTAR | Oct 27, 2026, 14:57 UTC | Oct 27, 2026, 19:23 UTC | 4 h 26 min |
| Villefranche-sur-Saone FRVSS | Oct 23, 2026, 05:30 UTC | Oct 23, 2026, 17:04 UTC | 11 h 34 min |
| Livorno ITLIV | Oct 22, 2026, 07:08 UTC | Oct 22, 2026, 19:08 UTC | 12 h 0 min |
| Napoli ITNAP | Oct 20, 2026, 05:38 UTC | Oct 20, 2026, 16:12 UTC | 10 h 34 min |
| Fusina ITFSA | Oct 14, 2026, 05:01 UTC | Oct 15, 2026, 15:08 UTC | 34 h 6 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 |
|---|---|---|---|---|
| Hong Kong HKHKG | Arrival(matched by call sign) | Jan 10, 2026, 03:18 UTC | OT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Feb 14, 2025, 00:11 UTC | OT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Mar 16, 2024, 02:19 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Mar 2, 2024, 02:28 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Feb 24, 2024, 02:19 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Feb 17, 2024, 02:10 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Feb 10, 2024, 02:14 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Feb 3, 2024, 02:19 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Jan 27, 2024, 02:05 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Jan 13, 2024, 02:12 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Jan 6, 2024, 02:19 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Dec 30, 2023, 02:16 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
Records published by the authority named on each row. Earliest record for this ship: March 3, 2021.
Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.
About VIKING YIDUN
MV Viking Sun is a cruise ship operated by Viking Ocean Cruises. The fourth in a series of 930-passenger cruise ships to be built by Fincantieri for her operator, she was delivered at Fincantieri's shipyard in Ancona, Italy, on 25 September 2017. In April 2021, ownership the Viking Sun was transferred to Viking Sun Ltd. of Bermuda, for operation by China Merchants Viking Cruises, a joint venture of Viking Ocean Cruises and China Merchants Shekou Cruises. She was then transferred to Chinese registration, with port of registry Qianhai, Shenzhen, and renamed Zhao Shang Yi Dun.
Summary from Wikipedia, licensed CC BY-SA.
Frequently asked questions
- What kind of ship is VIKING YIDUN?
- VIKING YIDUN is a cruise ship sailing under the flag of Norway, built in 2017 by Fincantieri. The vessel is 228.3 m long with a beam of 28.8 m and has a gross tonnage of 47,800.
- What sanctions and inspection records does Voydar hold for VIKING YIDUN?
- Voydar has no matched sanctions record displayed for VIKING YIDUN 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 VIKING YIDUN. 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 Cruise ships
Other cruise ships with full Voydar profiles. A different set each day. All cruise 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/9725433Cite this page
VIKING YIDUN. Voydar (voydar.com). https://www.voydar.com/vessel/9725433-viking-yidun. Retrieved November 19, 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.