Skip to content
voydar.com

HAGLAND PREMIER

Naval vessel · Norway · AIS Class A

IMO9964077MMSI257415000Call signLAUB8Last AIS position Nov 20, 2026, 17:58 UTC

In short

HAGLAND PREMIER (Naval vessel, Norway flag) was last seen on AIS on , under way at 10.6 kn, in the North Sea. Its crew-entered AIS destination is NO RUB (Rubbestadneset), with an ETA of Nov 20, 2026, 22:30 UTC; its reported draught is 3.5 m (voyage report via BarentsWatch AIS API, received Nov 20, 2026, 17:56 UTC). ISM manager: Hagland Shipping AS (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).

Current voyage: from Boneset - Karmoy (departed Nov 20, 2026, 17:29 UTC) to NO RUB (Rubbestadneset)

Data delivered by BarentsWatch

Vessel type
Naval vessel
Flag
Norway
Year built
—
Gross tonnage
—
Size, AIS-reported (length × beam)
87 m × 15 m

Last reported position: 59.5172° N, 5.2177° E · North Sea · See on the map

Watch this ship

Get an email when HAGLAND PREMIER reaches Rubbestadneset, and when it leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.

What you would have been told

Following HAGLAND PREMIER over the last 24 hours would have sent 3 messages.

Detected from AIS, as of Nov 20, 2026, 17:59 UTC.

Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for HAGLAND PREMIER reach you the moment they happen, arrival-time changes included. When it ends you stay on Free, with a daily email, unless you keep Plus (US$7 a month). Compare plans

Get alerts on your phone: the Voydar app

Last reported position

received
Position
59.5172° N, 5.2177° E
Area
North Sea
Status
Under way using engineWhat do AIS statuses mean?
Speed
10.6 kn
Course
2°
Heading
3°
Compass: course over ground 2°, heading 3°
NArrow: course. Hull: heading. As broadcast on AIS.
59.5172° N, 5.2177° E. Reference map only, not for navigation.
Locator map: Natural Earth (public domain)
59.5172° N, 5.2177° E
See it live in 3D →

Last 30 days: at least 12 port calls (Boneset - Karmoy, Stavanger, Fredrikstad, Sandvik, Styrso, Tyboron, Cuxhaven, Eydehavn, Hundested, Lillesand, Langoya, Straume, and Nordhavn).

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

Data delivered by BarentsWatch

A year of history in the Terminal (Plus) · the full archive since June 1, 2026 (Pro)Free forever. No card. Follow a ship and Plus is free for 14 days.

Try the live demo, no sign-up

Identity & particulars

Name
HAGLAND PREMIER
IMO numberWhat is an IMO number?
9964077
MMSIWhat is an MMSI?
257415000
Call signWhat is a call sign?
LAUB8
Flag
Norway
Vessel type
Naval vessel
Year built
—

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.

AIS-reported: the size the ship itself broadcasts over AIS, in whole metres, as entered on board. It is not a register entry. Received via BarentsWatch AIS API on November 20, 2026.

Data delivered by BarentsWatch

Ownership & management

Each line shows where the fact comes from. Links backed by an identifier point to the company page.

ISM manager
Source: EU MRV (THETIS-MRV) emissions · reporting year 2025 · reported · high confidence · retrieved Nov 16, 2026

