Skip to content

BARENTS SEA

Fishing vessel · Norway · built 1989 · AIS Class A

IMO8906949MMSI257388000Call signLKUALast AIS position Oct 3, 2026, 15:14 UTC

In short

BARENTS SEA (Fishing vessel, Norway flag) was last seen on AIS on , not moving, near Moldtustranda (Norwegian Sea). Its crew-entered AIS destination is BAATSFJORD; its reported draught is 6.6 m (voyage report via BarentsWatch AIS API, received Oct 3, 2026, 15:04 UTC). Its last detected port call was at Batsfjord: arrived Jun 9, 2026, left Jun 14, 2026. Registered owner: BARENTS SEA AS (source: Fiskeridirektoratet — Fartøyregisteret (Norwegian fishing vessel register API)).

Vessel type
Fishing vessel
Flag
Norway
Year built
1989
Gross tonnage
810
Size (length × beam)
45 m × 11 m
Registered owner
BARENTS SEA AS

Watch this ship

Get an email when BARENTS SEA 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 SEA.

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 BARENTS SEA
Photo: Trondheim Havn from Trondheim, Norway · Licence: CC BY-SA 2.0 · via Wikimedia Commons

Last reported position

received
Position
62.3247° N, 5.6633° E
Area
Norwegian Sea
StatusWhat do AIS statuses mean?
Under way sailing
Speed
0 kn
Course
169°
Heading
266°
62.3247° N, 5.6633° 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
BARENTS SEA
IMO numberWhat is an IMO number?
8906949
MMSIWhat is an MMSI?
257388000
Flag
Norway
Vessel type
Fishing vessel
AIS ship type
Fishing
Length overall
45 m
Year built
1989

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: Fiskeridirektoratet — Fartøyregisteret (Norwegian fishing vessel register API) · reported · confidence 0.95 · retrieved Sep 24, 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 BatsfjordAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at BatsfjordAIS-detectedVoydar port-call detector (AIS geofence)
Former name: UnityWikidata
Former name: TorbasWikidata
Former name: Ocean WayWikidata

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
UnityFormer nameJan 1, 2001Wikidata
TorbasFormer nameJan 1, 1997Wikidata
Ocean WayFormer nameJan 1, 1989Wikidata

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
Batsfjord NOBJFJun 9, 2026, 19:04 UTCJun 14, 2026, 00:40 UTC4 d 5 h

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 SEA now?
BARENTS SEA (Fishing vessel, Norway flag) was last seen on AIS on Oct 3, 2026, 15:14 UTC, not moving, near Moldtustranda (Norwegian Sea). The crew-entered destination was BAATSFJORD (voyage report via BarentsWatch AIS API, received Oct 3, 2026, 15:04 UTC). This report does not confirm the ship’s current route.
What kind of ship is BARENTS SEA?
BARENTS SEA is a fishing vessel sailing under the flag of Norway, built in 1989 by Flekkefjord Slipp & Maskinfabrikk AS. The vessel is 45 m long with a beam of 11 m and has a gross tonnage of 810.
Who is recorded as the owner or manager of BARENTS SEA?
BARENTS SEA AS is recorded as Registered owner for BARENTS SEA (source: Fiskeridirektoratet — Fartøyregisteret (Norwegian fishing vessel register API)). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for BARENTS SEA?
Voydar has no matched sanctions record displayed for BARENTS SEA 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 BARENTS SEA. 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/8906949
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