Hoegh Tokyo
Car carrier · Norway · built 2004 · AIS Class B
In short
Hoegh Tokyo (Car carrier, Norway flag) was last seen on AIS on , moored, in the port of Kallo. Its crew-entered AIS destination is GBBRS>BEANR, with an ETA of Nov 19, 2026, 06:30 UTC; its reported draught is 8.4 m (voyage report via AISstream.io global terrestrial AIS, received Nov 19, 2026, 18:57 UTC). It arrived there on Nov 19, 2026, 13:03 UTC. ISM manager: Hoegh Autoliners Management AS (source: EU MRV (THETIS-MRV) emissions, reporting year 2024).
- Vessel type
- Car carrier
- Flag
- Norway
- Year built
- 2004
- Gross tonnage
- 68,871
- Size (length × beam)
- 228 m × 32 m
- ISM manager
- Hoegh Autoliners Management AS
Last reported position: 51.2702° N, 4.2184° E · North Sea · See on the map
Shipping a car on this vessel?
Follow Hoegh Tokyo and Voydar's daily email tells you when it has arrived in port, left again, or changed its destination.
What you would have been told
Following Hoegh Tokyo over the last 24 hours would have sent 1 message.
- ArrivedKallo
Detected from AIS, as of Nov 19, 2026, 19:06 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for Hoegh Tokyo 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
- 51.2702° N, 4.2184° E
- Area
- North Sea
- Status
- MooredWhat do AIS statuses mean?
- Speed
- 0 kn
- Course
- 298°
- Heading
- 28°
- Compass: course over ground 298°, heading 28°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 2 port calls (Kallo and Avonmouth).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows Hoegh Tokyo's track before the last 30 days. Voydar has recorded its port calls since October 16, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
Length overall 228 mone tick every 25 m
Beam 32 mPlan outline, to scale
- Name
- Hoegh Tokyo
- IMO numberWhat is an IMO number?
- 9285483
- MMSIWhat is an MMSI?
- 257408000
- Call signWhat is a call sign?
- LAPZ7
- Flag
- Norway
- Vessel type
- Detailed type from WikidataCar carrier
- Gross tonnageGross tonnage vs deadweight
- 68,871
- Deadweight (DWT)
- Source: Wikidata, record Q117024430. Added to Voydar on October 24, 2026. Licence: CC0 1.0.27,100 t
- Length overall
- 228 m
- Beam
- 32 m
- Year built
- 2004
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 2024 · reported · high confidence · retrieved Nov 16, 2026
- Builder
- Source: Wikidata · reported · high confidence · retrieved Nov 15, 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.
| Date | Event | Source |
|---|---|---|
| Arrived at KalloAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left AvonmouthAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at AvonmouthAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left KeppelAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at KeppelAIS-detected | Voydar port-call detector (AIS geofence) | |
| Inspection at Baltimore, Maryland | USCG PSIX / CGMIX inspections | |
| Inspection at Mobile, Alabama | USCG PSIX / CGMIX inspections | |
| Inspection at Mobile, Alabama | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at Jacksonville, Florida | USCG PSIX / CGMIX inspections | |
| Inspection at Jacksonville, Florida | USCG PSIX / CGMIX inspections | |
| Inspection at Jacksonville, Florida | USCG PSIX / CGMIX inspections | |
| Inspection at Baltimore, Maryland | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at Baltimore, Maryland | USCG PSIX / CGMIX inspections | |
| Inspection at Baltimore, Maryland | USCG PSIX / CGMIX inspections | |
| Inspection at Jacksonville, Florida | USCG PSIX / CGMIX inspections | |
| Reported departure from JACKSONVILLE HARBOR, FLAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at JACKSONVILLE HARBOR, FLAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at WilmingtonAuthority-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.
Safety & inspections
| Date | Type | Port | Findings |
|---|---|---|---|
| Mar 13, 2026 | Vessel Inspection | Baltimore, Maryland | clean |
| Nov 13, 2025 | Vessel Inspection | Mobile, Alabama | clean |
| Mar 17, 2025 | Vessel Inspection | Mobile, Alabama | clean |
| Jul 14, 2024 | Vessel InspectionPSC | Jacksonville, Florida | clean |
| Jul 12, 2024 | Vessel Operational Control | Jacksonville, Florida | clean |
| Jul 12, 2024 | Vessel Operational Control | Jacksonville, Florida | clean |
| Jul 11, 2024 | Vessel Operational Control | Baltimore, Maryland | clean |
| Jul 9, 2024 | Vessel InspectionPSC | Baltimore, Maryland | clean |
| Jul 8, 2024 | Vessel Operational Control | Baltimore, Maryland | clean |
| Sep 29, 2023 | Vessel Inspection | Jacksonville, Florida | clean |
| Apr 14, 2021 | Vessel InspectionPSC | TEXAS CITY, Texas | clean |
| Apr 11, 2021 | Vessel InspectionPSC | Mobile, Alabama | clean |
| Dec 9, 2020 | Vessel Inspection | Mobile, Alabama | clean |
| Aug 28, 2020 | Vessel Inspection | Baltimore, Maryland | clean |
| Aug 20, 2020 | Vessel Inspection | Mobile, Alabama | clean |
| Aug 20, 2020 | Vessel InspectionPSC | TEXAS CITY, Texas | clean |
| Apr 10, 2020 | Vessel Inspection | Baltimore, Maryland | clean |
| Dec 16, 2019 | Vessel InspectionPSC | Savannah, Georgia | clean |
| Dec 11, 2019 | Vessel Inspection | TEXAS CITY, Texas | clean |
| Dec 1, 2018 | Vessel InspectionPSC | Jacksonville, Florida | clean |
Source: U.S. Coast Guard Port State Information Exchange (PSIX) — public domain. Covers inspections recorded in U.S. waters. Free on Voydar; the incumbents charge for this.
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 | 7,762 t | 2,475 t | 59 days | 434 kg |
| 2019 | 6,496 t | 2,062 t | 55 days | 420 kg |
| 2020 | 1,905 t | 604 t | 18 days | 312 kg |
| 2022 | 14,270 t | 4,559 t | 115 days | 363 kg |
| 2023 | 15,155 t | 4,985 t | 122 days | 394 kg |
| 2024 | 13,014 t | 4,162 t | 88 days | 420 kg |
Technical efficiency: EEXI (12.46 gCO₂/t·nm). 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 2024 sits among the ships EU MRV lists as “Vehicle carrier”. Lower is less CO₂.
- CO₂ per tonne of cargo carried one nautical mile52.88 g per tonne-nautical mile
- Lowest reportedHighest reported
45% of the 340 ships in this group reported a lower figure.
Group: lower quartile 43.93 · median 55.37 · upper quartile 79.73
- CO₂ per nautical mile sailed419.8 kg per nautical mile
- Lowest reportedHighest reported
99% of the 465 ships in this group reported a lower figure.
Group: lower quartile 291.8 · median 320.2 · upper quartile 343.2
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
| Port | Arrived | Departed | Time in port |
|---|---|---|---|
| Kallo BEKOU | Nov 19, 2026, 13:03 UTC | in port | — |
| Avonmouth GBAVO | Nov 15, 2026, 22:01 UTC | Nov 17, 2026, 09:03 UTC | 35 h 2 min |
| Keppel SGKEP | Oct 16, 2026, 05:50 UTC | Oct 17, 2026, 16:17 UTC | 34 h 26 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.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| JACKSONVILLE HARBOR, FL | Departure | Oct 25, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| JACKSONVILLE HARBOR, FL | Arrival | Oct 23, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Wilmington USILG | Arrival | Oct 19, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Wilmington USILG | Departure | Oct 19, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baltimore USBAL | Departure | Oct 18, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baltimore USBAL | Arrival | Oct 17, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New York USNYC | Arrival | Oct 14, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New York USNYC | Departure | Oct 14, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| TURTLE RIVER, GA (INCLUDED IN BRUNSWICK HARBOR, GA) | Arrival | Oct 11, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| TURTLE RIVER, GA (INCLUDED IN BRUNSWICK HARBOR, GA) | Departure | Oct 11, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| JACKSONVILLE HARBOR, FL | Departure | Oct 10, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| JACKSONVILLE HARBOR, FL | Arrival | Oct 10, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: February 4, 2006.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
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.
Predicted arrival
Voydar estimates arrival at Zeebrugge around Nov 19, 2026, 11:32 UTC, most likely between Nov 18, 2026, 20:45 UTC and Nov 23, 2026, 00:10 UTC. Based on 48 past transits between GBAVO and Zeebrugge seen in our port calls. The crew-reported ETA is Nov 19, 2026, 06:00 UTC.
Medium (51%) · Method seadar.behaviour.eta_prediction v1
| When | What we observed | Confidence |
|---|---|---|
| Nov 17, 2026, 04:45 UTC | Draught change Reported draught went from 9.1 m to 8.4 m while in port at Avonmouth. 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.
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
- What kind of ship is Hoegh Tokyo?
- Hoegh Tokyo is a car carrier sailing under the flag of Norway, built in 2004 by Hanwha Ocean. The vessel is 228 m long with a beam of 32 m and has a gross tonnage of 68,871.
- Who is recorded as the owner or manager of Hoegh Tokyo?
- Hoegh Autoliners Management AS is recorded as ISM manager for Hoegh Tokyo (source: EU MRV (THETIS-MRV) emissions; reporting year 2024). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for Hoegh Tokyo?
- Voydar has no matched sanctions record displayed for Hoegh Tokyo 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. Hoegh Tokyo has 50 recorded Port State Control inspections. Detention and deficiency detail is not recorded for these inspections.
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.
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.
Know this ship?
Help other readers. Member posts are shown as member content, never as sourced data.
- Date, place and an optional note
- Members who know her can answer
- Suggest a correctionChecked against sources before anything changes
More Car carriers
Other car carriers with full Voydar profiles. A different set each day. All car carriers
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/9285483Cite this page
Hoegh Tokyo. Voydar (voydar.com). https://www.voydar.com/vessel/9285483-hoegh-tokyo. Retrieved November 19, 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.