Moldefjord
Ferry · Norway · built 2009 · AIS Class A
In short
Moldefjord (Ferry, Norway flag) was last seen on AIS on , moored, in the Norwegian Sea. Its crew-entered AIS destination is HALSA-KANESTRAUM; its reported draught is 5.5 m (voyage report via BarentsWatch AIS API, received Oct 3, 2026, 00:19 UTC). It can carry up to 390 passengers (source: Wikidata).
Current voyage: from Halsa (departed Sep 21, 2026, 07:21 UTC) to HALSA-KANESTRAUM
- Vessel type
- Ferry
- Flag
- Norway
- Year built
- 2009
- Gross tonnage
- 2,971
- Size (length × beam)
- 122 m
- Registered owner
- —
Watch this ship
Get an email when Moldefjord 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 Moldefjord.
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
- 63.0676° N, 8.2269° E
- Area
- Norwegian Sea
- StatusWhat do AIS statuses mean?
- Moored
- Speed
- 0 kn
- Course
- 119°
- Heading
- 27°
Last 30 days: 1 port call (Halsa).
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
- Moldefjord
- IMO numberWhat is an IMO number?
- 9477115
- MMSIWhat is an MMSI?
- 258327500
- Call signWhat is a call sign?
- LCBA
- Flag
- Norway
- Vessel type
- Detailed type from WikidataFerry
- AIS ship type
- Passenger
- Gross tonnageGross tonnage vs deadweight
- 2,971
- Length overall
- 122 m
- Beam
- —
- Year built
- 2009
- Passengers (maximum)
- Source: Wikidata, record Q52379598. Added to Voydar on September 23, 2026. Licence: CC0 1.0.390
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 HalsaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at HalsaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left HalsaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at HalsaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left HalsaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at HalsaAIS-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 |
|---|---|---|---|
| Halsa NOHLS | Sep 20, 2026, 19:08 UTC | Sep 21, 2026, 07:21 UTC | 12 h 13 min |
| Halsa NOHLS | Aug 28, 2026, 19:07 UTC | Aug 29, 2026, 07:51 UTC | 12 h 44 min |
| Halsa NOHLS | Aug 21, 2026, 17:15 UTC | Aug 22, 2026, 06:56 UTC | 13 h 41 min |
| Halsa NOHLS | Aug 7, 2026, 16:34 UTC | Aug 7, 2026, 17:24 UTC | 49 min |
| Halsa NOHLS | Aug 7, 2026, 16:01 UTC | Aug 7, 2026, 16:33 UTC | 32 min |
| Halsa NOHLS | Jul 16, 2026, 19:08 UTC | Jul 17, 2026, 08:24 UTC | 13 h 16 min |
| Halsa NOHLS | Jul 10, 2026, 09:23 UTC | Jul 10, 2026, 10:52 UTC | 1 h 29 min |
| Halsa NOHLS | Jun 22, 2026, 10:19 UTC | Jun 22, 2026, 12:59 UTC | 2 h 39 min |
| Halsa NOHLS | Jun 21, 2026, 16:41 UTC | Jun 22, 2026, 08:53 UTC | 16 h 12 min |
| Halsa NOHLS | Jun 16, 2026, 17:10 UTC | Jun 16, 2026, 17:52 UTC | 42 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 Moldefjord now?
- Moldefjord (Ferry, Norway flag) was last seen on AIS on Oct 3, 2026, 00:41 UTC, moored, in the Norwegian Sea. The crew-entered destination was HALSA-KANESTRAUM (voyage report via BarentsWatch AIS API, received Oct 3, 2026, 00:19 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Moldefjord?
- Moldefjord is a ferry sailing under the flag of Norway, built in 2009 by Remontowa. The vessel is 122 m long and has a gross tonnage of 2,971.
- What sanctions and inspection records does Voydar hold for Moldefjord?
- Voydar has no matched sanctions record displayed for Moldefjord from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels and the New Zealand Russia Sanctions Register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for Moldefjord. 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/9477115Using 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.