Skip to content

TRONDS LIFT 8

Other · Norway · built 1967 · AIS Class B

IMO6725212MMSI259029690Call signLH5979Last AIS position Oct 6, 2026, 12:46 UTC

In short

TRONDS LIFT 8 (Other, Norway flag) was last seen on AIS on , not moving, in the North Sea. Its last detected port call was at Dusavik: arrived Sep 27, 2026, left Oct 2, 2026.

Vessel type
Other
Flag
Norway
Year built
1967
Gross tonnage
904
Size (length × beam)
45 m
Registered owner
—

Watch this ship

Get an email when TRONDS LIFT 8 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 TRONDS LIFT 8
Photo: Cavernia · Licence: CC BY-SA 4.0 · via Wikimedia Commons

Last reported position

received
Position
59.789° N, 5.7907° E
Area
North Sea
StatusWhat do AIS statuses mean?
Restricted manoeuvrability
Speed
0 kn
Course
55°
Heading
—
59.789° N, 5.7907° E
Open the full live map →

Last 30 days: 7 port calls (Dusavik, Haugesund, Hoylandsbygda, Hanoytangen, and Bergen).

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

Pro shows TRONDS LIFT 8's track before the last 30 days. Voydar has recorded its port calls since June 20, 2026.Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name
TRONDS LIFT 8
IMO numberWhat is an IMO number?
6725212
MMSIWhat is an MMSI?
259029690
Call signWhat is a call sign?
LH5979
Flag
Norway
Vessel type
Other
Length overall
45 m
Beam
—
Year built
1967

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.

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 DusavikAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at DusavikAIS-detectedVoydar port-call detector (AIS geofence)
Left HaugesundAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at HaugesundAIS-detectedVoydar port-call detector (AIS geofence)
Left HoylandsbygdaAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at HoylandsbygdaAIS-detectedVoydar port-call detector (AIS geofence)
Former name: Gps AtlasWikidata
Former name: Taklift 3Wikidata
Former name: Magnus VWikidata

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.

Former and other names

Names attested for this ship other than its current name.

NameEvidenceDateSource
Gps AtlasFormer nameJan 1, 2005Wikidata
Taklift 3Former nameJan 1, 1971Wikidata
Magnus VFormer nameJan 1, 1967Wikidata

A sanctions list's date is the earliest date the list shows the name, not when the ship took it. A name on a list is shown as a former name only where AIS shows the ship using another name after that date; otherwise it is listed as a name the list uses. AIS name changes are dated when Voydar saw them.

Source: Wikidata. Licence: CC0 1.0.

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
Dusavik NODUSSep 27, 2026, 19:23 UTCOct 2, 2026, 07:33 UTC4 d 12 h
Haugesund NOHAUSep 27, 2026, 11:58 UTCSep 27, 2026, 14:19 UTC2 h 21 min
Hoylandsbygda NOHLBSep 25, 2026, 01:43 UTCSep 27, 2026, 05:48 UTC2 d 4 h
Hanoytangen NOHOTSep 22, 2026, 15:33 UTCSep 24, 2026, 10:01 UTC42 h 29 min
Bergen NOBGOSep 11, 2026, 16:11 UTCSep 22, 2026, 03:43 UTC10 d 11 h
Hoylandsbygda NOHLBSep 8, 2026, 08:06 UTCSep 10, 2026, 05:26 UTC45 h 21 min
Hoylandsbygda NOHLBSep 7, 2026, 12:28 UTCSep 8, 2026, 07:29 UTC19 h 0 min
Hordvik NOHRVJul 21, 2026, 08:03 UTCAug 12, 2026, 17:26 UTC22 d 9 h
Halsnoy NOHAZJul 16, 2026, 11:56 UTCJul 19, 2026, 07:27 UTC2 d 19 h
Haugesund NOHAUJun 20, 2026, 11:54 UTCJun 21, 2026, 05:36 UTC17 h 42 min
Haugesund NOHAUJun 20, 2026, 10:52 UTCJun 20, 2026, 11:52 UTC1 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.

Frequently asked questions

Where is TRONDS LIFT 8 now?
TRONDS LIFT 8 (Other, Norway flag) was last seen on AIS on Oct 6, 2026, 12:46 UTC, not moving, in the North Sea.
What kind of ship is TRONDS LIFT 8?
TRONDS LIFT 8 is a other sailing under the flag of Norway, built in 1967 by Howaldtswerke-Deutsche Werft. The vessel is 45 m long and has a gross tonnage of 904.
What sanctions and inspection records does Voydar hold for TRONDS LIFT 8?
Voydar has no matched sanctions record displayed for TRONDS LIFT 8 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 TRONDS LIFT 8. 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/6725212
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