Skip to content

SULOEY

Ferry · Norway · built 2019 · AIS Class A

IMO9832298MMSI257054950Call signLFEZLast AIS position Oct 4, 2026, 14:33 UTC

In short

SULOEY (Ferry, Norway flag) was last seen on AIS on , under way at 11.9 kn, in the Norwegian Sea. Its crew-entered AIS destination is HAREID >SULESUND; its reported draught is 3.6 m (voyage report via BarentsWatch AIS API, received Oct 4, 2026, 14:08 UTC). It can carry up to 399 passengers (source: Wikidata).

Current voyage: from Hareid (departed Sep 30, 2026, 17:52 UTC) to HAREID >SULESUND

Vessel type
Ferry
Flag
Norway
Year built
2019
Gross tonnage
2,641
Size (length × beam)
111 m × 17 m
Registered owner
—

Watch this ship

Get an email when SULOEY 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 SULOEY.

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
62.393° N, 6.1446° E
Area
Norwegian Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
11.9 kn
Course
251°
Heading
251°
62.393° N, 6.1446° E
Open the full live map →

Last 30 days: at least 12 port calls (Hareid).

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-up

Identity & particulars

Name
SULOEY
IMO numberWhat is an IMO number?
9832298
MMSIWhat is an MMSI?
257054950
Flag
Norway
AIS ship type
Passenger
Gross tonnageGross tonnage vs deadweight
2,641
Net tonnage
792
Length overall
111 m
Beam
17 m
Year built
2019

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
Fjord1(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, 2026
Fjord1(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
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 HareidAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at HareidAIS-detectedVoydar port-call detector (AIS geofence)
Left HareidAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at HareidAIS-detectedVoydar port-call detector (AIS geofence)
Left HareidAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at HareidAIS-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
Hareid NOHRISep 22, 2026, 17:12 UTCSep 30, 2026, 17:52 UTC8 d 0 h
Hareid NOHRISep 17, 2026, 08:53 UTCSep 17, 2026, 10:02 UTC1 h 9 min
Hareid NOHRISep 16, 2026, 06:03 UTCSep 16, 2026, 07:02 UTC58 min
Hareid NOHRISep 12, 2026, 02:52 UTCSep 12, 2026, 04:31 UTC1 h 39 min
Hareid NOHRISep 11, 2026, 04:13 UTCSep 11, 2026, 05:21 UTC1 h 8 min
Hareid NOHRISep 9, 2026, 15:12 UTCSep 9, 2026, 16:21 UTC1 h 9 min
Hareid NOHRISep 9, 2026, 06:13 UTCSep 9, 2026, 08:21 UTC2 h 8 min
Hareid NOHRISep 8, 2026, 06:15 UTCSep 8, 2026, 07:22 UTC1 h 7 min
Hareid NOHRISep 8, 2026, 01:23 UTCSep 8, 2026, 02:01 UTC38 min
Hareid NOHRISep 7, 2026, 17:53 UTCSep 7, 2026, 18:31 UTC38 min
Hareid NOHRISep 7, 2026, 11:52 UTCSep 7, 2026, 12:52 UTC1 h 0 min
Hareid NOHRISep 6, 2026, 13:52 UTCSep 6, 2026, 15:01 UTC1 h 9 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 SULOEY now?
SULOEY (Ferry, Norway flag) was last seen on AIS on Oct 4, 2026, 14:33 UTC, under way at 11.9 kn, in the Norwegian Sea. The crew-entered destination was HAREID >SULESUND (voyage report via BarentsWatch AIS API, received Oct 4, 2026, 14:08 UTC). This report does not confirm the ship’s current route.
What kind of ship is SULOEY?
SULOEY is a ferry sailing under the flag of Norway, built in 2019 by Havyard Ship Technology. The vessel is 111 m long with a beam of 17 m and has a gross tonnage of 2,641.
What sanctions and inspection records does Voydar hold for SULOEY?
Voydar has no matched sanctions record displayed for SULOEY 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 SULOEY. 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/9832298
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