Skip to content

Hordafor VII

Tanker · Norway · built 1992 · AIS Class A

IMO9007104MMSI257054580Call signLFILLast AIS position Oct 1, 2026, 21:38 UTC

In short

Hordafor VII (Tanker, Norway flag) was last seen on AIS on , under way at 11.3 kn, in the North Sea. Its crew-entered AIS destination is ISBIL (Bildudalur - hofn), with an ETA of Oct 5, 2026, 12:00 UTC; its reported draught is 5.2 m (voyage report via BarentsWatch AIS API, received Oct 1, 2026, 21:14 UTC). Its last detected port call was at Svolvar Osan: arrived Jul 3, 2026, left Jul 3, 2026.

Vessel type
Tanker
Flag
Norway
Year built
1992
Gross tonnage
3,222
Size (length × beam)
88 m
Registered owner
—

Watch this ship

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

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 HORDAFOR VII
Photo: Cavernia · Licence: CC BY-SA 4.0 · via Wikimedia Commons

Last reported position

received
Position
60.5614° N, 3.3718° E
Area
North Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
11.3 kn
Course
306°
Heading
305°
60.5614° N, 3.3718° 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.

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
Hordafor VII
IMO numberWhat is an IMO number?
9007104
MMSIWhat is an MMSI?
257054580
Flag
Norway
Vessel type
Tanker
Gross tonnageGross tonnage vs deadweight
3,222
Length overall
87.5 m
Beam
—
Year built
1992

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
Hordafor(not linked to a company record)
Source: Wikidata · reported · confidence 0.6 · retrieved Sep 23, 2026
Q118907341(not linked to a company record)
Source: Wikidata · reported · confidence 0.6 · retrieved Jun 8, 2026
Operator
Hordafor(not linked to a company record)
Source: Wikidata · reported · confidence 0.6 · retrieved Sep 23, 2026
Q118907341(not linked to a company record)
Source: Wikidata · reported · confidence 0.6 · retrieved Jun 8, 2026
Builder
Aukra Bruk
Name on the vessel record; the original source was not recorded.

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 Svolvar OsanAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Svolvar OsanAIS-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
Svolvar Osan NOSOSJul 3, 2026, 20:39 UTCJul 3, 2026, 23:39 UTC3 h 0 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.

Behaviour at sea Voydar-derived

Patterns Voydar derived from this ship's AIS broadcasts. They are inferences, not reports: each one shows how it was computed and how confident we are, and none of them says why a ship behaved this way.

WhenWhat we observedConfidence
Sep 26, 2026, 14:38 UTC
Draught change

Reported draught went from 4.5 m to 5.2 m while in port at Fitjar. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)

Source: AISstream.io global terrestrial AIS. AIS data: AISstream.io. Licence: none published.

Derived from AIS positions of feeds whose terms allow display on Voydar. Coverage is terrestrial: gaps are reported only where our receivers kept hearing other ships. Detections below medium confidence are not shown.

How these are computed →

Frequently asked questions

Where is Hordafor VII now?
Hordafor VII (Tanker, Norway flag) was last seen on AIS on Oct 1, 2026, 21:38 UTC, under way at 11.3 kn, in the North Sea. The crew-entered destination was ISBIL (voyage report via BarentsWatch AIS API, received Oct 1, 2026, 21:14 UTC). This report does not confirm the ship’s current route.
What kind of ship is Hordafor VII?
Hordafor VII is a tanker sailing under the flag of Norway, built in 1992 by Aukra Bruk. The vessel is 87.5 m long and has a gross tonnage of 3,222.
What sanctions and inspection records does Voydar hold for Hordafor VII?
Voydar has no matched sanctions record displayed for Hordafor VII 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 Hordafor VII. 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/9007104
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