Hagland Chief
General cargo ship · Norway · built 2012 · AIS Class A
In short
Hagland Chief (General cargo ship, Norway flag) was last seen on AIS on , under way at 8.9 kn, in the Baltic Sea. Its crew-entered AIS destination is EGERSUND, with an ETA of Oct 7, 2026, 06:30 UTC; its reported draught is 4 m (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 19:01 UTC). ISM manager: Hagland Shipping AS (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).
Current voyage: from Nyborg (departed Oct 5, 2026, 14:17 UTC) to EGERSUND
- Vessel type
- General cargo ship
- Flag
- Norway
- Year built
- 2012
- Gross tonnage
- —
- Size (length × beam)
- 90 m × 14 m
- ISM manager
- Hagland Shipping AS
Watch this ship
Get an email when Hagland Chief 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
- 57.8827° N, 10.4454° E
- Area
- Baltic Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 8.9 kn
- Course
- 299°
- Heading
- 292°
Last 30 days: 10 port calls (Nyborg, Eigersund, Avernakke Havn, Egersund, Sjursoja/Oslo, Valberg, and Sirevag).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows Hagland Chief's track before the last 30 days. Voydar has recorded its port calls since August 18, 2026.Free forever. No card. New accounts include 14 days of Pro.
Try the live demo, no sign-upIdentity & particulars
- Name
- Hagland Chief
- IMO numberWhat is an IMO number?
- 9521344
- MMSIWhat is an MMSI?
- 257207000
- Call signWhat is a call sign?
- LACT8
- Flag
- Norway
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- —
- Deadweight (DWT)
- Source: Wikidata, record Q57313407. Added to Voydar on September 23, 2026. Licence: CC0 1.0.4,450 t
- Length overall
- 90 m
- Beam
- 14.4 m
- Year built
- 2012
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.
- Operator
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026Hagland Shipping(not linked to a company record)Source: Wikidata · reported · confidence 0.6 · retrieved Jun 8, 2026
- 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.
| Date | Event | Source |
|---|---|---|
| Left NyborgAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at NyborgAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left EigersundAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at EigersundAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left NyborgAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at NyborgAIS-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.
Emissions & fuel consumption
Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.
| Year | CO₂ emitted | Fuel burned | Time at sea | CO₂ / n mile |
|---|---|---|---|---|
| 2025 | 3,385 t | 1,056 t | 174 days | 81 kg |
Technical efficiency: EEXI (15.88 gCO₂/t·nm). 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
| Port | Arrived | Departed | Time in port |
|---|---|---|---|
| Nyborg DKNBG | Oct 5, 2026, 04:01 UTC | Oct 5, 2026, 14:17 UTC | 10 h 17 min |
| Eigersund NOEGD | Oct 2, 2026, 19:36 UTC | Oct 3, 2026, 15:57 UTC | 20 h 21 min |
| Nyborg DKNBG | Oct 1, 2026, 04:20 UTC | Oct 1, 2026, 15:27 UTC | 11 h 7 min |
| Avernakke Havn DKAVN | Sep 27, 2026, 05:33 UTC | Sep 27, 2026, 17:12 UTC | 11 h 39 min |
| Egersund NOEGE | Sep 25, 2026, 09:39 UTC | Sep 25, 2026, 19:42 UTC | 10 h 3 min |
| Sjursoja/Oslo NOSJU | Sep 23, 2026, 15:36 UTC | Sep 24, 2026, 07:28 UTC | 15 h 52 min |
| Valberg NOVBE | Sep 22, 2026, 15:48 UTC | Sep 23, 2026, 06:34 UTC | 14 h 47 min |
| Sirevag NOSRV | Sep 19, 2026, 04:06 UTC | Sep 19, 2026, 16:10 UTC | 12 h 4 min |
| Sirevag NOSRV | Sep 15, 2026, 05:39 UTC | Sep 17, 2026, 03:58 UTC | 46 h 20 min |
| Avernakke Havn DKAVN | Sep 13, 2026, 05:32 UTC | Sep 15, 2026, 05:37 UTC | 2 d 0 h |
| Haugesund NOHAU | Aug 21, 2026, 17:52 UTC | Aug 22, 2026, 16:33 UTC | 22 h 41 min |
| Storoya NOSOY | Aug 18, 2026, 19:08 UTC | Aug 21, 2026, 17:22 UTC | 2 d 22 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.
| When | What we observed | Confidence |
|---|---|---|
| Oct 2, 2026, 21:11 UTC | Draught change Reported draught went from 3.8 m to 6.5 m while in port at Eigersund. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Sep 27, 2026, 07:06 UTC | Draught change Reported draught went from 6.5 m to 4.1 m while in port at Avernakke Havn. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
Source: BarentsWatch AIS API. Contains data under NLOD made available by BarentsWatch. Licence: NLOD 2.0 (probable).
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.
Frequently asked questions
- Where is Hagland Chief now?
- Hagland Chief (General cargo ship, Norway flag) was last seen on AIS on Oct 6, 2026, 07:39 UTC, under way at 8.9 kn, in the Baltic Sea. The crew-entered destination was EGERSUND (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 19:01 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Hagland Chief?
- Hagland Chief is a general cargo ship sailing under the flag of Norway, built in 2012. The vessel is 90 m long with a beam of 14.4 m.
- Who is recorded as the owner or manager of Hagland Chief?
- Hagland Shipping AS is recorded as ISM manager for Hagland Chief (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 Chief?
- Voydar has no matched sanctions record displayed for Hagland Chief 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 Chief. 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/9521344Using 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.