Autosun
Ro-ro ship · Portugal · built 2000 · AIS Class A
In short
Autosun (Ro-ro ship, Portugal flag) was last seen on AIS on , under way at 11.9 kn, in the Bay of Biscay. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its crew-entered AIS destination is ESSDR (Santander), with an ETA of Oct 4, 2026, 08:30 UTC; its reported draught is 6.4 m (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 09:41 UTC). ISM manager: United European Car Carriers, Unipessoal Lda (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
Current voyage: from Pasajes (departed Sep 28, 2026, 11:25 UTC) to ESSDR (Santander)
- Vessel type
- Ro-ro ship
- Flag
- Portugal
- Year built
- 2000
- Gross tonnage
- 21,094
- Size (length × beam)
- —
- ISM manager
- United European Car Carriers, Unipessoal Lda
Watch this ship
Get an email when Autosun 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 Autosun.
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
- 47.1388° N, 5.3147° W
- Area
- Bay of Biscay
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 11.9 kn
- Course
- 163°
- Heading
- 159°
Last 30 days: 5 port calls (Pasajes, Santander, and Avonmouth).
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
- Autosun
- IMO numberWhat is an IMO number?
- 9227053
- MMSIWhat is an MMSI?
- 255801490
- Call signWhat is a call sign?
- CQQB
- Flag
- Portugal
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 21,094
- Length overall
- —
- Beam
- —
- Year built
- 2000
PortugalA 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 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 |
|---|---|---|
| Left PasajesAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at PasajesAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left SantanderAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at SantanderAIS-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) |
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 | 24,154 t | 7,736 t | 264 days | 305 kg |
| 2019 | 23,264 t | 7,448 t | 260 days | 315 kg |
| 2020 | 21,249 t | 6,751 t | 250 days | 317 kg |
| 2021 | 16,248 t | 5,074 t | 246 days | 266 kg |
| 2022 | 19,449 t | 6,086 t | 263 days | 277 kg |
| 2023 | 15,437 t | 6,846 t | 247 days | 228 kg |
| 2024 | 17,319 t | 5,445 t | 215 days | 290 kg |
| 2025 | 18,705 t | 5,937 t | 215 days | 309 kg |
Technical efficiency: EEXI (42 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 |
|---|---|---|---|
| Pasajes ESPAS | Sep 27, 2026, 20:06 UTC | Sep 28, 2026, 11:25 UTC | 15 h 19 min |
| Santander ESSDR | Sep 27, 2026, 04:39 UTC | Sep 27, 2026, 12:11 UTC | 7 h 33 min |
| Avonmouth GBAVO | Sep 24, 2026, 03:20 UTC | Sep 25, 2026, 03:50 UTC | 24 h 30 min |
| Avonmouth GBAVO | Sep 14, 2026, 08:53 UTC | Sep 22, 2026, 11:20 UTC | 8 d 2 h |
| Avonmouth GBAVO | Sep 7, 2026, 14:44 UTC | Sep 11, 2026, 11:35 UTC | 3 d 20 h |
| Avonmouth GBAVO | Jun 19, 2026, 06:48 UTC | Jun 20, 2026, 01:00 UTC | 18 h 12 min |
| Avonmouth GBAVO | Jun 13, 2026, 17:23 UTC | Jun 14, 2026, 19:16 UTC | 25 h 54 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 24, 2026, 21:44 UTC | Draught change Reported draught went from 7.1 m to 6.1 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
- Where is Autosun now?
- Autosun (Ro-ro ship, Portugal flag) was last seen on AIS on Oct 3, 2026, 12:16 UTC, under way at 11.9 kn, in the Bay of Biscay. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was ESSDR (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 09:41 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Autosun?
- Autosun is a ro-ro ship sailing under the flag of Portugal, built in 2000 by Tsuneishi Shipbuilding. The vessel has a gross tonnage of 21,094.
- Who is recorded as the owner or manager of Autosun?
- United European Car Carriers, Unipessoal Lda is recorded as ISM manager for Autosun (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 Autosun?
- Voydar has no matched sanctions record displayed for Autosun 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 Autosun. Missing records do not establish whether the ship has been detained.
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/9227053Using 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.