Höegh Manila
Car carrier · Norway · built 2007 · AIS Class A
In short
Höegh Manila (Car carrier, Norway flag) was last seen on AIS on , under way at 16.8 kn, in the North Atlantic Ocean. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its last detected port call was at Kallo: arrived Sep 7, 2026, left Sep 11, 2026. ISM manager: Hoegh Autoliners Management AS (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
- Vessel type
- Car carrier
- Flag
- Norway
- Year built
- 2007
- Gross tonnage
- 51,964
- Size (length × beam)
- 180 m
- ISM manager
- Hoegh Autoliners Management AS
Watch this ship
Höegh Manila 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
- 37.2731° N, 29.1103° W
- Area
- North Atlantic Ocean
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 16.8 kn
- Course
- 253°
- Heading
- 252°
Last 30 days: 1 port call (Kallo).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows Höegh Manila's track before the last 30 days. Voydar has recorded its port calls since September 4, 2026.Free forever. No card. New accounts include 14 days of Pro.
Try the live demo, no sign-upIdentity & particulars
- Name
- Höegh Manila
- IMO numberWhat is an IMO number?
- 9368912
- MMSIWhat is an MMSI?
- 259709000
- Call signWhat is a call sign?
- LAEC7
- Flag
- Norway
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 51,964
- Length overall
- 179.9 m
- Beam
- —
- Year built
- 2007
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 years 2024–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 KalloAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at KalloAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left KalloAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at KalloAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from BaltimoreAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at PhiladelphiaAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from PhiladelphiaAuthority-reported | USACE foreign traffic vessel entrances & clearances |
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 | 8,295 t | 2,647 t | 94 days | 276 kg |
| 2019 | 13,680 t | 4,365 t | 145 days | 283 kg |
| 2020 | 5,645 t | 1,800 t | 68 days | 271 kg |
| 2021 | 11,831 t | 3,779 t | 116 days | 310 kg |
| 2022 | 15,938 t | 5,079 t | 157 days | 306 kg |
| 2023 | 17,646 t | 5,626 t | 199 days | 268 kg |
| 2024 | 18,571 t | 5,921 t | 199 days | 273 kg |
| 2025 | 16,908 t | 5,392 t | 186 days | 268 kg |
Technical efficiency: EEXI (15.57 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 |
|---|---|---|---|
| Kallo BEKOU | Sep 7, 2026, 06:23 UTC | Sep 11, 2026, 12:16 UTC | 4 d 5 h |
| Kallo BEKOU | Sep 4, 2026, 18:21 UTC | Sep 7, 2026, 06:05 UTC | 2 d 11 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.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Baltimore USBAL | Departure | Dec 12, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Philadelphia USPHL | Arrival | Dec 8, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Philadelphia USPHL | Departure | Dec 8, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baltimore USBAL | Arrival | Dec 7, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| JACKSONVILLE HARBOR, FL | Departure | Dec 5, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| JACKSONVILLE HARBOR, FL | Arrival | Dec 5, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baltimore USBAL | Arrival | Aug 27, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baltimore USBAL | Departure | Aug 27, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| JACKSONVILLE HARBOR, FL | Departure | Aug 24, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| JACKSONVILLE HARBOR, FL | Arrival | Aug 24, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baltimore USBAL | Departure | Jul 1, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baltimore USBAL | Arrival | Jun 30, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: October 21, 2008.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
Frequently asked questions
- Where is Höegh Manila now?
- Höegh Manila (Car carrier, Norway flag) was last seen on AIS on Sep 20, 2026, 03:19 UTC, under way at 16.8 kn, in the North Atlantic Ocean. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report.
- What kind of ship is Höegh Manila?
- Höegh Manila is a car carrier sailing under the flag of Norway, built in 2007. The vessel is 179.9 m long and has a gross tonnage of 51,964.
- Who is recorded as the owner or manager of Höegh Manila?
- Hoegh Autoliners Management AS is recorded as ISM manager for Höegh Manila (source: EU MRV (THETIS-MRV) emissions; reporting years 2024–2025). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for Höegh Manila?
- Voydar has no matched sanctions record displayed for Höegh Manila 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 Höegh Manila. 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/9368912Using 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.