BALTIC WAVE
General cargo ship · Netherlands · built 2025 · AIS Class A
In short
BALTIC WAVE (General cargo ship, Netherlands flag) was last seen on AIS on , at anchor, in the Baltic Sea. Its crew-entered AIS destination is SEFLI (Flivik), with an ETA of Oct 1, 2026, 15:00 UTC; its reported draught is 3.2 m (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 11:23 UTC). Registered owner: Longsky Beheer B.V. (source: ILT — Nederlands vlagregister (Netherlands flag register data)).
Current voyage: from Ahus (departed Sep 30, 2026, 18:28 UTC) to SEFLI (Flivik)
- Vessel type
- General cargo ship
- Flag
- Netherlands
- Year built
- 2025
- Gross tonnage
- 2,593
- Size (length × beam)
- 88 m × 13 m
- Registered owner
- Longsky Beheer B.V.
Watch this ship
Get an email when BALTIC WAVE 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 BALTIC WAVE.
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
- 57.4641° N, 16.8869° E
- Area
- Baltic Sea
- StatusWhat do AIS statuses mean?
- At anchor
- Speed
- 0 kn
- Course
- 296°
- Heading
- 163°
Last 30 days: 3 port calls (Ahus, Gdansk, and Lillo).
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
- BALTIC WAVE
- IMO numberWhat is an IMO number?
- 9969508
- MMSIWhat is an MMSI?
- 246415000
- Call signWhat is a call sign?
- PIBV
- Flag
- Netherlands
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 2,593
- Length overall
- 88 m
- Beam
- 13 m
- Year built
- 2025
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.
- Registered owner
- Longsky Beheer B.V.(not linked to a company record)Source: ILT — Nederlands vlagregister (Netherlands flag register data) · reported · confidence 0.9 · retrieved Oct 1, 2026
- 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, 2026GS Projects B.V.(not linked to a company record)Source: ILT — Nederlands vlagregister (Netherlands flag register data) · reported · confidence 0.9 · retrieved Oct 1, 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 AhusAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at AhusAIS-detected | Voydar port-call detector (AIS geofence) | |
| 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) | |
| Left LilloAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at LilloAIS-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,811 t | 565 t | 170 days | 49 kg |
Technical efficiency: EEXI (11.24 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 |
|---|---|---|---|
| Ahus SEAHU | Sep 30, 2026, 07:39 UTC | Sep 30, 2026, 18:28 UTC | 10 h 49 min |
| Gdansk PLGDN | Sep 26, 2026, 03:43 UTC | Sep 27, 2026, 00:39 UTC | 20 h 56 min |
| Lillo BELIL | Sep 18, 2026, 21:23 UTC | Sep 18, 2026, 22:31 UTC | 1 h 8 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 26, 2026, 03:45 UTC | Bytomskie | 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 26, 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 |
|---|---|---|
| Sep 26, 2026, 15:05 UTC | Draught change Reported draught went from 3.2 m to 4.5 m while in port at Gdansk. Voydar infers the ship probably loaded 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 BALTIC WAVE now?
- BALTIC WAVE (General cargo ship, Netherlands flag) was last seen on AIS on Oct 2, 2026, 12:16 UTC, at anchor, in the Baltic Sea. The crew-entered destination was SEFLI (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 11:23 UTC). This report does not confirm the ship’s current route.
- What kind of ship is BALTIC WAVE?
- BALTIC WAVE is a general cargo ship sailing under the flag of Netherlands, built in 2025 by Ship and Steelbuilding (SaS). The vessel is 88 m long with a beam of 13 m and has a gross tonnage of 2,593.
- Who is recorded as the owner or manager of BALTIC WAVE?
- Longsky Beheer B.V. is recorded as Registered owner for BALTIC WAVE (source: ILT — Nederlands vlagregister (Netherlands flag register data)). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for BALTIC WAVE?
- Voydar has no matched sanctions record displayed for BALTIC WAVE 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 BALTIC WAVE. 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/9969508Using 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.