Viking Prince
Cargo ship · Norway · built 2012 · AIS Class A
In short
Viking Prince (Cargo ship, Norway flag) was last seen on AIS on , not moving, in the North Sea. Its crew-entered AIS destination is SCARABEO 8, with an ETA of Oct 3, 2026, 14:00 UTC; its reported draught is 5.6 m (voyage report via BarentsWatch AIS API, received Oct 3, 2026, 22:59 UTC). ISM manager: Eidesvik AS (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).
Current voyage: from Risavika (departed Oct 2, 2026, 23:11 UTC) to SCARABEO 8
- Vessel type
- Cargo ship
- Flag
- Norway
- Year built
- 2012
- Gross tonnage
- 5,381
- Size (length × beam)
- 90 m
- ISM manager
- Eidesvik AS
Watch this ship
Get an email when Viking Prince 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 Viking Prince.
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
- 59.8186° N, 2.6486° E
- Area
- North Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 0.4 kn
- Course
- 281°
- Heading
- 236°
Last 30 days: at least 12 port calls (Risavika).
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
- Viking Prince
- IMO numberWhat is an IMO number?
- 9596296
- MMSIWhat is an MMSI?
- 257787000
- Call signWhat is a call sign?
- LDCE
- Flag
- Norway
- Vessel type
- Cargo ship
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 5,381
- Deadweight (DWT)
- Source: Wikidata, record Q71165886. Added to Voydar on September 23, 2026. Licence: CC0 1.0.6,055 t
- Length overall
- 89.6 m
- Beam
- —
- Year built
- 2012
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 year 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 RisavikaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at RisavikaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left RisavikaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at RisavikaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left RisavikaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at RisavikaAIS-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 |
|---|---|---|---|---|
| 2025 | 5,239 t | 1,844 t | 217 days | 200 kg |
Technical efficiency: Not Applicable. 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 |
|---|---|---|---|
| Risavika NORIV | Oct 2, 2026, 06:57 UTC | Oct 2, 2026, 23:11 UTC | 16 h 14 min |
| Risavika NORIV | Sep 23, 2026, 13:46 UTC | Sep 25, 2026, 21:48 UTC | 2 d 8 h |
| Risavika NORIV | Sep 12, 2026, 07:04 UTC | Sep 16, 2026, 03:14 UTC | 3 d 20 h |
| Risavika NORIV | Sep 12, 2026, 04:43 UTC | Sep 12, 2026, 07:02 UTC | 2 h 19 min |
| Risavika NORIV | Sep 12, 2026, 03:58 UTC | Sep 12, 2026, 04:41 UTC | 43 min |
| Risavika NORIV | Sep 12, 2026, 02:49 UTC | Sep 12, 2026, 03:56 UTC | 1 h 7 min |
| Risavika NORIV | Sep 11, 2026, 22:13 UTC | Sep 12, 2026, 02:47 UTC | 4 h 34 min |
| Risavika NORIV | Sep 11, 2026, 20:34 UTC | Sep 11, 2026, 22:11 UTC | 1 h 37 min |
| Risavika NORIV | Sep 11, 2026, 19:42 UTC | Sep 11, 2026, 20:15 UTC | 32 min |
| Risavika NORIV | Sep 11, 2026, 19:01 UTC | Sep 11, 2026, 19:42 UTC | 41 min |
| Risavika NORIV | Sep 9, 2026, 17:33 UTC | Sep 9, 2026, 18:11 UTC | 38 min |
| Risavika NORIV | Sep 9, 2026, 16:36 UTC | Sep 9, 2026, 17:32 UTC | 56 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, 14:27 UTC | Alongside another ship Stayed within 183 m of STRIL POLAR at low speed for 2 h 30 min, 127 km from the nearest port and outside known anchorages. A candidate ship-to-ship transfer; many such meetings are routine and licensed. STRIL POLAR →Method seadar.behaviour.sts_candidate v1 | Medium (55%) |
| Sep 25, 2026, 21:13 UTC | Draught change Reported draught went from 6.3 m to 5.6 m while in port at Risavika. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
Source: BarentsWatch AIS API. Contains data under NLOD made available by BarentsWatch. Licence: NLOD 2.0 (probable).
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 Viking Prince now?
- Viking Prince (Cargo ship, Norway flag) was last seen on AIS on Oct 3, 2026, 23:04 UTC, not moving, in the North Sea. The crew-entered destination was SCARABEO 8 (voyage report via BarentsWatch AIS API, received Oct 3, 2026, 22:59 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Viking Prince?
- Viking Prince is a cargo ship sailing under the flag of Norway, built in 2012 by Kleven Verft. The vessel is 89.6 m long and has a gross tonnage of 5,381.
- Who is recorded as the owner or manager of Viking Prince?
- Eidesvik AS is recorded as ISM manager for Viking Prince (source: EU MRV (THETIS-MRV) emissions; reporting year 2025). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for Viking Prince?
- Voydar has no matched sanctions record displayed for Viking Prince 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 Prince. Missing records do not establish whether the ship has been detained.
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/9596296Using 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.