Skip to content

HORGEFJORD

Ferry · Norway · built 2018 · AIS Class A

IMO9826964MMSI257036840Call signLEWFLast AIS position Oct 1, 2026, 21:29 UTC

In short

HORGEFJORD (Ferry, Norway flag) was last seen on AIS on , moored, in the port of Torangsvag. Its crew-entered AIS destination is HUFTHAMAR-KROKEIDE (voyage report via BarentsWatch AIS API, received Oct 1, 2026, 21:20 UTC). It arrived there on Oct 1, 2026, 18:18 UTC. It can carry up to 295 passengers (source: Wikidata).

Vessel type
Ferry
Flag
Norway
Year built
2018
Gross tonnage
3,618
Size (length × beam)
113 m × 17 m
Registered owner
—

Watch this ship

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

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.

Photo of HORGEFJORD
Photo: Cavernia · Licence: CC BY-SA 4.0 · via Wikimedia Commons

Last reported position

received
Position
60.1058° N, 5.1773° E
Area
North Sea
Speed
0 kn
Course
203°
Heading
298°
60.1058° N, 5.1773° E
Open the full live map →

Last 30 days: at least 12 port calls (Torangsvag and Hufthammar).

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
HORGEFJORD
IMO numberWhat is an IMO number?
9826964
MMSIWhat is an MMSI?
257036840
Flag
Norway
AIS ship type
Passenger
Gross tonnageGross tonnage vs deadweight
3,618
Length overall
112.5 m
Beam
17.2 m
Year built
2018

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

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
Arrived at TorangsvagAIS-detectedVoydar port-call detector (AIS geofence)
Left TorangsvagAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at TorangsvagAIS-detectedVoydar port-call detector (AIS geofence)
Left TorangsvagAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at TorangsvagAIS-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
Torangsvag NOTAVOct 1, 2026, 18:18 UTCin port—
Torangsvag NOTAVSep 30, 2026, 18:18 UTCOct 1, 2026, 04:55 UTC10 h 37 min
Torangsvag NOTAVSep 29, 2026, 18:17 UTCSep 30, 2026, 04:55 UTC10 h 37 min
Torangsvag NOTAVSep 28, 2026, 18:22 UTCSep 29, 2026, 04:55 UTC10 h 32 min
Torangsvag NOTAVSep 27, 2026, 19:49 UTCSep 28, 2026, 04:55 UTC9 h 5 min
Torangsvag NOTAVSep 25, 2026, 18:19 UTCSep 26, 2026, 06:26 UTC12 h 7 min
Hufthammar NOHHASep 23, 2026, 17:59 UTCSep 24, 2026, 04:58 UTC10 h 59 min
Torangsvag NOTAVSep 22, 2026, 18:19 UTCSep 23, 2026, 04:55 UTC10 h 37 min
Torangsvag NOTAVSep 21, 2026, 18:28 UTCSep 22, 2026, 04:22 UTC9 h 53 min
Torangsvag NOTAVSep 20, 2026, 19:51 UTCSep 21, 2026, 04:22 UTC8 h 32 min
Torangsvag NOTAVSep 12, 2026, 18:20 UTCSep 13, 2026, 07:16 UTC12 h 55 min
Torangsvag NOTAVSep 10, 2026, 18:18 UTCSep 11, 2026, 04:40 UTC10 h 22 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 HORGEFJORD now?
HORGEFJORD (Ferry, Norway flag) was last seen on AIS on Oct 1, 2026, 21:29 UTC, moored, in the port of Torangsvag. The crew-entered destination was HUFTHAMAR-KROKEIDE (voyage report via BarentsWatch AIS API, received Oct 1, 2026, 21:20 UTC). This report does not confirm the ship’s current route.
What kind of ship is HORGEFJORD?
HORGEFJORD is a ferry sailing under the flag of Norway, built in 2018 by Tersan Shipyard. The vessel is 112.5 m long with a beam of 17.2 m and has a gross tonnage of 3,618.
What sanctions and inspection records does Voydar hold for HORGEFJORD?
Voydar has no matched sanctions record displayed for HORGEFJORD 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 HORGEFJORD. 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/9826964
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