Checking ownership or sanctions for your business? Teams screen fleets by IMO, keep watch with alerts and keep a dated record. Voydar for business →

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 Boneset - KarmoyAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Boneset - KarmoyAIS-detectedVoydar port-call detector (AIS geofence)
Left StavangerAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at StavangerAIS-detectedVoydar port-call detector (AIS geofence)
Left FredrikstadAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at FredrikstadAIS-detectedVoydar port-call detector (AIS geofence)
Reported departure from Nystad (Uusikaupunki)Authority-reportedDigitraffic Port Call API
Reported arrival at Nystad (Uusikaupunki)Authority-reportedDigitraffic Port Call API
Former name: HNLMS MERCUURAIS, seen by Voydar
Former name: NATO WARSHIP A900AIS, seen by Voydar
Call sign changed from LAUB8 to TT0362AIS, seen by Voydar

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
HNLMS MERCUURFormer name, change seen on AISOct 20, 2026AIS (vessel's own broadcast)
NATO WARSHIP A900Former name, change seen on AISOct 20, 2026AIS (vessel's own broadcast)

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.

Emissions & fuel consumption

Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.

YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
20254,072 t1,270 t234 days72 kg

Technical efficiency: Not Applicable. Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.

Compared with ships of its type

Where this ship’s reported CO₂ intensity for 2025 sits among the ships EU MRV lists as “General cargo ship”. Lower is less CO₂.

CO₂ per nautical mile sailed71.8 kg per nautical mile
Lowest reportedHighest reported

22% of the 2,956 ships in this group reported a lower figure.

Group: lower quartile 74.8 · median 110.6 · upper quartile 185.8

Calculated by Voydar from the figures ships report under EU MRV. This is not a rating and not the IMO Carbon Intensity Indicator (CII). EU MRV covers ships over 5,000 gross tonnage on voyages to, from and within the EU/EEA, so the group is those ships, not the world fleet. How this is calculated

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

Time in port over the last 19 days, drawn by Voydar from the AIS-detected calls listed below. Each bar runs from arrival to departure; gaps are time away from a detected port or without reception.
PortArrivedDepartedTime in port
Boneset - Karmoy NOBOENov 20, 2026, 16:10 UTCNov 20, 2026, 17:29 UTC1 h 19 min
Stavanger NOSVGNov 19, 2026, 15:45 UTCNov 20, 2026, 13:39 UTC21 h 54 min
Fredrikstad NOFRKNov 17, 2026, 06:04 UTCNov 18, 2026, 19:38 UTC37 h 34 min
Sandvik, Styrso SESTRNov 16, 2026, 05:21 UTCNov 16, 2026, 18:07 UTC12 h 45 min
Tyboron DKTYBNov 14, 2026, 19:12 UTCNov 15, 2026, 12:53 UTC17 h 41 min
Cuxhaven DECUXNov 11, 2026, 22:43 UTCNov 14, 2026, 15:03 UTC2 d 16 h
Eydehavn NOEYDNov 8, 2026, 20:47 UTCNov 10, 2026, 09:56 UTC37 h 9 min
Hundested DKHUNNov 7, 2026, 11:55 UTCNov 7, 2026, 21:50 UTC9 h 55 min
Lillesand NOLILNov 5, 2026, 18:04 UTCNov 6, 2026, 14:17 UTC20 h 13 min
Langoya NOLAONov 4, 2026, 14:17 UTCNov 5, 2026, 09:26 UTC19 h 9 min
Straume NOUMENov 4, 2026, 06:10 UTCNov 4, 2026, 16:27 UTC10 h 17 min
Nordhavn DKNHNNov 2, 2026, 23:53 UTCNov 3, 2026, 14:21 UTC14 h 28 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.

Data delivered by BarentsWatch

Reported by authorities Authority-reported

PortRecordDate (UTC)BerthSource
Nystad (Uusikaupunki) FIUKIArrivalOct 24, 2026, 10:15 UTCEi tiedossaDigitraffic Port Call API

Records published by the authority named on each row. Earliest record for this ship: October 24, 2026.

Behaviour at sea Voydar-derived

Patterns Voydar derived from this ship's AIS broadcasts. They are inferences, not reports: each one shows how it was computed and how confident we are, and none of them says why a ship behaved this way.

WhenWhat we observedConfidence
Nov 19, 2026, 17:07 UTC
Draught change

Reported draught went from 5.4 m to 3 m while in port at Stavanger. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

High (75%)
Nov 19, 2026, 00:04 UTC
Draught change

Reported draught went from 4.5 m to 5.4 m after leaving Fredrikstad. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (55%)
Nov 18, 2026, 00:57 UTC
Draught change

Reported draught went from 6.5 m to 4.5 m while in port at Fredrikstad. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

High (75%)
Nov 16, 2026, 16:51 UTC
Draught change

Reported draught went from 6.5 m to 4.5 m while in port at Sandvik, Styrso. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

High (75%)
Nov 15, 2026, 00:15 UTC
Draught change

Reported draught went from 4.5 m to 6.5 m while in port at Tyboron. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

High (75%)
Nov 12, 2026, 09:41 UTC
Draught change

Reported draught went from 5.7 m to 4.5 m while in port at Cuxhaven. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Nov 10, 2026, 10:17 UTC
Draught change

Reported draught went from 4.5 m to 5.7 m after leaving Eydehavn. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (55%)
Nov 7, 2026, 23:15 UTC
Draught change

Reported draught went from 6.5 m to 4.5 m after leaving Hundested. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Nov 6, 2026, 00:35 UTC
Draught change

Reported draught went from 4.3 m to 6.5 m while in port at Lillesand. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

High (75%)
Nov 6, 2026, 00:00 UTC
IMO used twice

IMO 9964077 was broadcast by two ships (MMSI 245974000 and 257415000) 631 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Nov 5, 2026, 00:00 UTC
IMO used twice

IMO 9964077 was broadcast by two ships (MMSI 245974000 and 257415000) 454 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Nov 4, 2026, 15:18 UTC
Draught change

Reported draught went from 6.5 m to 4.3 m while in port at Langoya. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

High (75%)
Nov 4, 2026, 00:00 UTC
IMO used twice

IMO 9964077 was broadcast by two ships (MMSI 245974000 and 257415000) 367 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Nov 3, 2026, 01:13 UTC
Draught change

Reported draught went from 4.3 m to 6.5 m while in port at Nordhavn. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

High (75%)
Nov 3, 2026, 00:00 UTC
IMO used twice

IMO 9964077 was broadcast by two ships (MMSI 245974000 and 257415000) 513 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Nov 2, 2026, 00:00 UTC
IMO used twice

IMO 9964077 was broadcast by two ships (MMSI 245974000 and 257415000) 681 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Nov 1, 2026, 00:00 UTC
IMO used twice

IMO 9964077 was broadcast by two ships (MMSI 245974000 and 257415000) 450 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Oct 29, 2026, 15:38 UTC
Draught change

Reported draught went from 5.5 m to 4.5 m while in port at Sirevag. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Oct 29, 2026, 00:00 UTC
IMO used twice

IMO 9964077 was broadcast by two ships (MMSI 245974000 and 257415000) 130 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

Medium (70%)
Oct 28, 2026, 00:00 UTC
IMO used twice

IMO 9964077 was broadcast by two ships (MMSI 245974000 and 257415000) 119 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

Medium (70%)

Source: BarentsWatch AIS API. Data delivered by BarentsWatch (NLOD 2.0; data owner: Kystverket). Licence: NLOD 2.0 (BarentsWatch API terms 2023-11-02; Live/Historic AIS OpenAPI licence NLOD).

Source: AISstream.io global terrestrial AIS. AIS data: AISstream.io. Licence: none published.

Derived from AIS positions of feeds whose terms allow display on Voydar. Coverage is terrestrial: gaps are reported only where our receivers kept hearing other ships. Detections below medium confidence are not shown.

How these are computed →

Frequently asked questions

What kind of ship is HAGLAND PREMIER?
HAGLAND PREMIER is a naval vessel sailing under the flag of Norway.
Who is recorded as the owner or manager of HAGLAND PREMIER?
Hagland Shipping AS is recorded as ISM manager for HAGLAND PREMIER (source: EU MRV (THETIS-MRV) emissions; reporting year 2025). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for HAGLAND PREMIER?
Voydar has no matched sanctions record displayed for HAGLAND PREMIER 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 HAGLAND PREMIER. Missing records do not establish whether the ship has been detained.

Full Vessel Report

A dated PDF with the complete track since June 2026, every port call, ownership and flag changes, inspections, a sanctions and dark-activity screening snapshot, emissions, companies and every source.

See a sample report (PDF)

Sample: a real report for EVER GIVEN (IMO 9811000), built from public data and marked SAMPLE on every page.

Every fact on this page stays free.

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/9964077
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

Cite this page

HAGLAND PREMIER. Voydar (voydar.com). https://www.voydar.com/vessel/9964077-hagland-premier. Retrieved November 20, 2026.

Each fact above names its own source and date. Cite that primary source too when you rely on a fact.

Using this data in code?

Every account gets a personal API allowance: 2,500 credits a month free, 25,000 with Pro. Pro includes use in your own product. Growth and Scale add volume, and each includes one Pro membership.

See plans

Sources and attribution

  • Data delivered by BarentsWatch (NLOD 2.0; data owner: Kystverket) (NLOD 2.0 (BarentsWatch API terms 2023-11-02; Live/Historic AIS OpenAPI licence NLOD))

Each fact above names its source and the date it was retrieved. Each source's licence applies to its data.

Compiled by Voydar from the sources named on this page.

Page: https://www.voydar.com/vessel/9964077-hagland-premier

Generated from voydar.com on Nov 20, 2026, 17:59 UTC