STORFJORD
Ferry · Norway · built 2011 · AIS Class A
In short
STORFJORD (Ferry, Norway flag) was last seen on AIS on , under way at 6.8 kn, in the North Sea. Its crew-entered AIS destination is SLOEVAAG-LEIRVAAG; its reported draught is 3 m (voyage report via BarentsWatch AIS API, received Oct 6, 2026, 12:02 UTC). It can carry up to 292 passengers (source: Wikidata).
Current voyage: from Slovag (departed Sep 21, 2026, 03:51 UTC) to SLOEVAAG-LEIRVAAG
- Vessel type
- Ferry
- Flag
- Norway
- Year built
- 2011
- Gross tonnage
- 2,967
- Size (length × beam)
- 110 m × 17 m
- Registered owner
- —
Watch this ship
Get an email when STORFJORD 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.

Last reported position
received- Position
- 60.8536° N, 5.0646° E
- Area
- North Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 6.8 kn
- Course
- 15°
- Heading
- 5°
Last 30 days: 1 port call (Slovag).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows STORFJORD's track before the last 30 days. Voydar has recorded its port calls since June 9, 2026.Free forever. No card. New accounts include 14 days of Pro.
Try the live demo, no sign-upIdentity & particulars
- Name
- STORFJORD
- IMO numberWhat is an IMO number?
- 9528469
- MMSIWhat is an MMSI?
- 259098000
- Call signWhat is a call sign?
- LDKO
- Flag
- Norway
- Vessel type
- Detailed type from WikidataFerry
- AIS ship type
- Passenger
- Gross tonnageGross tonnage vs deadweight
- 2,967
- Length overall
- 109.5 m
- Beam
- 17 m
- Year built
- 2011
- Passengers (maximum)
- Source: Wikidata, record Q61790842. Added to Voydar on September 23, 2026. Licence: CC0 1.0.292
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, 2026Fjord1(not linked to a company record)Source: Wikidata · reported · confidence 0.6 · retrieved Jun 8, 2026
- Operator
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026Fjord1(not linked to a company record)Source: Wikidata · reported · confidence 0.6 · retrieved Jun 8, 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 SlovagAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at SlovagAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left SlovagAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at SlovagAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left SlovagAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at SlovagAIS-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.
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 |
|---|---|---|---|
| Slovag NOSLV | Sep 20, 2026, 21:36 UTC | Sep 21, 2026, 03:51 UTC | 6 h 15 min |
| Slovag NOSLV | Jul 27, 2026, 21:37 UTC | Jul 28, 2026, 03:51 UTC | 6 h 14 min |
| Slovag NOSLV | Jul 14, 2026, 12:35 UTC | Jul 14, 2026, 13:46 UTC | 1 h 11 min |
| Mongstad NOMON | Jul 6, 2026, 04:09 UTC | Jul 6, 2026, 05:47 UTC | 1 h 37 min |
| Slovag NOSLV | Jun 21, 2026, 21:43 UTC | Jun 22, 2026, 04:18 UTC | 6 h 34 min |
| Slovag NOSLV | Jun 21, 2026, 15:34 UTC | Jun 21, 2026, 16:20 UTC | 45 min |
| Slovag NOSLV | Jun 19, 2026, 17:36 UTC | Jun 19, 2026, 18:18 UTC | 42 min |
| Mongstad NOMON | Jun 13, 2026, 06:14 UTC | Jun 13, 2026, 07:03 UTC | 49 min |
| Slovag NOSLV | Jun 9, 2026, 19:47 UTC | Jun 10, 2026, 03:50 UTC | 8 h 4 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.
Frequently asked questions
- Where is STORFJORD now?
- STORFJORD (Ferry, Norway flag) was last seen on AIS on Oct 6, 2026, 12:32 UTC, under way at 6.8 kn, in the North Sea. The crew-entered destination was SLOEVAAG-LEIRVAAG (voyage report via BarentsWatch AIS API, received Oct 6, 2026, 12:02 UTC). This report does not confirm the ship’s current route.
- What kind of ship is STORFJORD?
- STORFJORD is a ferry sailing under the flag of Norway, built in 2011 by Remontowa. The vessel is 109.5 m long with a beam of 17 m and has a gross tonnage of 2,967.
- What sanctions and inspection records does Voydar hold for STORFJORD?
- Voydar has no matched sanctions record displayed for STORFJORD 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 STORFJORD. 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/9528469Using 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.