BARENTS OCEAN
General cargo ship · Norway · built 1984 · AIS Class A
In short
BARENTS OCEAN (General cargo ship, Norway flag) was last seen on AIS on , moored, in the Norwegian Sea. Its crew-entered AIS destination is RODSKJAR, with an ETA of Oct 3, 2026, 09:00 UTC (voyage report via BarentsWatch AIS API, received Oct 3, 2026, 00:55 UTC).
Current voyage: from Lodingen (departed Oct 2, 2026, 14:32 UTC) to RODSKJAR
- Vessel type
- General cargo ship
- Flag
- Norway
- Year built
- 1984
- Gross tonnage
- 1,525
- Size (length × beam)
- 76 m × 11 m
- Registered owner
- —
Watch this ship
Get an email when BARENTS OCEAN 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 BARENTS OCEAN.
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.

Last reported position
received- Position
- 68.344° N, 15.4285° E
- Area
- Norwegian Sea
- StatusWhat do AIS statuses mean?
- Moored
- Speed
- 0 kn
- Course
- 54°
- Heading
- 349°
Last 30 days: 11 port calls (Lodingen, Anfinnsletta, Kjopsvik, Tromso, Alta, Fjelldal, Tytebarvika, and Bogoy).
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-upIdentity & particulars
- Name
- BARENTS OCEAN
- IMO numberWhat is an IMO number?
- 8318063
- MMSIWhat is an MMSI?
- 257080050
- Call signWhat is a call sign?
- LFYQ
- Flag
- Norway
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 1,525
- Deadweight (DWT)
- Source: Wikidata, record Q83637936. Added to Voydar on September 23, 2026. Licence: CC0 1.0.1,837 t
- Length overall
- 76.5 m
- Beam
- 11.5 m
- Year built
- 1984
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.
| Date | Event | Source |
|---|---|---|
| Left LodingenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at LodingenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left AnfinnslettaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at AnfinnslettaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left LodingenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at LodingenAIS-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.
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 |
|---|---|---|---|
| Lodingen NOLOD | Oct 2, 2026, 03:54 UTC | Oct 2, 2026, 14:32 UTC | 10 h 37 min |
| Anfinnsletta NOAFS | Oct 1, 2026, 20:34 UTC | Oct 2, 2026, 01:45 UTC | 5 h 12 min |
| Lodingen NOLOD | Oct 1, 2026, 13:55 UTC | Oct 1, 2026, 18:57 UTC | 5 h 2 min |
| Kjopsvik NOKJK | Sep 30, 2026, 21:11 UTC | Oct 1, 2026, 12:03 UTC | 14 h 52 min |
| Tromso NOTOS | Sep 28, 2026, 05:23 UTC | Sep 29, 2026, 15:40 UTC | 34 h 17 min |
| Alta NOALF | Sep 27, 2026, 07:45 UTC | Sep 27, 2026, 14:58 UTC | 7 h 13 min |
| Fjelldal NOFJL | Sep 26, 2026, 01:48 UTC | Sep 26, 2026, 08:24 UTC | 6 h 36 min |
| Fjelldal NOFJL | Sep 23, 2026, 16:06 UTC | Sep 24, 2026, 05:59 UTC | 13 h 53 min |
| Tytebarvika NOTYT | Sep 22, 2026, 17:33 UTC | Sep 23, 2026, 00:19 UTC | 6 h 47 min |
| Anfinnsletta NOAFS | Sep 12, 2026, 01:34 UTC | Sep 12, 2026, 05:00 UTC | 3 h 25 min |
| Bogoy NOOYB | Sep 11, 2026, 22:26 UTC | Sep 12, 2026, 01:33 UTC | 3 h 7 min |
| Jovik NOJOV | Aug 28, 2026, 05:46 UTC | Aug 28, 2026, 10:48 UTC | 5 h 3 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 BARENTS OCEAN now?
- BARENTS OCEAN (General cargo ship, Norway flag) was last seen on AIS on Oct 3, 2026, 00:57 UTC, moored, in the Norwegian Sea. The crew-entered destination was RODSKJAR (voyage report via BarentsWatch AIS API, received Oct 3, 2026, 00:55 UTC). This report does not confirm the ship’s current route.
- What kind of ship is BARENTS OCEAN?
- BARENTS OCEAN is a general cargo ship sailing under the flag of Norway, built in 1984 by Husumer Schiffswerft. The vessel is 76.5 m long with a beam of 11.5 m and has a gross tonnage of 1,525.
- What sanctions and inspection records does Voydar hold for BARENTS OCEAN?
- Voydar has no matched sanctions record displayed for BARENTS OCEAN 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 BARENTS OCEAN. 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/8318063Using 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.