PELAGIA KYST
Tanker · Norway · built 2019 · AIS Class A
In short
PELAGIA KYST (Tanker, Norway flag) was last seen on AIS on , moored, in the port of Bogoy. Its crew-entered AIS destination is STEIGEN, with an ETA of Oct 6, 2026, 16:00 UTC; its reported draught is 3.5 m (voyage report via BarentsWatch AIS API, received Oct 6, 2026, 14:23 UTC). It arrived there on Oct 6, 2026, 14:29 UTC.
- Vessel type
- Tanker
- Flag
- Norway
- Year built
- 2019
- Gross tonnage
- —
- Size (length × beam)
- 45 m × 10 m
- Registered owner
- —
Watch this ship
Get an email when PELAGIA KYST arrives or 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
- 67.9017° N, 15.1867° E
- Area
- Norwegian Sea
- StatusWhat do AIS statuses mean?
- Moored
- Speed
- 0 kn
- Course
- 264°
- Heading
- —
Last 30 days: 11 port calls (Bogoy, Henningsvar, Lovund, Tromsdalen, Bodo, Tromso, and Nordkjosbotn).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows PELAGIA KYST's track before the last 30 days. Voydar has recorded its port calls since September 4, 2026.Free forever. No card. New accounts include 14 days of Pro.
Try the live demo, no sign-upIdentity & particulars
- Name
- PELAGIA KYST
- IMO numberWhat is an IMO number?
- 9846483
- MMSIWhat is an MMSI?
- 257061880
- Call signWhat is a call sign?
- LFQA
- Flag
- Norway
- Vessel type
- Tanker
- AIS ship type
- Tanker (hazardous cat. C)
- Gross tonnageGross tonnage vs deadweight
- —
- Length overall
- 44.7 m
- Beam
- 10.2 m
- Year built
- 2019
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
- Hordafor(not linked to a company record)Source: Wikidata · reported · confidence 0.6 · retrieved Sep 23, 2026Q118907341(not linked to a company record)Source: Wikidata · reported · confidence 0.6 · retrieved Jun 8, 2026
- Operator
- Hordafor(not linked to a company record)Source: Wikidata · reported · confidence 0.6 · retrieved Sep 23, 2026Q118907341(not linked to a company record)Source: Wikidata · reported · confidence 0.6 · retrieved Jun 8, 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 |
|---|---|---|
| Arrived at BogoyAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left HenningsvarAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at HenningsvarAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left LovundAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at LovundAIS-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 |
|---|---|---|---|
| Bogoy NOOYB | Oct 6, 2026, 14:29 UTC | in port | — |
| Henningsvar NOHEN | Oct 5, 2026, 22:51 UTC | Oct 6, 2026, 08:03 UTC | 9 h 13 min |
| Lovund NOLOV | Oct 1, 2026, 08:21 UTC | Oct 1, 2026, 12:41 UTC | 4 h 20 min |
| Tromsdalen NONZY | Sep 29, 2026, 10:32 UTC | Sep 29, 2026, 12:35 UTC | 2 h 4 min |
| Lovund NOLOV | Sep 27, 2026, 15:51 UTC | Sep 27, 2026, 19:11 UTC | 3 h 20 min |
| Bodo NOBOO | Sep 25, 2026, 14:59 UTC | Sep 25, 2026, 20:32 UTC | 5 h 33 min |
| Tromso NOTOS | Sep 22, 2026, 16:16 UTC | Sep 23, 2026, 16:29 UTC | 24 h 13 min |
| Tromso NOTOS | Sep 22, 2026, 14:17 UTC | Sep 22, 2026, 15:18 UTC | 1 h 1 min |
| Bodo NOBOO | Sep 19, 2026, 19:05 UTC | Sep 20, 2026, 12:30 UTC | 17 h 25 min |
| Bodo NOBOO | Sep 17, 2026, 17:36 UTC | Sep 19, 2026, 08:41 UTC | 39 h 5 min |
| Nordkjosbotn NONKB | Sep 15, 2026, 02:17 UTC | Sep 16, 2026, 06:35 UTC | 28 h 18 min |
| Salthella NOSLH | Sep 4, 2026, 19:09 UTC | Sep 7, 2026, 19:32 UTC | 3 d 0 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 PELAGIA KYST now?
- PELAGIA KYST (Tanker, Norway flag) was last seen on AIS on Oct 6, 2026, 15:09 UTC, moored, in the port of Bogoy. The crew-entered destination was STEIGEN (voyage report via BarentsWatch AIS API, received Oct 6, 2026, 14:23 UTC). This report does not confirm the ship’s current route.
- What kind of ship is PELAGIA KYST?
- PELAGIA KYST is a tanker sailing under the flag of Norway, built in 2019. The vessel is 44.7 m long with a beam of 10.2 m.
- What sanctions and inspection records does Voydar hold for PELAGIA KYST?
- Voydar has no matched sanctions record displayed for PELAGIA KYST 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 PELAGIA KYST. 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/9846483Using 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.