Skip to content

FORTUNE TIDE

Cargo ship · Norway · built 2013 · AIS Class A

IMO9683659MMSI258759000Call signLGCJLast AIS position Oct 4, 2026, 06:56 UTC

In short

FORTUNE TIDE (Cargo ship, Norway flag) was last seen on AIS on , not moving, in the North Sea. Its crew-entered AIS destination is VALHALL, with an ETA of Oct 3, 2026, 07:30 UTC; its reported draught is 5.4 m (voyage report via BarentsWatch AIS API, received Oct 4, 2026, 06:46 UTC). Registered owner: Solstad Offshore (source: Wikidata, since 2016).

Current voyage: from Risavika (departed Oct 3, 2026, 11:48 UTC) to VALHALL

Vessel type
Cargo ship
Flag
Norway
Year built
2013
Gross tonnage
4,560
Size (length × beam)
86 m
Registered owner
Solstad Offshore

Watch this ship

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

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 FORTUNE TIDE
Photo: Alan Jamieson from Aberdeen, Scotland · Licence: CC BY 2.0 · via Wikimedia Commons

Last reported position

received
Position
56.272° N, 3.4027° E
Area
North Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
0.4 kn
Course
259°
Heading
230°
56.272° N, 3.4027° E
Open the full live map →

Last 30 days: 10 port calls (Risavika and Tananger).

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
FORTUNE TIDE
IMO numberWhat is an IMO number?
9683659
MMSIWhat is an MMSI?
258759000
Flag
Norway
Vessel type
Cargo ship
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
4,560
Length overall
86 m
Beam
—
Year built
2013

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 · since 2016 · reported · confidence 0.8 · retrieved Sep 22, 2026
Rem Offshore(Former)
Source: Wikidata · 2013–2016 · reported · confidence 0.8 · retrieved Sep 22, 2026
Operator
Solstad Shipping(not linked to a company record)
Source: Wikidata · reported · confidence 0.6 · retrieved Jun 8, 2026
Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
ISM manager
Source: EU MRV (THETIS-MRV) emissions · reporting year 2025 · reported · confidence 0.9 · retrieved Sep 28, 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 RisavikaAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at RisavikaAIS-detectedVoydar port-call detector (AIS geofence)
Left RisavikaAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at RisavikaAIS-detectedVoydar port-call detector (AIS geofence)
Left TanangerAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at TanangerAIS-detectedVoydar port-call detector (AIS geofence)
Owner: Solstad Offshore (previously Rem Offshore)Voydar relationship-change derivation (derived by Voydar from Wikidata)

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.

Emissions & fuel consumption

Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.

YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
20255,872 t1,832 t228 days198 kg

Technical efficiency: Not Applicable. Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.

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
Risavika NORIVOct 2, 2026, 07:45 UTCOct 3, 2026, 11:48 UTC28 h 2 min
Risavika NORIVSep 15, 2026, 17:51 UTCSep 15, 2026, 18:45 UTC54 min
Tananger NOTAESep 15, 2026, 15:00 UTCSep 15, 2026, 17:51 UTC2 h 51 min
Tananger NOTAESep 15, 2026, 12:29 UTCSep 15, 2026, 14:35 UTC2 h 6 min
Tananger NOTAESep 15, 2026, 09:50 UTCSep 15, 2026, 12:26 UTC2 h 36 min
Tananger NOTAESep 15, 2026, 09:08 UTCSep 15, 2026, 09:47 UTC39 min
Risavika NORIVSep 12, 2026, 10:14 UTCSep 12, 2026, 14:07 UTC3 h 53 min
Tananger NOTAESep 12, 2026, 08:42 UTCSep 12, 2026, 10:14 UTC1 h 32 min
Risavika NORIVSep 12, 2026, 07:06 UTCSep 12, 2026, 08:42 UTC1 h 36 min
Risavika NORIVSep 8, 2026, 14:07 UTCSep 9, 2026, 17:14 UTC27 h 7 min
Risavika NORIVAug 25, 2026, 14:21 UTCSep 8, 2026, 13:18 UTC13 d 22 h
Risavika NORIVAug 25, 2026, 12:49 UTCAug 25, 2026, 14:19 UTC1 h 30 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 27, 2026, 15:57 UTC
Alongside another ship

Stayed within 98 m of STRIL ORION at low speed for 3 h 50 min, 31 km from the nearest port and outside known anchorages. A candidate ship-to-ship transfer; many such meetings are routine and licensed.

STRIL ORION →

Method seadar.behaviour.sts_candidate v1

Medium (65%)

Source: BarentsWatch AIS API. Contains data under NLOD made available by BarentsWatch. Licence: NLOD 2.0 (probable).

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 FORTUNE TIDE now?
FORTUNE TIDE (Cargo ship, Norway flag) was last seen on AIS on Oct 4, 2026, 06:56 UTC, not moving, in the North Sea. The crew-entered destination was VALHALL (voyage report via BarentsWatch AIS API, received Oct 4, 2026, 06:46 UTC). This report does not confirm the ship’s current route.
What kind of ship is FORTUNE TIDE?
FORTUNE TIDE is a cargo ship sailing under the flag of Norway, built in 2013 by Kleven Verft. The vessel is 86 m long and has a gross tonnage of 4,560.
Who is recorded as the owner or manager of FORTUNE TIDE?
Solstad Offshore is recorded as Registered owner for FORTUNE TIDE (source: Wikidata; since 2016). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for FORTUNE TIDE?
Voydar has no matched sanctions record displayed for FORTUNE TIDE 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 FORTUNE TIDE. 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/9683659
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