Aurora
Container ship · Antigua & Barbuda · built 2001 · AIS Class A
In short
Aurora (Container ship, Antigua & Barbuda flag) was last seen on AIS on , under way at 15.4 kn, in the English Channel. Its crew-entered AIS destination is IEDUB (Dublin), with an ETA of Oct 5, 2026, 05:00 UTC; its reported draught is 8.3 m (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 18:40 UTC). ISM manager: TAS Transatlantische Schifffahrts GmbH & Co. KG (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
Current voyage: from Zeebrugge (departed Oct 3, 2026, 11:08 UTC) to IEDUB (Dublin)
- Vessel type
- Container ship
- Year built
- 2001
- Gross tonnage
- 9,981
- Size (length × beam)
- 134 m × 23 m
Watch this ship
Get an email when Aurora 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 Aurora.
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
- 50.6736° N, 0.6231° E
- Area
- English Channel
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 15.4 kn
- Course
- 235°
- Heading
- 233°
Last 30 days: 8 port calls (Zeebrugge, Lillo, Dun Laoghaire, Dublin-Marine Terminal, and ESB Poolbeg-Dublin).
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
- Aurora
- IMO numberWhat is an IMO number?
- 9234989
- MMSIWhat is an MMSI?
- 304080000
- Call signWhat is a call sign?
- V2GS9
- Vessel type
- Container ship
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 9,981
- Deadweight (DWT)
- Source: Wikidata, record Q52351148. Added to Voydar on September 23, 2026. Licence: CC0 1.0.11,386 t
- Length overall
- 134.4 m
- Beam
- 22.8 m
- Year built
- 2001
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 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 ZeebruggeAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at ZeebruggeAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left LilloAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at LilloAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Dun LaoghaireAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Dun LaoghaireAIS-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 | 8,021 t | 2,539 t | 216 days | 257 kg |
| 2019 | 9,530 t | 2,985 t | 232 days | 270 kg |
| 2020 | 13,848 t | 4,319 t | 181 days | 239 kg |
| 2021 | 9,434 t | 2,943 t | 129 days | 247 kg |
| 2022 | 9,833 t | 3,077 t | 133 days | 257 kg |
| 2023 | 10,592 t | 3,305 t | 169 days | 250 kg |
| 2024 | 11,500 t | 3,627 t | 166 days | 258 kg |
| 2025 | 6,775 t | 2,143 t | 97 days | 287 kg |
Technical efficiency: EEXI (11 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 |
|---|---|---|---|
| Zeebrugge BEZEE | Oct 2, 2026, 20:47 UTC | Oct 3, 2026, 11:08 UTC | 14 h 21 min |
| Lillo BELIL | Oct 1, 2026, 03:13 UTC | Oct 1, 2026, 17:08 UTC | 13 h 55 min |
| Dun Laoghaire IEDLG | Sep 27, 2026, 16:56 UTC | Sep 29, 2026, 02:16 UTC | 33 h 20 min |
| Dublin-Marine Terminal IEMTL | Sep 26, 2026, 07:46 UTC | Sep 27, 2026, 16:56 UTC | 33 h 10 min |
| Lillo BELIL | Sep 22, 2026, 13:34 UTC | Sep 23, 2026, 00:33 UTC | 10 h 59 min |
| ESB Poolbeg-Dublin IEESB | Sep 20, 2026, 13:09 UTC | Sep 22, 2026, 10:58 UTC | 45 h 49 min |
| Dublin-Marine Terminal IEMTL | Sep 11, 2026, 20:46 UTC | Sep 20, 2026, 13:09 UTC | 8 d 16 h |
| Lillo BELIL | Sep 8, 2026, 15:25 UTC | Sep 9, 2026, 03:35 UTC | 12 h 10 min |
| Lillo BELIL | Jun 9, 2026, 18:36 UTC | Jun 10, 2026, 18:45 UTC | 24 h 10 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 27, 2026, 17:25 UTC | Draught change Reported draught went from 8.2 m to 6.1 m while in port at Dun Laoghaire. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
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 Aurora now?
- Aurora (Container ship, Antigua & Barbuda flag) was last seen on AIS on Oct 3, 2026, 18:56 UTC, under way at 15.4 kn, in the English Channel. The crew-entered destination was IEDUB (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 18:40 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Aurora?
- Aurora is a container ship sailing under the flag of Antigua & Barbuda, built in 2001 by Pella Sietas. The vessel is 134.4 m long with a beam of 22.8 m and has a gross tonnage of 9,981.
- Who is recorded as the owner or manager of Aurora?
- TAS Transatlantische Schifffahrts GmbH & Co. KG is recorded as ISM manager for Aurora (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 Aurora?
- Voydar has no matched sanctions record displayed for Aurora 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 Aurora. 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/9234989Using 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.