Skip to content

KV BERGEN

Law enforcement vessel · Norway · built 2010 · AIS Class A

IMO9389368MMSI257492000Call signLAQMLast AIS position Oct 4, 2026, 18:37 UTC
Open in Terminal

In short

KV BERGEN (Law enforcement vessel, Norway flag) was last seen on AIS on , moored, in the North Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its crew-entered AIS destination is LAW ENFORCEMENT; its reported draught is 6 m (voyage report via BarentsWatch AIS API, received Oct 4, 2026, 18:25 UTC).

Current voyage: from Langoya (departed Sep 21, 2026, 19:53 UTC) to LAW ENFORCEMENT

Vessel type
Law enforcement vessel
Flag
Norway
Year built
2010
Gross tonnage
4,025
Size (length × beam)
93 m
Registered owner
—

Watch this ship

KV BERGEN has not been received for a while. Follow it and we will email you as soon as it is heard again, then when it reaches or leaves port.

Free forever. No card. A free account follows up to 5 ships and ports.

Photo of KV BERGEN
Photo: Oljeindustriens Landsforening · Licence: CC BY-SA 2.0 · via Wikimedia Commons

Last reported position

received
Position
60.3348° N, 5.2192° E
Area
North Sea
Speed
0 kn
Course
241°
Heading
0°
60.3348° N, 5.2192° E
Open the full live map →

Last 30 days: 5 port calls (Langoya, Re, Heroya, Egersund, and Langevag).

Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.

Pro shows KV BERGEN's track before the last 30 days. Voydar has recorded its port calls since July 27, 2026.Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name
KV BERGEN
IMO numberWhat is an IMO number?
9389368
MMSIWhat is an MMSI?
257492000
Call signWhat is a call sign?
LAQM
Flag
Norway
Vessel type
Law enforcement vessel
AIS ship type
Law enforcement
Gross tonnageGross tonnage vs deadweight
4,025
Length overall
93 m
Beam
—
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.

Builder
Myklebust Verft
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 LangoyaAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at LangoyaAIS-detectedVoydar port-call detector (AIS geofence)
Left ReAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at ReAIS-detectedVoydar port-call detector (AIS geofence)
Left HeroyaAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at HeroyaAIS-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
Langoya NOLAOSep 21, 2026, 16:52 UTCSep 21, 2026, 19:53 UTC3 h 1 min
Re NOREESep 21, 2026, 07:12 UTCSep 21, 2026, 08:22 UTC1 h 9 min
Heroya NOHRYSep 18, 2026, 09:00 UTCSep 19, 2026, 19:02 UTC34 h 2 min
Egersund NOEGESep 15, 2026, 15:13 UTCSep 16, 2026, 09:18 UTC18 h 5 min
Langevag NOLAGSep 12, 2026, 22:53 UTCSep 12, 2026, 23:47 UTC53 min
Florvag NOFLOSep 3, 2026, 02:22 UTCSep 11, 2026, 06:32 UTC8 d 4 h
Karsto NOKARAug 22, 2026, 18:00 UTCAug 24, 2026, 05:36 UTC35 h 36 min
Kristiansand NOKRSAug 21, 2026, 06:12 UTCAug 21, 2026, 08:26 UTC2 h 13 min
Manger NOMGRAug 12, 2026, 22:00 UTCAug 13, 2026, 08:29 UTC10 h 28 min
Trondheim NOTRDAug 4, 2026, 09:56 UTCAug 10, 2026, 03:39 UTC5 d 17 h
Muruvika NOMRVAug 4, 2026, 04:56 UTCAug 4, 2026, 05:30 UTC34 min
Hareid NOHRIJul 27, 2026, 03:14 UTCJul 27, 2026, 12:36 UTC9 h 22 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 KV BERGEN now?
KV BERGEN (Law enforcement vessel, Norway flag) was last seen on AIS on Oct 4, 2026, 18:37 UTC, moored, in the North Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was LAW ENFORCEMENT (voyage report via BarentsWatch AIS API, received Oct 4, 2026, 18:25 UTC). This report does not confirm the ship’s current route.
What kind of ship is KV BERGEN?
KV BERGEN is a law enforcement vessel sailing under the flag of Norway, built in 2010 by Myklebust Verft. The vessel is 93 m long and has a gross tonnage of 4,025.
What sanctions and inspection records does Voydar hold for KV BERGEN?
Voydar has no matched sanctions record displayed for KV BERGEN 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 KV BERGEN. 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/9389368
View JSONAPI documentationFree without a key for occasional use; use an API key for more.
Follow by RSSOpen data

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