FURE VIKEN
Oil tanker · Sweden · AIS Class A
In short
FURE VIKEN (Oil tanker, Sweden flag) was last seen on AIS on , under way at 10.1 kn, in the Norwegian Sea. Its crew-entered AIS destination is NO HRD (Harstad), with an ETA of Oct 7, 2026, 01:00 UTC; its reported draught is 8.1 m (voyage report via BarentsWatch AIS API, received Oct 6, 2026, 11:35 UTC). ISM manager: Furetank Rederi AB (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
Current voyage: from Trondheim (departed Oct 5, 2026, 14:36 UTC) to NO HRD (Harstad)
- Vessel type
- Oil tanker
- Flag
- Sweden
- Year built
- —
- Gross tonnage
- —
- Size (length × beam)
- —
- ISM manager
- Furetank Rederi AB
Watch this ship
Get an email when FURE VIKEN reaches Harstad, and when it 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.
Last reported position
received- Position
- 66.7054° N, 11.4026° E
- Area
- Norwegian Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 10.1 kn
- Course
- 2°
- Heading
- 15°
Last 30 days: 6 port calls (Trondheim, Mongstad, Fiskarstrand, and Hamburg).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows FURE VIKEN'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-upIdentity & particulars
- Name
- FURE VIKEN
- IMO numberWhat is an IMO number?
- 9980318
- MMSIWhat is an MMSI?
- 265057000
- Call signWhat is a call sign?
- SBLJ
- Flag
- Sweden
- AIS ship type
- Tanker
- Gross tonnageGross tonnage vs deadweight
- —
- Length overall
- —
- Beam
- —
- Year built
- —
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.
- ISM manager
- Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–2025 · reported · confidence 0.9 · retrieved Oct 5, 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.
| Date | Event | Source |
|---|---|---|
| Left TrondheimAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at TrondheimAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left MongstadAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at MongstadAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left FiskarstrandAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at FiskarstrandAIS-detected | Voydar 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.
Emissions & fuel consumption
Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.
| Year | CO₂ emitted | Fuel burned | Time at sea | CO₂ / n mile |
|---|---|---|---|---|
| 2024 | 2,694 t | 884 t | 68 days | 157 kg |
| 2025 | 5,023 t | 1,708 t | 138 days | 148 kg |
Technical efficiency: EEDI (5.16 gCO₂/t·nm). 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
| Port | Arrived | Departed | Time in port |
|---|---|---|---|
| Trondheim NOTRD | Oct 5, 2026, 00:30 UTC | Oct 5, 2026, 14:36 UTC | 14 h 6 min |
| Mongstad NOMON | Oct 2, 2026, 22:39 UTC | Oct 4, 2026, 02:18 UTC | 27 h 39 min |
| Fiskarstrand NOFST | Oct 1, 2026, 06:02 UTC | Oct 1, 2026, 16:19 UTC | 10 h 17 min |
| Mongstad NOMON | Sep 28, 2026, 09:03 UTC | Sep 30, 2026, 17:36 UTC | 2 d 8 h |
| Hamburg DEHAM | Sep 25, 2026, 11:27 UTC | Sep 26, 2026, 13:34 UTC | 26 h 6 min |
| Mongstad NOMON | Sep 16, 2026, 10:33 UTC | Sep 17, 2026, 08:15 UTC | 21 h 42 min |
| Mongstad NOMON | Aug 15, 2026, 02:09 UTC | Aug 16, 2026, 10:38 UTC | 32 h 28 min |
| Mongstad NOMON | Aug 3, 2026, 15:37 UTC | Aug 5, 2026, 20:42 UTC | 2 d 5 h |
| Mongstad NOMON | Jul 22, 2026, 15:52 UTC | Aug 3, 2026, 15:10 UTC | 11 d 23 h |
| Mongstad NOMON | Jul 11, 2026, 21:09 UTC | Jul 13, 2026, 19:33 UTC | 46 h 24 min |
| Mongstadbase NOMOB | Jun 30, 2026, 13:46 UTC | Jul 2, 2026, 09:30 UTC | 43 h 44 min |
| Mongstad NOMON | Jun 20, 2026, 16:22 UTC | Jun 21, 2026, 17:37 UTC | 25 h 15 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.
| When | What we observed | Confidence |
|---|---|---|
| Oct 4, 2026, 01:33 UTC | Draught change Reported draught went from 6.3 m to 8.4 m while in port at Mongstad. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Oct 2, 2026, 06:55 UTC | Draught change Reported draught went from 9.1 m to 6.7 m after leaving Fiskarstrand. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 29, 2026, 15:16 UTC | Draught change Reported draught went from 6.8 m to 9.4 m while in port at Mongstad. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Sep 26, 2026, 10:44 UTC | Draught change Reported draught went from 9.5 m to 6.8 m while in port at Hamburg. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
Source: BarentsWatch AIS API. Contains data under NLOD made available by BarentsWatch. Licence: NLOD 2.0 (probable).
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.
Frequently asked questions
- Where is FURE VIKEN now?
- FURE VIKEN (Oil tanker, Sweden flag) was last seen on AIS on Oct 6, 2026, 12:04 UTC, under way at 10.1 kn, in the Norwegian Sea. The crew-entered destination was NO HRD (voyage report via BarentsWatch AIS API, received Oct 6, 2026, 11:35 UTC). This report does not confirm the ship’s current route.
- What kind of ship is FURE VIKEN?
- FURE VIKEN is an oil tanker sailing under the flag of Sweden.
- Who is recorded as the owner or manager of FURE VIKEN?
- Furetank Rederi AB is recorded as ISM manager for FURE VIKEN (source: EU MRV (THETIS-MRV) emissions; reporting years 2024–2025). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for FURE VIKEN?
- Voydar has no matched sanctions record displayed for FURE VIKEN 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 FURE VIKEN. 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/9980318Using 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.