Vega Scorpio
Container ship · built 2010
In short
Vega Scorpio (Container ship) has no AIS position on record with Voydar.
- Vessel type
- Container ship
- Flag
- —
- Year built
- 2010
- Gross tonnage
- —
- Size (length × beam)
- 139 m
- Registered owner
- —
Watch this ship
Vega Scorpio 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
No AIS position on record for this vessel. Identity and particulars are below.
A year of history in the Terminal (Plus) · the full archive since June 1, 2026 (Pro)Free forever. No card. New accounts include 14 days of Pro.
Try the live demo, no sign-upIdentity & particulars
- Name
- Vega Scorpio
- IMO numberWhat is an IMO number?
- 9491599
- MMSIWhat is an MMSI?
- —
- Call signWhat is a call sign?
- —
- Flag
- —
- Gross tonnageGross tonnage vs deadweight
- —
- Length overall
- 139.3 m
- Beam
- —
- Year built
- 2010
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 2025 · reported · confidence 0.9 · retrieved Oct 5, 2026Source: 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 |
|---|---|---|
| ISM manager: Okyanus Ege Denizcilik Ticaret A.S. (previously CONTSHIPS MANAGEMENT INC.) | Voydar relationship-change derivation (derived by Voydar from EU MRV (THETIS-MRV) emissions) | |
| Reported departure from MiamiAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at MiamiAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from MiamiAuthority-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 |
|---|---|---|---|---|
| 2021 | 9,770 t | 3,074 t | 118 days | 343 kg |
| 2022 | 6,768 t | 2,154 t | 92 days | 309 kg |
| 2024 | 2,336 t | 738 t | 38 days | 270 kg |
| 2025 | 0 t | 0 t | 0 days | — |
Technical efficiency: EEXI (24.58 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.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Miami USMIA | Departure | Nov 26, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Miami USMIA | Arrival | Nov 26, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Miami USMIA | Departure | Nov 19, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Miami USMIA | Arrival | Nov 19, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Miami USMIA | Departure | Nov 12, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Miami USMIA | Arrival | Nov 11, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Miami USMIA | Departure | Nov 5, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Miami USMIA | Arrival | Nov 4, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| San Juan PRSJU | Departure | Aug 27, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| San Juan PRSJU | Arrival | Aug 27, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| San Juan PRSJU | Departure | Aug 13, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| San Juan PRSJU | Arrival | Aug 13, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: July 15, 2012.
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 Vega Scorpio now?
- Voydar has no displayable AIS position for Vega Scorpio in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
- What kind of ship is Vega Scorpio?
- Vega Scorpio is a container ship, built in 2010. The vessel is 139.3 m long.
- What sanctions and inspection records does Voydar hold for Vega Scorpio?
- Voydar has no matched sanctions record displayed for Vega Scorpio 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 Vega Scorpio. 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/9491599Using 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.