Skip to content

OERLAND

Ferry · Norway · built 2006 · AIS Class A

IMO9371543MMSI258585000Call signLNXILast AIS position Oct 5, 2026, 04:55 UTC

In short

OERLAND (Ferry, Norway flag) was last seen on AIS on , not moving, near Moldtustranda (Norwegian Sea). Its crew-entered AIS destination is LAUVSTAD VOLDA; its reported draught is 4.8 m (voyage report via BarentsWatch AIS API, received Oct 5, 2026, 04:41 UTC). Registered owner: Norled (source: Wikidata).

Current voyage: from Volda (departed Aug 28, 2026, 19:22 UTC) to LAUVSTAD VOLDA

Vessel type
Ferry
Flag
Norway
Year built
2006
Gross tonnage
884
Size (length × beam)
63 m × 14 m
Registered owner
Norled

Watch this ship

Get an email when OERLAND 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 OERLAND
Photo: Jan-Tore Egge · Licence: CC BY-SA 4.0 · via Wikimedia Commons

Last reported position

received
Position
62.165° N, 5.9424° E
Area
Norwegian Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
0 kn
Course
172°
Heading
170°
62.165° N, 5.9424° E
Open the full live map →

Voydar detected no port call in the last 30 days.

Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.

Pro shows OERLAND's track before the last 30 days. Voydar has recorded its port calls since July 10, 2026.Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name
OERLAND
IMO numberWhat is an IMO number?
9371543
MMSIWhat is an MMSI?
258585000
Flag
Norway
AIS ship type
Passenger
Length overall
62.9 m
Beam
13.7 m
Year built
2006

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

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
Volda NOVDAAug 28, 2026, 17:46 UTCAug 28, 2026, 19:22 UTC1 h 36 min
Volda NOVDAAug 27, 2026, 20:17 UTCAug 27, 2026, 21:22 UTC1 h 5 min
Volda NOVDAAug 27, 2026, 17:44 UTCAug 27, 2026, 19:22 UTC1 h 39 min
Volda NOVDAAug 27, 2026, 09:48 UTCAug 27, 2026, 10:53 UTC1 h 5 min
Volda NOVDAAug 3, 2026, 06:45 UTCAug 3, 2026, 07:52 UTC1 h 7 min
Volda NOVDAAug 2, 2026, 15:25 UTCAug 2, 2026, 17:02 UTC1 h 37 min
Volda NOVDAJul 28, 2026, 04:19 UTCJul 28, 2026, 05:52 UTC1 h 33 min
Volda NOVDAJul 25, 2026, 20:05 UTCJul 25, 2026, 22:10 UTC2 h 4 min
Volda NOVDAJul 25, 2026, 05:45 UTCJul 25, 2026, 06:53 UTC1 h 7 min
Volda NOVDAJul 18, 2026, 18:56 UTCJul 18, 2026, 20:22 UTC1 h 27 min
Volda NOVDAJul 10, 2026, 15:23 UTCJul 10, 2026, 16:53 UTC1 h 30 min
Volda NOVDAJul 10, 2026, 09:44 UTCJul 10, 2026, 10:52 UTC1 h 8 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 OERLAND now?
OERLAND (Ferry, Norway flag) was last seen on AIS on Oct 5, 2026, 04:55 UTC, not moving, near Moldtustranda (Norwegian Sea). The crew-entered destination was LAUVSTAD VOLDA (voyage report via BarentsWatch AIS API, received Oct 5, 2026, 04:41 UTC). This report does not confirm the ship’s current route.
What kind of ship is OERLAND?
OERLAND is a ferry sailing under the flag of Norway, built in 2006 by Fiskerstrand Verft. The vessel is 62.9 m long with a beam of 13.7 m and has a gross tonnage of 884.
Who is recorded as the owner or manager of OERLAND?
Norled is recorded as Registered owner for OERLAND (source: Wikidata). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for OERLAND?
Voydar has no matched sanctions record displayed for OERLAND 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 OERLAND. 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/9371543
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