Bore Wave
Ro-ro ship · Netherlands · built 2022 · AIS Class A
In short
Bore Wave (Ro-ro ship, Netherlands flag) was last seen on AIS on , under way at 11.3 kn, in the Baltic Sea. Its crew-entered AIS destination is FIRAU (Rauma (Raumo)), with an ETA of Nov 17, 2026, 18:00 UTC; its reported draught is 6.8 m (voyage report via AISstream.io global terrestrial AIS, received Nov 16, 2026, 14:58 UTC). Registered owner: Rederij Bore Wave (source: ILT — Nederlands vlagregister (Netherlands flag register data)).
Current voyage: from Nieuwdorp (departed Nov 13, 2026, 05:46 UTC) to FIRAU (Rauma (Raumo))
- Vessel type
- Ro-ro ship
- Flag
- Netherlands
- Year built
- 2022
- Gross tonnage
- 9,260
- Size (length × beam)
- 122 m × 21 m
- Registered owner
- Rederij Bore Wave

Last reported position: 57.9385° N, 18.3166° E · Baltic Sea · See on the map
Shipping a car on this vessel?
Follow Bore Wave and Voydar's daily email tells you when it has reached Rauma (Raumo), and when it leaves or changes its destination.
What you would have been told
Nothing in the last 24 hours: no arrival or departure at a port. You are told the moment that changes.
Detected from AIS, as of Nov 16, 2026, 15:21 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for Bore 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
- 57.9385° N, 18.3166° E
- Area
- Baltic Sea
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 11.3 kn
- Course
- 31°
- Heading
- 31°
- Compass: course over ground 31°, heading 31°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 7 port calls (Nieuwdorp, Santander, IJmuiden/Velsen, Amsterdam, Sunila, and Rauma (Raumo)).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows Bore Wave's track before the last 30 days. Voydar has recorded its port calls since October 4, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
Length overall 121.9 mone tick every 25 m
Beam 21 mPlan outline, to scale
- Name
- Bore Wave
- IMO numberWhat is an IMO number?
- 9892896
- MMSIWhat is an MMSI?
- 246278000
- Call signWhat is a call sign?
- PEVW
- Flag
- Netherlands
- Vessel type
- Detailed type from WikidataRo-ro ship
- Gross tonnageGross tonnage vs deadweight
- 9,260
- Length overall
- 121.9 m
- Beam
- 21 m
- Year built
- 2022
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
- Rederij Bore Wave(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 years 2024–2025 · reported · high confidence · retrieved Nov 16, 2026
- Builder
- Source: Wikidata · reported · high confidence · retrieved Nov 15, 2026WUHU SHIPYARD CO. LTD(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.
| Date | Event | Source |
|---|---|---|
| Left NieuwdorpAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at NieuwdorpAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left SantanderAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at SantanderAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left IJmuiden/VelsenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at IJmuiden/VelsenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from KotkaAuthority-reported | Digitraffic Port Call API | |
| Reported arrival at KotkaAuthority-reported | Digitraffic Port Call API | |
| Reported arrival at Rauma (Raumo)Authority-reported | Digitraffic Port Call API |
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 |
|---|---|---|---|---|
| 2022 | 1,383 t | 437 t | 40 days | 128 kg |
| 2023 | 6,815 t | 2,307 t | 250 days | 106 kg |
| 2024 | 6,458 t | 2,333 t | 236 days | 100 kg |
| 2025 | 6,794 t | 2,405 t | 241 days | 104 kg |
Technical efficiency: EEXI (6.3 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 sailed103.8 kg per nautical mile
- Lowest reportedHighest reported
47% 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
| Port | Arrived | Departed | Time in port |
|---|---|---|---|
| Nieuwdorp NLNIU | Nov 12, 2026, 00:38 UTC | Nov 13, 2026, 05:46 UTC | 29 h 8 min |
| Santander ESSDR | Nov 5, 2026, 15:51 UTC | Nov 6, 2026, 19:08 UTC | 27 h 17 min |
| IJmuiden/Velsen NLIJM | Nov 2, 2026, 22:25 UTC | Nov 2, 2026, 23:31 UTC | 1 h 6 min |
| Amsterdam NLAMS | Nov 1, 2026, 22:05 UTC | Nov 2, 2026, 21:39 UTC | 23 h 33 min |
| IJmuiden/Velsen NLIJM | Nov 1, 2026, 20:03 UTC | Nov 1, 2026, 20:52 UTC | 49 min |
| Sunila FISUL | Oct 28, 2026, 03:20 UTC | Oct 28, 2026, 13:40 UTC | 10 h 20 min |
| Rauma (Raumo) FIRAU | Oct 20, 2026, 13:29 UTC | Oct 26, 2026, 21:55 UTC | 6 d 8 h |
| Nieuwdorp NLNIU | Oct 15, 2026, 04:20 UTC | Oct 15, 2026, 18:49 UTC | 14 h 29 min |
| Oostende (Ostend) BEOST | Oct 14, 2026, 23:48 UTC | Oct 15, 2026, 01:07 UTC | 1 h 19 min |
| Santander ESSDR | Oct 8, 2026, 15:10 UTC | Oct 9, 2026, 17:28 UTC | 26 h 18 min |
| IJmuiden/Velsen NLIJM | Oct 5, 2026, 20:00 UTC | Oct 5, 2026, 21:36 UTC | 1 h 36 min |
| Amsterdam NLAMS | Oct 4, 2026, 21:00 UTC | Oct 5, 2026, 19:11 UTC | 22 h 10 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 |
|---|---|---|---|---|
| Kotka FIKTK | Arrival | Oct 28, 2026, 03:45 UTC | HIEH2 | Digitraffic Port Call API |
| Rauma (Raumo) FIRAU | Arrival | Oct 20, 2026, 14:00 UTC | Ro-Ro 1 | Digitraffic Port Call API |
Records published by the authority named on each row. Earliest record for this ship: October 20, 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.
| When | What we observed | Confidence |
|---|---|---|
| Nov 12, 2026, 18:22 UTC | Draught change Reported draught went from 5.6 m to 6.8 m while in port at Nieuwdorp. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 7, 2026, 17:22 UTC | Draught change Reported draught went from 6.1 m to 5.6 m after leaving Santander. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Nov 2, 2026, 20:33 UTC | Draught change Reported draught went from 6.8 m to 6.2 m while in port at Amsterdam. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 15, 2026, 18:17 UTC | Draught change Reported draught went from 5.6 m to 6.6 m while in port at Nieuwdorp. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 5, 2026, 18:28 UTC | Draught change Reported draught went from 6.8 m to 6 m while in port at Amsterdam. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 30, 2026, 15:33 UTC | Draught change Reported draught went from 6.2 m to 6.8 m while in port at Sunila. 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.
Source: Fintraffic / digitraffic.fi, license CC 4.0 BY. Licence: CC BY 4.0.
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
- What kind of ship is Bore Wave?
- Bore Wave is a ro-ro ship sailing under the flag of Netherlands, built in 2022 by Wuhu Shipyard. The vessel is 121.9 m long with a beam of 21 m and has a gross tonnage of 9,260.
- Who is recorded as the owner or manager of Bore Wave?
- Rederij Bore Wave is recorded as Registered owner for Bore 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 Bore Wave?
- Voydar has no matched sanctions record displayed for Bore 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 Bore 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.
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.
Know this ship?
Help other readers. Member posts are shown as member content, never as sourced data.
- Date, place and an optional note
- Members who know her can answer
- Suggest a correctionChecked against sources before anything changes
More Ro-ro ships
Other ro-ro ships with full Voydar profiles. A different set each day. All ro-ro ships
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/9892896Cite this page
Bore Wave. Voydar (voydar.com). https://www.voydar.com/vessel/9892896-bore-wave. Retrieved November 16, 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 adds internal business use; API plans add building the data into your own products.