GT VELA
General cargo ship · Antigua & Barbuda · built 1991 · AIS Class A
In short
GT VELA (General cargo ship, Antigua & Barbuda flag) was last seen on AIS on , under way at 9.6 kn, in the Baltic Sea. Its crew-entered AIS destination is LVRIX (Riga), with an ETA of Oct 2, 2026, 16:00 UTC; its reported draught is 3.4 m (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 20:23 UTC). ISM manager: GT Vela Shipping Ltd (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).
Current voyage: from Liepaja (departed Oct 1, 2026, 19:12 UTC) to LVRIX (Riga)
- Vessel type
- General cargo ship
- Year built
- 1991
- Gross tonnage
- 2,481
- Size (length × beam)
- 87 m × 13 m
- ISM manager
- GT Vela Shipping Ltd
Watch this ship
Get an email when GT VELA 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 GT VELA.
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
- 56.7918° N, 20.8212° E
- Area
- Baltic Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 9.6 kn
- Course
- 354°
- Heading
- 356°
Last 30 days: 3 port calls (Liepaja, Gdynia, and Szczecin).
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
- GT VELA
- IMO numberWhat is an IMO number?
- 8912027
- MMSIWhat is an MMSI?
- 305970000
- Call signWhat is a call sign?
- V2UE
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 2,481
- Deadweight (DWT)
- Source: Wikidata, record Q83652825. Added to Voydar on September 23, 2026. Licence: CC0 1.0.3,269 t
- Length overall
- 87.4 m
- Beam
- 13 m
- Year built
- 1991
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 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 LiepajaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at LiepajaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left GdyniaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported arrival at GdyniaAuthority-reported | Urząd Morski w Gdyni: ships in port, expected and departing (Gdynia, Gdańsk) | |
| Arrived at GdyniaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left SzczecinAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at SzczecinAIS-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 |
|---|---|---|---|---|
| 2025 | 1,761 t | 549 t | 121 days | 72 kg |
Technical efficiency: EEXI (17.94 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 |
|---|---|---|---|
| Liepaja LVLPX | Sep 30, 2026, 12:30 UTC | Oct 1, 2026, 19:12 UTC | 30 h 42 min |
| Gdynia PLGDY | Sep 26, 2026, 03:41 UTC | Sep 29, 2026, 19:30 UTC | 3 d 15 h |
| Szczecin PLSZZ | Sep 22, 2026, 16:03 UTC | Sep 24, 2026, 18:43 UTC | 2 d 2 h |
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 |
|---|---|---|---|---|
| Gdynia PLGDY | Arrival | Sep 28, 2026, 04:20 UTC | Wendy | Urząd Morski w Gdyni: ships in port, expected and departing (Gdynia, Gdańsk) |
Records published by the authority named on each row. Earliest record for this ship: September 28, 2026.
Source: Urząd Morski w Gdyni (www.umgdy.gov.pl); processed by Seadar (times converted to UTC, IMO checksum-validated). The retrieval date is shown with the data. Licence: Polish PSI reuse (ustawa o otwartych danych), conditions: cite source, date, processing.
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 |
|---|---|---|
| Oct 1, 2026, 09:05 UTC | Draught change Reported draught went from 5.2 m to 3.4 m while in port at Liepaja. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 29, 2026, 16:37 UTC | Draught change Reported draught went from 3.4 m to 5.2 m while in port at Gdynia. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 24, 2026, 16:19 UTC | Draught change Reported draught went from 5.2 m to 3.4 m while in port at Szczecin. 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 GT VELA now?
- GT VELA (General cargo ship, Antigua & Barbuda flag) was last seen on AIS on Oct 1, 2026, 20:53 UTC, under way at 9.6 kn, in the Baltic Sea. The crew-entered destination was LVRIX (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 20:23 UTC). This report does not confirm the ship’s current route.
- What kind of ship is GT VELA?
- GT VELA is a general cargo ship sailing under the flag of Antigua & Barbuda, built in 1991 by ENVC Shipyard. The vessel is 87.4 m long with a beam of 13 m and has a gross tonnage of 2,481.
- Who is recorded as the owner or manager of GT VELA?
- GT Vela Shipping Ltd is recorded as ISM manager for GT VELA (source: EU MRV (THETIS-MRV) emissions; reporting year 2025). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for GT VELA?
- Voydar has no matched sanctions record displayed for GT VELA from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels and the New Zealand Russia Sanctions Register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for GT VELA. 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/8912027Using 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.