TRANS HAV
Ro-ro ship · Malta · built 2007 · AIS Class A
In short
TRANS HAV (Ro-ro ship, Malta flag) was last seen on AIS on , moored, in the port of Ardalstangen. Its crew-entered AIS destination is HOYANGER, with an ETA of Oct 2, 2026, 04:30 UTC; its reported draught is 6.5 m (voyage report via BarentsWatch AIS API, received Oct 1, 2026, 21:17 UTC). It arrived there on Oct 1, 2026, 06:19 UTC.
- Vessel type
- Ro-ro ship
- Flag
- Malta
- Year built
- 2007
- Gross tonnage
- 15,586
- Size (length × beam)
- 166 m
- Registered owner
- —
Watch this ship
Get an email when TRANS HAV arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
We email you a link and a code. That creates a free account, no password or card, and follows TRANS HAV.
Free account, no card: follow up to 5 ships and ports. Plus follows 50, Pro 500.
By continuing you accept the Terms and the Privacy policy.
Last reported position
received- Position
- 61.2322° N, 7.7064° E
- Area
- Norwegian Sea
- StatusWhat do AIS statuses mean?
- Moored
- Speed
- 0.2 kn
- Course
- 1°
- Heading
- 164°
Last 30 days: 10 port calls (Ardalstangen, Havik, Husoy - Karmoy, Bergen, and Tananger).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
A year of history in the Terminal (Plus) · the full archive since June 1, 2026 (Pro)
Try the live demo, no sign-upIdentity & particulars
- Name
- TRANS HAV
- IMO numberWhat is an IMO number?
- 9348948
- MMSIWhat is an MMSI?
- 249497000
- Call signWhat is a call sign?
- 9HA6277
- Flag
- Malta
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 15,586
- Length overall
- 165.8 m
- Beam
- —
- Year built
- 2007
MaltaA 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 Sep 28, 2026Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–2025 · reported · confidence 0.9 · retrieved Sep 28, 2026
- Builder
- 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.
| Date | Event | Source |
|---|---|---|
| Arrived at ArdalstangenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left HavikAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at HavikAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Husoy - KarmoyAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Husoy - KarmoyAIS-detected | Voydar port-call detector (AIS geofence) | |
| ISM manager: Stodig Ship Management AS (previously Oy Trailer-Link AB) | Voydar relationship-change derivation (derived by Voydar from EU MRV (THETIS-MRV) emissions) |
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 |
|---|---|---|---|---|
| 2018 | 20,418 t | 6,537 t | 162 days | 335 kg |
| 2019 | 18,398 t | 5,891 t | 158 days | 322 kg |
| 2020 | 17,668 t | 5,628 t | 252 days | 332 kg |
| 2021 | 30,021 t | 9,519 t | 252 days | 329 kg |
| 2022 | 24,662 t | 7,820 t | 235 days | 307 kg |
| 2023 | 25,697 t | 8,150 t | 261 days | 298 kg |
| 2024 | 25,185 t | 7,988 t | 285 days | 288 kg |
| 2025 | 17,686 t | 5,646 t | 198 days | 289 kg |
Technical efficiency: EEXI (14.61 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 |
|---|---|---|---|
| Ardalstangen NOARD | Oct 1, 2026, 06:19 UTC | in port | — |
| Havik NOHVI | Sep 30, 2026, 10:37 UTC | Sep 30, 2026, 13:34 UTC | 2 h 57 min |
| Husoy - Karmoy NOHSO | Sep 26, 2026, 03:28 UTC | Sep 26, 2026, 09:09 UTC | 5 h 41 min |
| Bergen NOBGO | Sep 25, 2026, 18:18 UTC | Sep 25, 2026, 20:44 UTC | 2 h 26 min |
| Ardalstangen NOARD | Sep 24, 2026, 05:49 UTC | Sep 24, 2026, 22:51 UTC | 17 h 2 min |
| Havik NOHVI | Sep 23, 2026, 10:32 UTC | Sep 23, 2026, 12:41 UTC | 2 h 9 min |
| Havik NOHVI | Sep 16, 2026, 10:42 UTC | Sep 16, 2026, 13:52 UTC | 3 h 10 min |
| Bergen NOBGO | Sep 11, 2026, 19:30 UTC | Sep 11, 2026, 21:44 UTC | 2 h 14 min |
| Ardalstangen NOARD | Sep 10, 2026, 06:08 UTC | Sep 10, 2026, 21:39 UTC | 15 h 31 min |
| Tananger NOTAE | Sep 5, 2026, 11:38 UTC | Sep 5, 2026, 18:07 UTC | 6 h 30 min |
| Havik NOHVI | Aug 29, 2026, 05:40 UTC | Aug 29, 2026, 08:37 UTC | 2 h 57 min |
| Havik NOHVI | Aug 22, 2026, 05:38 UTC | Aug 22, 2026, 07:54 UTC | 2 h 16 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.
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 |
|---|---|---|
| Sep 25, 2026, 10:57 UTC | Draught change Reported draught went from 6.5 m to 7.3 m after leaving Ardalstangen. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
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.
Frequently asked questions
- Where is TRANS HAV now?
- TRANS HAV (Ro-ro ship, Malta flag) was last seen on AIS on Oct 1, 2026, 21:27 UTC, moored, in the port of Ardalstangen. The crew-entered destination was HOYANGER (voyage report via BarentsWatch AIS API, received Oct 1, 2026, 21:17 UTC). This report does not confirm the ship’s current route.
- What kind of ship is TRANS HAV?
- TRANS HAV is a ro-ro ship sailing under the flag of Malta, built in 2007 by Pella Sietas. The vessel is 165.8 m long and has a gross tonnage of 15,586.
- What sanctions and inspection records does Voydar hold for TRANS HAV?
- Voydar has no matched sanctions record displayed for TRANS HAV from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels and the New Zealand Russia Sanctions Register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for TRANS HAV. Missing records do not establish whether the ship has been detained.
Sister ships
Likely sister ships: built by Pella Sietas, same type, gross tonnage within 2.5% and length within 1.5% of this ship's.
Neighbouring IMO numbers
IMO numbers are issued in sequence. These are the nearest numbers below and above this ship's that have a full Voydar profile.
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/9348948Using 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.