NORDKAPP
Cruise ship · Norway · built 1996 · AIS Class A
In short
NORDKAPP (Cruise ship, Norway flag) was last seen on AIS on , under way at 15 kn, in the Norwegian Sea. Its crew-entered AIS destination is NO KKN (Kirkenes), with an ETA of Oct 7, 2026, 07:00 UTC; its reported draught is 5.2 m (voyage report via BarentsWatch AIS API, received Oct 4, 2026, 02:37 UTC). Its last detected port call was at Sandnessjoen: arrived Oct 4, 2026, left Oct 4, 2026. Registered owner: Hurtigruten (source: Wikidata).
- Vessel type
- Cruise ship
- Flag
- Norway
- Year built
- 1996
- Gross tonnage
- 11,386
- Size (length × beam)
- 123 m × 20 m
- Registered owner
- Hurtigruten
Watch this ship
Get an email when NORDKAPP 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 NORDKAPP.
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
- 66.1077° N, 12.7532° E
- Area
- Norwegian Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 15 kn
- Course
- 48°
- Heading
- 47°
Last 30 days: at least 12 port calls (Sandnessjoen, Bronnoysund, Vikna, Kolvereid, Kristiansund, Molde, Alesund, Maloy, Flora, and Bergen).
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
- NORDKAPP
- IMO numberWhat is an IMO number?
- 9107772
- MMSIWhat is an MMSI?
- 259330000
- Call signWhat is a call sign?
- LASQ
- Flag
- Norway
- Vessel type
- Detailed type from WikidataCruise ship
- AIS ship type
- Passenger
- Gross tonnageGross tonnage vs deadweight
- 11,386
- Length overall
- 123.3 m
- Beam
- 20 m
- Year built
- 1996
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.
- Registered owner
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
- Operator
- Source: Wikidata · since 2006 · reported · confidence 0.8 · retrieved Sep 22, 2026Source: Wikidata · 1996–2006 · reported · confidence 0.8 · retrieved Sep 22, 2026
- 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 SandnessjoenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at SandnessjoenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left BronnoysundAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at BronnoysundAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left ViknaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at ViknaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Operator: Hurtigruten (previously Ofotens og Vesteraalens Dampskibsselskab) | Voydar relationship-change derivation (derived by Voydar from Wikidata) |
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 |
|---|---|---|---|---|
| 2018 | 19,903 t | 6,208 t | 275 days | 236 kg |
| 2019 | 19,863 t | 6,196 t | 278 days | 219 kg |
| 2020 | 4,373 t | 1,364 t | 58 days | 242 kg |
| 2021 | 18,213 t | 5,681 t | 258 days | 230 kg |
| 2022 | 17,011 t | 5,306 t | 226 days | 241 kg |
| 2023 | 19,617 t | 6,119 t | 272 days | 246 kg |
| 2024 | 18,345 t | 5,722 t | 274 days | 234 kg |
| 2025 | 18,819 t | 5,870 t | 283 days | 204 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 |
|---|---|---|---|
| Sandnessjoen NOSSJ | Oct 4, 2026, 02:22 UTC | Oct 4, 2026, 03:04 UTC | 41 min |
| Bronnoysund NOBNN | Oct 3, 2026, 23:22 UTC | Oct 4, 2026, 00:05 UTC | 43 min |
| Vikna NOVKN | Oct 3, 2026, 19:40 UTC | Oct 3, 2026, 20:18 UTC | 38 min |
| Kolvereid NOKLD | Oct 3, 2026, 07:45 UTC | Oct 3, 2026, 11:10 UTC | 3 h 25 min |
| Kristiansund NOKSU | Oct 3, 2026, 00:45 UTC | Oct 3, 2026, 01:42 UTC | 56 min |
| Molde NOMOL | Oct 2, 2026, 20:45 UTC | Oct 2, 2026, 21:27 UTC | 41 min |
| Alesund NOAES | Oct 2, 2026, 15:51 UTC | Oct 2, 2026, 18:23 UTC | 2 h 32 min |
| Alesund NOAES | Oct 2, 2026, 07:39 UTC | Oct 2, 2026, 08:29 UTC | 50 min |
| Maloy NOMAY | Oct 2, 2026, 03:13 UTC | Oct 2, 2026, 03:49 UTC | 36 min |
| Flora NOFLR | Oct 2, 2026, 00:38 UTC | Oct 2, 2026, 01:28 UTC | 50 min |
| Bergen NOBGO | Oct 1, 2026, 12:35 UTC | Oct 1, 2026, 18:45 UTC | 6 h 9 min |
| Maloy NOMAY | Oct 1, 2026, 03:38 UTC | Oct 1, 2026, 04:21 UTC | 43 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.
About NORDKAPP
MS Nordkapp is a Hurtigruten ship built in 1996 by Kleven Verft AS, Norway, for Ofotens og Vesteraalens Dampskibsselskab for use in Hurtigruten ferry service along the coast of Norway. She is a sister ship of MS Polarlys and MS Nordnorge. Nordkapp is one of 11 ships that travel the Norwegian coast from Bergen to Kirkenes. MS Nordkapp (North Cape) is named after the North Cape on the island of Magerøya in Northern Norway.
Summary from Wikipedia, licensed CC BY-SA.
Frequently asked questions
- Where is NORDKAPP now?
- NORDKAPP (Cruise ship, Norway flag) was last seen on AIS on Oct 4, 2026, 03:13 UTC, under way at 15 kn, in the Norwegian Sea. The crew-entered destination was NO KKN (voyage report via BarentsWatch AIS API, received Oct 4, 2026, 02:37 UTC). This report does not confirm the ship’s current route.
- What kind of ship is NORDKAPP?
- NORDKAPP is a cruise ship sailing under the flag of Norway, built in 1996 by Kleven Verft. The vessel is 123.3 m long with a beam of 20 m and has a gross tonnage of 11,386.
- Who is recorded as the owner or manager of NORDKAPP?
- Hurtigruten is recorded as Registered owner for NORDKAPP (source: Wikidata). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for NORDKAPP?
- Voydar has no matched sanctions record displayed for NORDKAPP 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 NORDKAPP. 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/9107772Using 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.