Legiony Polskie
Bulk carrier · Portugal · built 2016 · AIS Class A
In short
Legiony Polskie (Bulk carrier, Portugal flag) was last seen on AIS on , moored, in the port of Sagunto. Its crew-entered AIS destination is ES SAG (Sagunto); its reported draught is 10 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 11:00 UTC). It arrived there on Oct 3, 2026, 18:37 UTC. ISM manager: Polska Zegluga Morska P.P. (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
- Vessel type
- Bulk carrier
- Flag
- Portugal
- Year built
- 2016
- Gross tonnage
- 25,278
- Size (length × beam)
- 180 m
- ISM manager
- Polska Zegluga Morska P.P.
Watch this ship
Get an email when Legiony Polskie arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
Free forever. No card. A free account follows up to 5 ships and ports.
Last reported position
received- Position
- 39.6441° N, 0.2125° W
- Area
- Mediterranean Sea
- StatusWhat do AIS statuses mean?
- Moored
- Speed
- 0 kn
- Course
- 261°
- Heading
- 349°
Last 30 days: 2 port calls (Sagunto and Tanger Med).
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)Free forever. No card. New accounts include 14 days of Pro.
Try the live demo, no sign-upIdentity & particulars
- Name
- Legiony Polskie
- IMO numberWhat is an IMO number?
- 9708045
- MMSIWhat is an MMSI?
- 255917339
- Call signWhat is a call sign?
- CQ2968
- Flag
- Portugal
- Vessel type
- Bulk carrier
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 25,278
- Length overall
- 180 m
- Beam
- —
- Year built
- 2016
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 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 |
|---|---|---|
| Arrived at SaguntoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Tanger MedAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Tanger MedAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from ELIZABETH RIVER (SOUTHERN BRANCH) VAAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from SavannahAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at ELIZABETH RIVER (SOUTHERN BRANCH) VAAuthority-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 |
|---|---|---|---|---|
| 2018 | 7,707 t | 2,454 t | 154 days | 222 kg |
| 2019 | 4,448 t | 1,409 t | 102 days | 225 kg |
| 2020 | 6,432 t | 2,034 t | 116 days | 209 kg |
| 2021 | 6,169 t | 1,961 t | 97 days | 250 kg |
| 2022 | 4,560 t | 1,450 t | 75 days | 217 kg |
| 2023 | 5,839 t | 1,859 t | 103 days | 213 kg |
| 2024 | 5,962 t | 1,892 t | 97 days | 222 kg |
| 2025 | 7,901 t | 2,511 t | 137 days | 219 kg |
Technical efficiency: EEXI (4.61 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 |
|---|---|---|---|
| Sagunto ESSAG | Oct 3, 2026, 18:37 UTC | in port | — |
| Tanger Med MAPTM | Sep 30, 2026, 14:44 UTC | Oct 3, 2026, 01:09 UTC | 2 d 10 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 |
|---|---|---|---|---|
| ELIZABETH RIVER (SOUTHERN BRANCH) VA | Departure | Oct 20, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Savannah USSAV | Departure | Oct 18, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ELIZABETH RIVER (SOUTHERN BRANCH) VA | Arrival | Oct 16, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Savannah USSAV | Arrival | Oct 12, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Mobile USMOB | Arrival | Oct 3, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Mobile USMOB | Departure | Oct 3, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New Orleans USMSY | Departure | Oct 1, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New Orleans USMSY | Arrival | Sep 30, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Sep 27, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Sep 25, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: September 25, 2016.
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 Legiony Polskie now?
- Legiony Polskie (Bulk carrier, Portugal flag) was last seen on AIS on Oct 6, 2026, 11:03 UTC, moored, in the port of Sagunto. The crew-entered destination was ES SAG (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 11:00 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Legiony Polskie?
- Legiony Polskie is a bulk carrier sailing under the flag of Portugal, built in 2016. The vessel is 180 m long and has a gross tonnage of 25,278.
- Who is recorded as the owner or manager of Legiony Polskie?
- Polska Zegluga Morska P.P. is recorded as ISM manager for Legiony Polskie (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 Legiony Polskie?
- Voydar has no matched sanctions record displayed for Legiony Polskie 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 Legiony Polskie. 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/9708045Using 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.