Skip to content
voydar.com

BALTIC WAVE

General cargo ship · Netherlands · built 2025 · AIS Class A

IMO9969508MMSI246415000Call signPIBVLast AIS position Nov 17, 2026, 16:41 UTC

In short

BALTIC WAVE (General cargo ship, Netherlands flag) was last seen on AIS on , under way at 6.2 kn, in the North Sea. Its crew-entered AIS destination is NLRTM (Rotterdam), with an ETA of Nov 19, 2026, 08:00 UTC; its reported draught is 4.8 m (voyage report via AISstream.io global terrestrial AIS, received Nov 17, 2026, 16:07 UTC). Registered owner: Longsky Beheer B.V. (source: ILT — Nederlands vlagregister (Netherlands flag register data)).

Current voyage: from Achterwehr (departed Nov 17, 2026, 13:13 UTC) to NLRTM (Rotterdam)

Data: AISHub contributors

Year built
2025
Gross tonnage
2,593
Size (length × beam)
88 m × 13 m
Registered owner
Longsky Beheer B.V.

Last reported position: 54.1234° N, 9.3289° E · North Sea · See on the map

Watch this ship

Get an email when BALTIC WAVE reaches Rotterdam, and when it leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.

What you would have been told

Following BALTIC WAVE over the last 24 hours would have sent 3 messages.

Detected from AIS, as of Nov 17, 2026, 17:10 UTC.

Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for BALTIC WAVE reach you the moment they happen, arrival-time changes included. When it ends you stay on Free, with a daily email, unless you keep Plus (US$7 a month). Compare plans

Get alerts on your phone: Voydar for iPhone

Last reported position

received
Position
54.1234° N, 9.3289° E
Area
North Sea
Status
Under way using engineWhat do AIS statuses mean?
Speed
6.2 kn
Course
186°
Heading
187°
Compass: course over ground 186°, heading 187°
NArrow: course. Hull: heading. As broadcast on AIS.
54.1234° N, 9.3289° E. Reference map only, not for navigation.
Locator map: Natural Earth (public domain)
54.1234° N, 9.3289° E
See it live in 3D →

Last 30 days: 10 port calls (Achterwehr, Holtenau, Nakskov, Budelsdorf, Brunsbuttel, Schiedam, and Szczecin).

Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.

Data: AISHub contributors

Pro shows BALTIC WAVE's track before the last 30 days. Voydar has recorded its port calls since October 18, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.

Try the live demo, no sign-up

Identity & particulars

Length overall 88 mone tick every 10 m

Beam 13 mPlan outline, to scale

Drawn by Voydar from the recorded type, length and beam. The side view is a drawing of the ship type, not of this ship; the length rule and the plan outline's proportions are to scale, the hull shape is not surveyed.
Name
BALTIC WAVE
IMO numberWhat is an IMO number?
9969508
MMSIWhat is an MMSI?
246415000
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 · high confidence · retrieved Nov 12, 2026
ISM manager
Source: EU MRV (THETIS-MRV) emissions · reporting year 2025 · reported · high confidence · retrieved Nov 16, 2026
Builder
Source: Wikidata · reported · high confidence · retrieved Nov 15, 2026
GS Projects B.V.(not linked to a company record)
Source: ILT — Nederlands vlagregister (Netherlands flag register data) · reported · high confidence · retrieved Nov 12, 2026

Checking ownership or sanctions for your business? Teams screen fleets by IMO, keep watch with alerts and keep a dated record. Voydar for business →

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.

DateEventSource
Left AchterwehrAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at AchterwehrAIS-detectedVoydar port-call detector (AIS geofence)
Left HoltenauAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at HoltenauAIS-detectedVoydar port-call detector (AIS geofence)
Left HoltenauAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at HoltenauAIS-detectedVoydar port-call detector (AIS geofence)
Reported arrival at GdanskAuthority-reportedUrząd Morski w Gdyni: ships in port, expected and departing (Gdynia, Gdańsk)

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.

YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
20251,811 t565 t170 days49 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.

Compared with ships of its type

Where this ship’s reported CO₂ intensity for 2025 sits among the ships EU MRV lists as “General cargo ship”. Lower is less CO₂.

CO₂ per nautical mile sailed48.6 kg per nautical mile
Lowest reportedHighest reported

