FEGDA
Tug · St. Kitts & Nevis · AIS Class A
In short
FEGDA (Tug, St. Kitts & Nevis flag) was last seen on AIS on , not moving, in the Baltic Sea. Its crew-entered AIS destination is LTKLJ (Klaipeda); its reported draught is 3.8 m (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 17:18 UTC).
Current voyage: from Malku ilankos juru uosto PVP/Klaipeda (departed Sep 22, 2026, 08:44 UTC) to LTKLJ (Klaipeda)
- Vessel type
- Tug
- Year built
- —
- Gross tonnage
- —
- Size (length × beam)
- —
- Registered owner
- —
Watch this ship
Get an email when FEGDA 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 FEGDA.
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
- 55.7087° N, 21.1226° E
- Area
- Baltic Sea
- StatusWhat do AIS statuses mean?
- Restricted manoeuvrability
- Speed
- 0 kn
- Course
- 221°
- Heading
- 54°
Last 30 days: 4 port calls (Malku ilankos juru uosto PVP/Klaipeda).
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
- FEGDA
- IMO numberWhat is an IMO number?
- 7529469
- MMSIWhat is an MMSI?
- 341333002
- Call signWhat is a call sign?
- V4AM7
- Vessel type
- Tug
- Gross tonnageGross tonnage vs deadweight
- —
- Length overall
- —
- Beam
- —
- Year built
- —
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.
No owner, operator or manager is recorded for this vessel yet.
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 Malku ilankos juru uosto PVP/KlaipedaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Malku ilankos juru uosto PVP/KlaipedaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Malku ilankos juru uosto PVP/KlaipedaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Malku ilankos juru uosto PVP/KlaipedaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Malku ilankos juru uosto PVP/KlaipedaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Malku ilankos juru uosto PVP/KlaipedaAIS-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.
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 |
|---|---|---|---|
| Malku ilankos juru uosto PVP/Klaipeda LTMLM | Sep 18, 2026, 09:23 UTC | Sep 22, 2026, 08:44 UTC | 3 d 23 h |
| Malku ilankos juru uosto PVP/Klaipeda LTMLM | Sep 14, 2026, 21:25 UTC | Sep 15, 2026, 13:46 UTC | 16 h 21 min |
| Malku ilankos juru uosto PVP/Klaipeda LTMLM | Sep 14, 2026, 00:22 UTC | Sep 14, 2026, 16:25 UTC | 16 h 3 min |
| Malku ilankos juru uosto PVP/Klaipeda LTMLM | Sep 8, 2026, 00:52 UTC | Sep 8, 2026, 15:39 UTC | 14 h 46 min |
| Molo juru uosto PVP/Klaipeda LTMOM | Jul 16, 2026, 12:08 UTC | Aug 3, 2026, 14:10 UTC | 18 d 2 h |
| Malku ilankos juru uosto PVP/Klaipeda LTMLM | Jul 15, 2026, 14:13 UTC | Jul 15, 2026, 20:47 UTC | 6 h 35 min |
| Pilies juru uosto PVP/Klaipeda LTPLM | Jul 14, 2026, 23:55 UTC | Jul 15, 2026, 09:54 UTC | 9 h 59 min |
| Malku ilankos juru uosto PVP/Klaipeda LTMLM | Jun 26, 2026, 21:21 UTC | Jun 28, 2026, 13:26 UTC | 40 h 6 min |
| Malku ilankos juru uosto PVP/Klaipeda LTMLM | Jun 25, 2026, 21:14 UTC | Jun 25, 2026, 22:54 UTC | 1 h 40 min |
| Malku ilankos juru uosto PVP/Klaipeda LTMLM | Jun 19, 2026, 02:37 UTC | Jun 19, 2026, 10:05 UTC | 7 h 28 min |
| Malku ilankos juru uosto PVP/Klaipeda LTMLM | Jun 15, 2026, 06:25 UTC | Jun 15, 2026, 13:15 UTC | 6 h 51 min |
| Malku ilankos juru uosto PVP/Klaipeda LTMLM | Jun 9, 2026, 19:09 UTC | Jun 15, 2026, 06:23 UTC | 5 d 11 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.
Frequently asked questions
- Where is FEGDA now?
- FEGDA (Tug, St. Kitts & Nevis flag) was last seen on AIS on Oct 3, 2026, 17:35 UTC, not moving, in the Baltic Sea. The crew-entered destination was LTKLJ (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 17:18 UTC). This report does not confirm the ship’s current route.
- What kind of ship is FEGDA?
- FEGDA is a tug sailing under the flag of St. Kitts & Nevis.
- What sanctions and inspection records does Voydar hold for FEGDA?
- Voydar has no matched sanctions record displayed for FEGDA 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 FEGDA. 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/7529469Using 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.