SOEROEYFISK
Fishing vessel · Norway · built 2010 · AIS Class A
In short
SOEROEYFISK (Fishing vessel, Norway flag) was last seen on AIS on , under way at 10.4 kn, in the Barents Sea. Its crew-entered AIS destination is CH 16 FOR INFO; its reported draught is 6 m (voyage report via BarentsWatch AIS API, received Oct 3, 2026, 14:45 UTC). Registered owner: SØRØYFISK AS (source: Fiskeridirektoratet — Fartøyregisteret (Norwegian fishing vessel register API)).
Current voyage: from Kuvika (departed Oct 2, 2026, 00:50 UTC) to CH 16 FOR INFO
- Vessel type
- Fishing vessel
- Flag
- Norway
- Year built
- 2010
- Gross tonnage
- 1,003
- Size (length × beam)
- 50 m × 12 m
- Registered owner
- SØRØYFISK AS
Watch this ship
Get an email when SOEROEYFISK 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 SOEROEYFISK.
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
- 71.1864° N, 26.6139° E
- Area
- Barents Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 10.4 kn
- Course
- 82°
- Heading
- 82°
Last 30 days: 4 port calls (Kuvika, Honningsvag, and Tufjorden).
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
- SOEROEYFISK
- IMO numberWhat is an IMO number?
- 9565429
- MMSIWhat is an MMSI?
- 259963000
- Call signWhat is a call sign?
- LLGS
- Flag
- Norway
- Vessel type
- Fishing vessel
- AIS ship type
- Fishing
- Gross tonnageGross tonnage vs deadweight
- 1,003
- Length overall
- 49.8 m
- Beam
- 12.2 m
- Year built
- 2010
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.
| Date | Event | Source |
|---|---|---|
| Left KuvikaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at KuvikaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left HonningsvagAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at HonningsvagAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left TufjordenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at TufjordenAIS-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 |
|---|---|---|---|
| Kuvika NOKUV | Oct 1, 2026, 21:18 UTC | Oct 2, 2026, 00:50 UTC | 3 h 32 min |
| Honningsvag NOHVG | Sep 27, 2026, 21:19 UTC | Sep 30, 2026, 04:18 UTC | 2 d 6 h |
| Tufjorden NOTUF | Sep 24, 2026, 23:16 UTC | Sep 25, 2026, 05:54 UTC | 6 h 39 min |
| Honningsvag NOHVG | Sep 22, 2026, 13:31 UTC | Sep 23, 2026, 13:11 UTC | 23 h 40 min |
| Kristoffervalen NOKVL | Jun 20, 2026, 18:00 UTC | Jun 28, 2026, 17:23 UTC | 7 d 23 h |
| Honningsvag NOHVG | Jun 9, 2026, 16:17 UTC | Jun 11, 2026, 08:32 UTC | 40 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.
Frequently asked questions
- Where is SOEROEYFISK now?
- SOEROEYFISK (Fishing vessel, Norway flag) was last seen on AIS on Oct 3, 2026, 14:51 UTC, under way at 10.4 kn, in the Barents Sea. The crew-entered destination was CH 16 FOR INFO (voyage report via BarentsWatch AIS API, received Oct 3, 2026, 14:45 UTC). This report does not confirm the ship’s current route.
- What kind of ship is SOEROEYFISK?
- SOEROEYFISK is a fishing vessel sailing under the flag of Norway, built in 2010 by Havyard Ship Technology. The vessel is 49.8 m long with a beam of 12.2 m and has a gross tonnage of 1,003.
- Who is recorded as the owner or manager of SOEROEYFISK?
- SØRØYFISK AS is recorded as Registered owner for SOEROEYFISK (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 SOEROEYFISK?
- Voydar has no matched sanctions record displayed for SOEROEYFISK 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 SOEROEYFISK. 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/9565429Using 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.