6% of the 2,956 ships in this group reported a lower figure.

Group: lower quartile 74.8 · median 110.6 · upper quartile 185.8

Calculated by Voydar from the figures ships report under EU MRV. This is not a rating and not the IMO Carbon Intensity Indicator (CII). EU MRV covers ships over 5,000 gross tonnage on voyages to, from and within the EU/EEA, so the group is those ships, not the world fleet. How this is calculated

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

Time in port over the last 32 days, drawn by Voydar from the AIS-detected calls listed below. Each bar runs from arrival to departure; gaps are time away from a detected port or without reception.
PortArrivedDepartedTime in port
Achterwehr DEAWRNov 17, 2026, 12:00 UTCNov 17, 2026, 13:13 UTC1 h 14 min
Holtenau DEHTUNov 12, 2026, 03:51 UTCNov 17, 2026, 11:27 UTC5 d 7 h
Holtenau DEHTUNov 10, 2026, 18:21 UTCNov 12, 2026, 02:40 UTC32 h 19 min
Nakskov DKNAKNov 2, 2026, 20:21 UTCNov 9, 2026, 18:05 UTC6 d 21 h
Holtenau DEHTUNov 2, 2026, 13:26 UTCNov 2, 2026, 14:47 UTC1 h 21 min
Budelsdorf DEUSFNov 2, 2026, 09:46 UTCNov 2, 2026, 11:11 UTC1 h 25 min
Brunsbuttel DEBRBNov 2, 2026, 02:26 UTCNov 2, 2026, 04:28 UTC2 h 2 min
Schiedam NLSCIOct 28, 2026, 02:14 UTCOct 28, 2026, 17:01 UTC14 h 47 min
Holtenau DEHTUOct 25, 2026, 07:44 UTCOct 25, 2026, 10:06 UTC2 h 22 min
Szczecin PLSZZOct 20, 2026, 23:46 UTCOct 23, 2026, 02:03 UTC2 d 2 h
Holtenau DEHTUOct 18, 2026, 11:16 UTCOct 18, 2026, 12:28 UTC1 h 12 min
Kiel Canal DECKLOct 18, 2026, 01:32 UTCOct 18, 2026, 04:02 UTC2 h 30 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

PortRecordDate (UTC)BerthSource
Gdansk PLGDNArrivalSep 26, 2026, 03:45 UTCBytomskieUrzą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.

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.

WhenWhat we observedConfidence
Nov 9, 2026, 16:47 UTC
Draught change

Reported draught went from 4.9 m to 3 m while in port at Nakskov. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Oct 28, 2026, 17:05 UTC
Draught change

Reported draught went from 5 m to 3 m after leaving Schiedam. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Oct 15, 2026, 03:47 UTC
Draught change

Reported draught went from 3.2 m to 4.2 m while in port at Antwerpen. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
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.

How these are computed →

Frequently asked questions

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, 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 BALTIC WAVE. Missing records do not establish whether the ship has been detained.

Full Vessel Report

A dated PDF with the complete track since June 2026, every port call, ownership and flag changes, inspections, a sanctions and dark-activity screening snapshot, emissions, companies and every source.

See a sample report (PDF)

Sample: a real report for EVER GIVEN (IMO 9811000), built from public data and marked SAMPLE on every page.

Every fact on this page stays free.

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/9969508
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

Cite this page

BALTIC WAVE. Voydar (voydar.com). https://www.voydar.com/vessel/9969508-baltic-wave. Retrieved November 17, 2026.

Each fact above names its own source and date. Cite that primary source too when you rely on a fact.

Using this data in code?

Every account gets a personal API allowance: 2,500 credits a month free, 25,000 with Pro. Pro includes use in your own product. Growth and Scale add volume, and each includes one Pro membership.

See plans

Sources and attribution

  • Data: AISHub contributors (AISHub Terms of Use (2026-10-08))
  • Bron: Inspectie Leefomgeving en Transport (ILT), Vlagregister data (CC0 1.0). (CC0 1.0 (ilent.nl site-wide))
  • Wikidata (CC0 1.0)

Each fact above names its source and the date it was retrieved. Each source's licence applies to its data.

Compiled by Voydar from the sources named on this page.

Page: https://www.voydar.com/vessel/9969508-baltic-wave

Generated from voydar.com on Nov 17, 2026, 17:10 UTC