BONANZA
Cargo ship · Netherlands · AIS Class A
In short
BONANZA (Cargo ship, Netherlands flag) was last seen on AIS on , moored, near Terneuzen (North Sea). Its reported AIS draught is 2 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 10:18 UTC). Its last detected port call was at Gent (Ghent): arrived Sep 30, 2026, left Oct 1, 2026.
- Vessel type
- Cargo ship
- Flag
- Netherlands
- Year built
- —
- Gross tonnage
- —
- Size (length × beam)
- —
- Registered owner
- —
Watch this ship
Get an email when BONANZA 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
- 51.3314° N, 3.8237° E
- Area
- North Sea
- StatusWhat do AIS statuses mean?
- Moored
- Speed
- 0 kn
- Course
- 84°
- Heading
- 195°
Last 30 days: 2 port calls (Gent (Ghent) and Terneuzen).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows BONANZA's track before the last 30 days. Voydar has recorded its port calls since June 15, 2026.Free forever. No card. New accounts include 14 days of Pro.
Try the live demo, no sign-upIdentity & particulars
- Name
- BONANZA
- IMO numberWhat is an IMO number?
- —
- MMSIWhat is an MMSI?
- 244650925
- Call signWhat is a call sign?
- PI2659
- Flag
- Netherlands
- Vessel type
- Cargo ship
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- —
- Length overall
- —
- Beam
- —
- Year built
- —
NetherlandsA 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.
No owner, operator or manager is recorded for this vessel yet.
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 Gent (Ghent)AIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Gent (Ghent)AIS-detected | Voydar port-call detector (AIS geofence) | |
| Left TerneuzenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at TerneuzenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left DordrechtAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at DordrechtAIS-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.
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 |
|---|---|---|---|
| Gent (Ghent) BEGNE | Sep 30, 2026, 23:32 UTC | Oct 1, 2026, 12:45 UTC | 13 h 13 min |
| Terneuzen NLTNZ | Sep 22, 2026, 18:07 UTC | Sep 24, 2026, 12:34 UTC | 42 h 28 min |
| Dordrecht NLDOR | Jun 19, 2026, 07:09 UTC | Jun 26, 2026, 08:21 UTC | 7 d 1 h |
| Hoek van Holland NLHVH | Jun 15, 2026, 16:17 UTC | Jun 16, 2026, 05:02 UTC | 12 h 45 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.
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 |
|---|---|---|
| Oct 2, 2026, 08:18 UTC | Draught change Reported draught went from 4.5 m to 2 m after leaving Gent (Ghent). Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 24, 2026, 15:41 UTC | Draught change Reported draught went from 2 m to 4.5 m after leaving Terneuzen. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 23, 2026, 05:29 UTC | Draught change Reported draught went from 4.5 m to 2 m while in port at Terneuzen. 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 BONANZA now?
- BONANZA (Cargo ship, Netherlands flag) was last seen on AIS on Oct 6, 2026, 10:35 UTC, moored, near Terneuzen (North Sea).
- What kind of ship is BONANZA?
- BONANZA is a cargo ship sailing under the flag of Netherlands.
- What sanctions and inspection records does Voydar hold for BONANZA?
- Voydar has no matched sanctions record displayed for BONANZA 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 BONANZA. 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/mmsi-244650925Using 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.