Skip to content
voydar.com

AUTO WAY

Car carrier · Norway · built 2006 · AIS Class A

IMO9303558MMSI257824000Call signLAVD7Last AIS position Nov 16, 2026, 23:44 UTC

In short

AUTO WAY (Car carrier, Norway flag) was last seen on AIS on , under way at 16.4 kn, in the Mediterranean Sea. 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 Zeebrugge: arrived Nov 10, 2026, left Nov 12, 2026. ISM manager: Wallenius Marine (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Data: AISHub contributors

Vessel type
Car carrier
Flag
Norway
Year built
2006
Gross tonnage
59,705
Size (length × beam)
199 m × 32 m
ISM manager
Wallenius Marine
Photo of IMO 9303558
Photo: Ein Dahmer · Licence: CC BY-SA 4.0 · via Wikimedia Commons

Last reported position: 37.0002° N, 2.8947° E · Mediterranean Sea · See on the map

Shipping a car on this vessel?

AUTO WAY has not been received for a while. Follow it for an email update when Voydar receives a new position, and for arrival and departure alerts.

What you would have been told

Nothing in the last 24 hours: no arrival or departure at a port. You are told the moment that changes.

Detected from AIS, as of Nov 17, 2026, 17:43 UTC.

Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for AUTO WAY 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: Voydar for iPhone

Last reported position

received
Position
37.0002° N, 2.8947° E
Area
Mediterranean Sea
Status
Under way using engineWhat do AIS statuses mean?
Speed
16.4 kn
Course
70°
Heading
71°
Compass: course over ground 70°, heading 71°
NArrow: course. Hull: heading. As broadcast on AIS.
37.0002° N, 2.8947° E. Reference map only, not for navigation.
Locator map: Natural Earth (public domain)
37.0002° N, 2.8947° E
See it live in 3D →

Last 30 days: 3 port calls (Zeebrugge, Nieuwdorp, and Piraeus).

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

Data: AISHub contributors

Pro shows AUTO WAY's track before the last 30 days. Voydar has recorded its port calls since September 2, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.

Try the live demo, no sign-up

Identity & particulars

Length overall 199.1 mone tick every 25 m

Beam 32.2 mPlan outline, to scale

Drawn by Voydar from the recorded type, length and beam. The side view is a drawing of the ship type, not of this ship; the length rule and the plan outline's proportions are to scale, the hull shape is not surveyed.
Name
AUTO WAY
IMO numberWhat is an IMO number?
9303558
MMSIWhat is an MMSI?
257824000
Call signWhat is a call sign?
LAVD7
Flag
Norway
Vessel type
Car carrier
Gross tonnageGross tonnage vs deadweight
59,705
Length overall
199.1 m
Beam
32.2 m
Year built
2006

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 · high confidence · retrieved Nov 16, 2026
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.

DateEventSource
Left ZeebruggeAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at ZeebruggeAIS-detectedVoydar port-call detector (AIS geofence)
Left NieuwdorpAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at NieuwdorpAIS-detectedVoydar port-call detector (AIS geofence)
Left PiraeusAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at PiraeusAIS-detectedVoydar port-call detector (AIS geofence)
Call sign changed from LAVD7 to DATAHUBAIS, seen by Voydar
Port State Control inspection at TEXAS CITY, TexasUSCG PSIX / CGMIX inspections
Inspection at Mobile, AlabamaUSCG PSIX / CGMIX inspections
ISM manager: Wallenius Marine AB (previously Hoegh Autoliners Management AS)Voydar relationship-change derivation (derived by Voydar from EU MRV (THETIS-MRV) emissions)
Port State Control inspection at Baltimore, MarylandUSCG PSIX / CGMIX inspections
Port State Control inspection at Jacksonville, FloridaUSCG PSIX / CGMIX inspections
Inspection at Portsmouth, VirginiaUSCG PSIX / CGMIX inspections
Port State Control inspection at Jacksonville, FloridaUSCG PSIX / CGMIX inspections
Inspection at Portsmouth, VirginiaUSCG PSIX / CGMIX inspections
Inspection at Woods Hole, MassachusettsUSCG PSIX / CGMIX inspections
Port State Control inspection at Mobile, AlabamaUSCG PSIX / CGMIX inspections
Port State Control inspection at Cape Canaveral, FloridaUSCG PSIX / CGMIX inspections
Reported arrival at WilmingtonAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from WilmingtonAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from JACKSONVILLE HARBOR, FLAuthority-reportedUSACE 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

44
Inspections
not recorded
Detentions
0
Deficiencies
DateTypePortFindings
Mar 19, 2024Vessel InspectionPSCTEXAS CITY, Texasclean
Mar 10, 2024Vessel InspectionMobile, Alabamaclean
Jul 18, 2021Vessel InspectionPSCBaltimore, Marylandclean
Jul 14, 2021Vessel InspectionPSCJacksonville, Floridaclean
Mar 11, 2021Vessel InspectionPortsmouth, Virginiaclean
Mar 10, 2021Vessel InspectionPSCJacksonville, Floridaclean
Nov 10, 2019BoardingPortsmouth, Virginiaclean
Jul 2, 2019BoardingWoods Hole, Massachusettsclean
Apr 24, 2019Vessel InspectionPSCMobile, Alabamaclean
Apr 29, 2018Vessel InspectionPSCCape Canaveral, Floridaclean
Sep 9, 2016Vessel InspectionPSCTEXAS CITY, Texasclean
Dec 3, 2014Vessel InspectionPSCNorth Charleston, South Carolinaclean
Nov 13, 2014BoardingPort Arthur, Texasclean
Aug 13, 2014Vessel InspectionJacksonville, Floridaclean
Aug 12, 2014Vessel InspectionJacksonville, Floridaclean
Jun 27, 2014Vessel InspectionJacksonville, Floridaclean
Apr 1, 2014Vessel InspectionJacksonville, Floridaclean
Mar 28, 2014Vessel InspectionPSCJacksonville, Floridaclean
Mar 13, 2014Vessel InspectionTEXAS CITY, Texasclean
Jan 28, 2014Vessel InspectionFPO, AP,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.

CO₂ emitted per reporting year, tonnes (EU MRV, as reported and verified). The table below has every figure.
YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
20185,294 t1,683 t57 days337 kg
20195,650 t1,797 t43 days384 kg
20208,909 t2,840 t81 days368 kg
20215,852 t1,864 t48 days330 kg
202210,581 t3,386 t107 days300 kg
202315,841 t5,061 t126 days343 kg
202413,432 t4,291 t123 days321 kg
202525,980 t8,693 t257 days320 kg

Technical efficiency: EEXI (14.63 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 2025 sits among the ships EU MRV lists as “Vehicle carrier”. Lower is less CO₂.

CO₂ per tonne of cargo carried one nautical mile59.38 g per tonne-nautical mile
Lowest reportedHighest reported

53% of the 512 ships in this group reported a lower figure.

Group: lower quartile 42.45 · median 56.04 · upper quartile 87.32

CO₂ per nautical mile sailed320.5 kg per nautical mile
Lowest reportedHighest reported

61% of the 514 ships in this group reported a lower figure.

Group: lower quartile 274.3 · median 309.1 · upper quartile 338.7

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

Time in port over the last 77 days, drawn by Voydar from the AIS-detected calls listed below. Each bar runs from arrival to departure; gaps are time away from a detected port or without reception.
PortArrivedDepartedTime in port
Zeebrugge BEZEENov 10, 2026, 21:59 UTCNov 12, 2026, 11:22 UTC37 h 23 min
Nieuwdorp NLNIUNov 5, 2026, 19:23 UTCNov 6, 2026, 23:14 UTC27 h 51 min
Piraeus GRPIROct 22, 2026, 04:39 UTCOct 22, 2026, 16:20 UTC11 h 40 min
Sagunto ESSAGOct 18, 2026, 10:25 UTCOct 18, 2026, 18:21 UTC7 h 56 min
Vigo ESVGOOct 15, 2026, 16:55 UTCOct 16, 2026, 01:38 UTC8 h 43 min
Zeebrugge BEZEEOct 10, 2026, 23:18 UTCOct 13, 2026, 07:11 UTC2 d 7 h
Cuxhaven DECUXOct 9, 2026, 05:50 UTCOct 10, 2026, 01:11 UTC19 h 21 min
Piraeus GRPIRSep 23, 2026, 04:34 UTCSep 23, 2026, 08:34 UTC3 h 59 min
Piraeus GRPIRSep 17, 2026, 03:48 UTCSep 17, 2026, 15:27 UTC11 h 39 min
Vigo ESVGOSep 11, 2026, 10:18 UTCSep 11, 2026, 19:57 UTC9 h 38 min
Zeebrugge BEZEESep 6, 2026, 00:43 UTCSep 9, 2026, 02:08 UTC3 d 1 h
Nieuwdorp NLNIUSep 2, 2026, 09:44 UTCSep 3, 2026, 14:12 UTC28 h 28 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

PortRecordDate (UTC)BerthSource
Wilmington USILGArrivalDec 22, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Wilmington USILGDepartureDec 22, 2016(date only)—USACE foreign traffic vessel entrances & clearances
JACKSONVILLE HARBOR, FLDepartureDec 20, 2016(date only)—USACE foreign traffic vessel entrances & clearances
JACKSONVILLE HARBOR, FLArrivalDec 19, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Freeport USFPODepartureDec 15, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Freeport USFPOArrivalDec 14, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Wilmington USILGArrivalSep 18, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Wilmington USILGDepartureSep 18, 2016(date only)—USACE foreign traffic vessel entrances & clearances
JACKSONVILLE HARBOR, FLArrivalSep 16, 2016(date only)—USACE foreign traffic vessel entrances & clearances
JACKSONVILLE HARBOR, FLDepartureSep 16, 2016(date only)—USACE foreign traffic vessel entrances & clearances
TURTLE RIVER, GA (INCLUDED IN BRUNSWICK HARBOR, GA)DepartureSep 15, 2016(date only)—USACE foreign traffic vessel entrances & clearances
TURTLE RIVER, GA (INCLUDED IN BRUNSWICK HARBOR, GA)ArrivalSep 14, 2016(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: February 28, 2007.

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
Nov 6, 2026, 20:42 UTC
Draught change

Reported draught went from 8.8 m to 8.3 m while in port at Nieuwdorp. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Oct 22, 2026, 11:32 UTC
Draught change

Reported draught went from 8.9 m to 8.1 m while in port at Piraeus. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Oct 5, 2026, 19:02 UTC
Two positions

This MMSI was reported in two places 2,115 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 5, 2026, 18:18 UTC
Two positions

This MMSI was reported in two places 2,114 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 5, 2026, 18:05 UTC
Two positions

This MMSI was reported in two places 2,114 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 5, 2026, 17:47 UTC
Two positions

This MMSI was reported in two places 2,115 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 5, 2026, 17:32 UTC
Two positions

This MMSI was reported in two places 2,115 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 5, 2026, 17:16 UTC
Two positions

This MMSI was reported in two places 2,115 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 5, 2026, 16:35 UTC
Two positions

This MMSI was reported in two places 2,110 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 5, 2026, 15:32 UTC
Two positions

This MMSI was reported in two places 2,104 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 5, 2026, 15:03 UTC
Two positions

This MMSI was reported in two places 2,101 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 5, 2026, 14:49 UTC
Two positions

This MMSI was reported in two places 2,099 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 5, 2026, 14:17 UTC
Two positions

This MMSI was reported in two places 2,097 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 5, 2026, 14:01 UTC
Two positions

This MMSI was reported in two places 2,095 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 5, 2026, 13:20 UTC
Two positions

This MMSI was reported in two places 2,092 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 5, 2026, 12:34 UTC
Two positions

This MMSI was reported in two places 2,090 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 5, 2026, 11:31 UTC
Two positions

This MMSI was reported in two places 2,087 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 5, 2026, 11:04 UTC
Two positions

This MMSI was reported in two places 2,084 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 5, 2026, 10:49 UTC
Two positions

This MMSI was reported in two places 2,083 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 5, 2026, 09:31 UTC
Two positions

This MMSI was reported in two places 2,059 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)

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.

How these are computed →

Frequently asked questions

What kind of ship is AUTO WAY?
AUTO WAY is a car carrier sailing under the flag of Norway, built in 2006 by Hanwha Ocean. The vessel is 199.1 m long with a beam of 32.2 m and has a gross tonnage of 59,705.
Who is recorded as the owner or manager of AUTO WAY?
Wallenius Marine is recorded as ISM manager for AUTO WAY (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 AUTO WAY?
Voydar has no matched sanctions record displayed for AUTO WAY 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. AUTO WAY has 44 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.

See a sample report (PDF)

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

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/9303558
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

Cite this page

AUTO WAY. Voydar (voydar.com). https://www.voydar.com/vessel/9303558-auto-way. Retrieved November 17, 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.

See plans

Sources and attribution

  • Data: AISHub contributors (AISHub Terms of Use (2026-10-08))
  • Wikidata (CC0 1.0)

Each fact above names its source and the date it was retrieved. Each source's licence applies to its data.

Compiled by Voydar from the sources named on this page.

Page: https://www.voydar.com/vessel/9303558-auto-way

Generated from voydar.com on Nov 17, 2026, 17:43 UTC