Skip to content

STAVANGERFJORD

Ferry · Denmark · built 2013 · AIS Class A

IMO9586605MMSI219347000Call signOYOW2Last AIS position Oct 6, 2026, 18:41 UTC

In short

STAVANGERFJORD (Ferry, Denmark flag) was last seen on AIS on , under way at 18.9 kn, in the North Sea. Its crew-entered AIS destination is KRISTIANSAND, with an ETA of Oct 6, 2026, 21:00 UTC; its reported draught is 6.5 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 18:40 UTC). Registered owner: Fjord Line (source: Wikidata).

Current voyage: from Kristiansand (departed Oct 6, 2026, 12:39 UTC) to KRISTIANSAND

Vessel type
Ferry
Year built
2013
Gross tonnage
32,491
Size (length × beam)
170 m × 33 m
Registered owner
Fjord Line

Watch this ship

Get an email when STAVANGERFJORD arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.

Free forever. No card. A free account follows up to 5 ships and ports.

Photo of STAVANGERFJORD
Photo: Trondheim Havn · Licence: CC BY-SA 2.0 · via Wikimedia Commons

Last reported position

received
Position
57.7799° N, 9.267° E
Area
North Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
18.9 kn
Course
295°
Heading
292°
57.7799° N, 9.267° E
Open the full live map →

Last 30 days: at least 12 port calls (Kristiansand, Tananger, Bergen, and Hirtshals).

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. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name
STAVANGERFJORD
IMO numberWhat is an IMO number?
9586605
MMSIWhat is an MMSI?
219347000
Call signWhat is a call sign?
OYOW2
AIS ship type
Passenger
Gross tonnageGross tonnage vs deadweight
32,491
Length overall
170 m
Beam
32.9 m
Year built
2013

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 · 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 Oct 5, 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.

DateEventSource
Left KristiansandAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at KristiansandAIS-detectedVoydar port-call detector (AIS geofence)
Left TanangerAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at TanangerAIS-detectedVoydar port-call detector (AIS geofence)
Left BergenAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at BergenAIS-detectedVoydar 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.

YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
201843,392 t15,638 t304 days329 kg
201943,650 t15,718 t310 days327 kg
202030,647 t10,979 t242 days311 kg
202135,728 t12,851 t291 days299 kg
202228,749 t10,224 t241 days290 kg
202438,531 t14,063 t297 days306 kg
202540,646 t14,913 t308 days308 kg

Technical efficiency: EEXI (21.19 gCO₂/t·nm). 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

PortArrivedDepartedTime in port
Kristiansand NOKRSOct 6, 2026, 11:26 UTCOct 6, 2026, 12:39 UTC1 h 13 min
Tananger NOTAEOct 5, 2026, 17:26 UTCOct 5, 2026, 19:29 UTC2 h 3 min
Bergen NOBGOOct 5, 2026, 10:56 UTCOct 5, 2026, 12:10 UTC1 h 14 min
Tananger NOTAEOct 5, 2026, 04:55 UTCOct 5, 2026, 05:43 UTC49 min
Kristiansand NOKRSOct 4, 2026, 21:06 UTCOct 4, 2026, 21:48 UTC42 min
Kristiansand NOKRSOct 4, 2026, 11:25 UTCOct 4, 2026, 12:38 UTC1 h 13 min
Tananger NOTAEOct 3, 2026, 17:25 UTCOct 3, 2026, 19:27 UTC2 h 1 min
Bergen NOBGOOct 3, 2026, 10:54 UTCOct 3, 2026, 12:12 UTC1 h 17 min
Tananger NOTAEOct 3, 2026, 04:52 UTCOct 3, 2026, 05:45 UTC53 min
Hirtshals DKHIROct 2, 2026, 16:24 UTCOct 2, 2026, 17:28 UTC1 h 4 min
Kristiansand NOKRSOct 2, 2026, 11:21 UTCOct 2, 2026, 12:38 UTC1 h 17 min
Bergen NOBGOOct 1, 2026, 10:59 UTCOct 1, 2026, 12:18 UTC1 h 19 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.

Predicted arrival

Voydar estimates arrival at Risavika around Oct 9, 2026, 03:50 UTC, most likely between Oct 7, 2026, 00:03 UTC and Oct 12, 2026, 21:15 UTC. Based on 164 past transits between NOTAE and Risavika seen in our port calls. The crew-reported ETA is Oct 5, 2026, 17:30 UTC.

Medium (65%) · Method seadar.behaviour.eta_prediction v1

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.

How these are computed →

About STAVANGERFJORD

MS Stavangerfjord is a Danish registered cruiseferry operated by Norwegian ferry operator Fjord Line. The vessel operates between Hirtshals, Stavanger, Bergen and Langesund. It is the first cruise ferry in the world powered exclusively by liquefied natural gas.

Summary from Wikipedia, licensed CC BY-SA.

Frequently asked questions

Where is STAVANGERFJORD now?
STAVANGERFJORD (Ferry, Denmark flag) was last seen on AIS on Oct 6, 2026, 18:41 UTC, under way at 18.9 kn, in the North Sea. The crew-entered destination was KRISTIANSAND (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 18:40 UTC). This report does not confirm the ship’s current route.
What kind of ship is STAVANGERFJORD?
STAVANGERFJORD is a ferry sailing under the flag of Denmark, built in 2013 by Fosen Yard. The vessel is 170 m long with a beam of 32.9 m and has a gross tonnage of 32,491.
Who is recorded as the owner or manager of STAVANGERFJORD?
Fjord Line is recorded as Registered owner for STAVANGERFJORD (source: Wikidata). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for STAVANGERFJORD?
Voydar has no matched sanctions record displayed for STAVANGERFJORD 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 STAVANGERFJORD. 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/9586605
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

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.

See plans