Skip to content

HAGLAND PIONEER

General cargo ship · Norway · AIS Class A

IMO9936331MMSI258059000Call signLAQE8Last AIS position Oct 5, 2026, 18:31 UTC

In short

HAGLAND PIONEER (General cargo ship, Norway flag) was last seen on AIS on , under way at 12.6 kn, near Cuxhaven (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 DECUX (Cuxhaven), with an ETA of Oct 5, 2026, 20:00 UTC; its reported draught is 6.7 m (voyage report via BarentsWatch AIS API, received Oct 4, 2026, 21:40 UTC). ISM manager: Hagland Shipping AS (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).

Current voyage: from Larvik (departed Oct 4, 2026, 10:14 UTC) to DECUX (Cuxhaven)

Flag
Norway
Year built
—
Gross tonnage
—
Size (length × beam)
—

Watch this ship

HAGLAND PIONEER 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.

Last reported position

received
Position
53.9858° N, 8.3687° E
Area
North Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
12.6 kn
Course
101°
Heading
99°
53.9858° N, 8.3687° E
Open the full live map →

Last 30 days: 10 port calls (Larvik, Langoya, Nordhavn, Oskarshamn, Utne, Laksevag, Knarrevik, Vikkilen, Sjursoja/Oslo, and Skarholmen).

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

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

Try the live demo, no sign-up

Identity & particulars

Name
HAGLAND PIONEER
IMO numberWhat is an IMO number?
9936331
MMSIWhat is an MMSI?
258059000
Call signWhat is a call sign?
LAQE8
Flag
Norway
AIS ship type
Cargo
Length overall
—
Beam
—
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.

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 · confidence 0.9 · retrieved Oct 5, 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 LarvikAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at LarvikAIS-detectedVoydar port-call detector (AIS geofence)
Left LangoyaAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at LangoyaAIS-detectedVoydar port-call detector (AIS geofence)
Left NordhavnAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at NordhavnAIS-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.

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,132 t1,289 t234 days74 kg

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

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
Larvik NOLAROct 3, 2026, 17:19 UTCOct 4, 2026, 10:14 UTC16 h 55 min
Langoya NOLAOOct 2, 2026, 22:16 UTCOct 3, 2026, 12:58 UTC14 h 42 min
Nordhavn DKNHNOct 1, 2026, 14:18 UTCOct 1, 2026, 22:42 UTC8 h 24 min
Oskarshamn SEOSKSep 30, 2026, 04:39 UTCSep 30, 2026, 11:27 UTC6 h 48 min
Utne NOUTNSep 26, 2026, 04:28 UTCSep 26, 2026, 18:29 UTC14 h 1 min
Laksevag NOLVGSep 25, 2026, 12:57 UTCSep 25, 2026, 21:27 UTC8 h 29 min
Knarrevik NOKRVSep 25, 2026, 06:26 UTCSep 25, 2026, 12:50 UTC6 h 23 min
Vikkilen NOVKKSep 18, 2026, 10:06 UTCSep 18, 2026, 18:40 UTC8 h 34 min
Sjursoja/Oslo NOSJUSep 13, 2026, 22:56 UTCSep 14, 2026, 13:48 UTC14 h 52 min
Skarholmen NOSRHSep 7, 2026, 23:09 UTCSep 8, 2026, 00:35 UTC1 h 26 min
Skorgeneset NOSGTSep 5, 2026, 12:19 UTCSep 6, 2026, 20:09 UTC31 h 50 min
Gdynia PLGDYJul 17, 2026, 03:50 UTCJul 27, 2026, 12:52 UTC10 d 9 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.

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
Oct 1, 2026, 15:29 UTC
Draught change

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

Method seadar.behaviour.draught_change v1

High (75%)
Sep 30, 2026, 10:17 UTC
Draught change

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

Method seadar.behaviour.draught_change v1

High (75%)
Sep 26, 2026, 17:01 UTC
Draught change

Reported draught went from 4.2 m to 6.2 m while in port at Utne. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

High (75%)
Sep 25, 2026, 11:10 UTC
Draught change

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

Method seadar.behaviour.draught_change v1

Medium (65%)

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

Source: BarentsWatch AIS API. Contains data under NLOD made available by BarentsWatch. Licence: NLOD 2.0 (probable).

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

Where is HAGLAND PIONEER now?
HAGLAND PIONEER (General cargo ship, Norway flag) was last seen on AIS on Oct 5, 2026, 18:31 UTC, under way at 12.6 kn, near Cuxhaven (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 DECUX (voyage report via BarentsWatch AIS API, received Oct 4, 2026, 21:40 UTC). This report does not confirm the ship’s current route.
What kind of ship is HAGLAND PIONEER?
HAGLAND PIONEER is a general cargo ship sailing under the flag of Norway.
Who is recorded as the owner or manager of HAGLAND PIONEER?
Hagland Shipping AS is recorded as ISM manager for HAGLAND PIONEER (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 PIONEER?
Voydar has no matched sanctions record displayed for HAGLAND PIONEER 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 PIONEER. 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/9936331
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