Skip to content

SJARMOR

Fishing vessel · Norway · built 1999 · AIS Class A

IMO9207132MMSI257541600Call signLJZOLast AIS position Oct 3, 2026, 13:44 UTC

In short

SJARMOR (Fishing vessel, Norway flag) was last seen on AIS on , not moving, in the port of Eigersund. Its crew-entered AIS destination is CH 16 (voyage report via BarentsWatch AIS API, received Oct 3, 2026, 13:06 UTC). It arrived there on Oct 2, 2026, 10:29 UTC. Registered owner: NORD SOLUND FISKERISELSKAP AS (source: Fiskeridirektoratet — Fartøyregisteret (Norwegian fishing vessel register API)).

Vessel type
Fishing vessel
Flag
Norway
Year built
1999
Gross tonnage
1,192
Size (length × beam)
61 m × 11 m

Watch this ship

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

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
58.4475° N, 5.9894° E
Area
North Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
0 kn
Course
349°
Heading
43°
58.4475° N, 5.9894° E
Open the full live map →

Last 30 days: at least 12 port calls (Eigersund, Egersund, and Bergen).

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
SJARMOR
IMO numberWhat is an IMO number?
9207132
MMSIWhat is an MMSI?
257541600
Flag
Norway
Vessel type
Fishing vessel
AIS ship type
Fishing
Gross tonnageGross tonnage vs deadweight
1,192
Length overall
61 m
Beam
11 m
Year built
1999

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

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
Arrived at EigersundAIS-detectedVoydar port-call detector (AIS geofence)
Left EigersundAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at EigersundAIS-detectedVoydar port-call detector (AIS geofence)
Left EgersundAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at EgersundAIS-detectedVoydar 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

PortArrivedDepartedTime in port
Eigersund NOEGDOct 2, 2026, 10:29 UTCin port—
Eigersund NOEGDSep 29, 2026, 10:24 UTCSep 29, 2026, 16:53 UTC6 h 29 min
Egersund NOEGESep 26, 2026, 10:07 UTCSep 26, 2026, 16:31 UTC6 h 25 min
Bergen NOBGOSep 21, 2026, 02:18 UTCSep 21, 2026, 11:00 UTC8 h 42 min
Bergen NOBGOSep 20, 2026, 20:15 UTCSep 21, 2026, 02:17 UTC6 h 3 min
Bergen NOBGOSep 20, 2026, 18:04 UTCSep 20, 2026, 20:14 UTC2 h 10 min
Bergen NOBGOSep 20, 2026, 14:47 UTCSep 20, 2026, 18:04 UTC3 h 17 min
Bergen NOBGOSep 20, 2026, 02:55 UTCSep 20, 2026, 06:16 UTC3 h 22 min
Bergen NOBGOSep 20, 2026, 00:48 UTCSep 20, 2026, 02:54 UTC2 h 6 min
Bergen NOBGOSep 19, 2026, 16:45 UTCSep 20, 2026, 00:47 UTC8 h 3 min
Bergen NOBGOSep 17, 2026, 05:38 UTCSep 19, 2026, 16:44 UTC2 d 11 h
Bergen NOBGOSep 16, 2026, 06:00 UTCSep 17, 2026, 05:38 UTC23 h 38 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 SJARMOR now?
SJARMOR (Fishing vessel, Norway flag) was last seen on AIS on Oct 3, 2026, 13:44 UTC, not moving, in the port of Eigersund. The crew-entered destination was CH 16 (voyage report via BarentsWatch AIS API, received Oct 3, 2026, 13:06 UTC). This report does not confirm the ship’s current route.
What kind of ship is SJARMOR?
SJARMOR is a fishing vessel sailing under the flag of Norway, built in 1999. The vessel is 61 m long with a beam of 11 m and has a gross tonnage of 1,192.
Who is recorded as the owner or manager of SJARMOR?
NORD SOLUND FISKERISELSKAP AS is recorded as Registered owner for SJARMOR (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 SJARMOR?
Voydar has no matched sanctions record displayed for SJARMOR 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 SJARMOR. 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/9207132
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