ICARUS III
Tanker · Cyprus · AIS Class A
In short
ICARUS III (Tanker, Cyprus flag) was last seen on AIS on , under way at 9.4 kn, in the Baltic Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its crew-entered AIS destination is OIL FIELD B-3; its reported draught is 8 m (voyage report via AISstream.io global terrestrial AIS, received Sep 28, 2026, 20:58 UTC). ISM manager: Technical Ship Management Ltd (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
Current voyage: from Gdansk (departed Sep 28, 2026, 20:25 UTC) to OIL FIELD B-3
- Vessel type
- Tanker
- Flag
- Cyprus
- Year built
- —
- Gross tonnage
- —
- Size (length × beam)
- —
- ISM manager
- Technical Ship Management Ltd
Watch this ship
ICARUS III 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
received- Position
- 54.5097° N, 19.0368° E
- Area
- Baltic Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 9.4 kn
- Course
- 27°
- Heading
- 30°
Last 30 days: 1 port call (Gdansk).
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
- ICARUS III
- IMO numberWhat is an IMO number?
- 9145413
- MMSIWhat is an MMSI?
- 212335000
- Call signWhat is a call sign?
- P3WM9
- Flag
- Cyprus
- Vessel type
- Tanker
- AIS ship type
- Tanker (hazardous cat. B)
- 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.
- 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 |
|---|---|---|
| Left GdanskAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported arrival at GdanskAuthority-reported | Urząd Morski w Gdyni: ships in port, expected and departing (Gdynia, Gdańsk) | |
| Arrived at GdanskAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from PORT OF SOUTH LOUISIANA (LA)Authority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from PORT OF SOUTH LOUISIANA (LA)Authority-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 | 2,237 t | 698 t | 365 days | 14,062 kg |
| 2019 | 2,215 t | 691 t | 365 days | — |
| 2020 | 2,275 t | 710 t | 326 days | 12,782 kg |
| 2021 | 2,306 t | 719 t | 365 days | 2,305,780 kg |
| 2022 | 2,278 t | 711 t | 312 days | 13,814 kg |
| 2024 | 2,356 t | 735 t | 7 days | 15,057 kg |
| 2025 | 2,480 t | 773 t | 2 days | 28,832 kg |
Technical efficiency: EIV (8.17 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 |
|---|---|---|---|
| Gdansk PLGDN | Sep 27, 2026, 14:47 UTC | Sep 28, 2026, 20:25 UTC | 29 h 39 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.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Gdansk PLGDN | Arrival | Sep 27, 2026, 16:30 UTC | BPPP Stanowisko "R" | Urząd Morski w Gdyni: ships in port, expected and departing (Gdynia, Gdańsk) |
| PORT OF SOUTH LOUISIANA (LA) | Departure | Nov 21, 2003(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORT OF SOUTH LOUISIANA (LA) | Departure | Nov 15, 2003(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORT OF SOUTH LOUISIANA (LA) | Arrival | Nov 15, 2003(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: November 15, 2003.
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.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
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 28, 2026, 17:16 UTC | Draught change Reported draught went from 11.7 m to 8 m while in port at Gdansk. 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 ICARUS III now?
- ICARUS III (Tanker, Cyprus flag) was last seen on AIS on Sep 28, 2026, 21:33 UTC, under way at 9.4 kn, in the Baltic Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was OIL FIELD B-3 (voyage report via AISstream.io global terrestrial AIS, received Sep 28, 2026, 20:58 UTC). This report does not confirm the ship’s current route.
- What kind of ship is ICARUS III?
- ICARUS III is a tanker sailing under the flag of Cyprus.
- Who is recorded as the owner or manager of ICARUS III?
- Technical Ship Management Ltd is recorded as ISM manager for ICARUS III (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 ICARUS III?
- Voydar has no matched sanctions record displayed for ICARUS III 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 ICARUS III. 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/9145413Using 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.