LEANBA
Cargo ship · Netherlands · AIS Class A
In short
LEANBA (Cargo ship, Netherlands flag) was last seen on AIS on , not moving, in the North Sea. Its crew-entered AIS destination is ZWOLLE ALMELO (voyage report via AISstream.io global terrestrial AIS, received Nov 18, 2026, 09:39 UTC).
Current voyage: from Amsterdam (departed Nov 13, 2026, 15:55 UTC) to ZWOLLE ALMELO
- Vessel type
- Cargo ship
- Flag
- Netherlands
- Year built
- —
- Gross tonnage
- —
- Size, AIS-reported (length × beam)
- 80 m × 8 m
- Registered owner
- —
Last reported position: 52.3662° N, 6.6343° E · North Sea · See on the map
Watch this ship
Get an email when LEANBA arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
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 19, 2026, 08:13 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for LEANBA 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: the Voydar app
Last reported position
received- Position
- 52.3662° N, 6.6343° E
- Area
- North Sea
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 0 kn
- Course
- 0°
- Heading
- —
- Compass: course over ground 0°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 6 port calls (Amsterdam, Hoek van Holland, and Rotterdam).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows LEANBA's track before the last 30 days. Voydar has recorded its port calls since September 24, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
- Name
- LEANBA
- IMO numberWhat is an IMO number?
- —
- MMSIWhat is an MMSI?
- 244690603
- Call signWhat is a call sign?
- PF7798
- Flag
- Netherlands
- Vessel type
- Cargo ship
- Gross tonnageGross tonnage vs deadweight
- —
- Length (AIS-reported)
- Broadcast by the ship over AIS, not a register entry. Received via AISstream.io global terrestrial AIS on November 18, 2026.80 m
- Beam (AIS-reported)
- Broadcast by the ship over AIS, not a register entry. Received via AISstream.io global terrestrial AIS on November 18, 2026.8 m
- 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.
AIS-reported: the size the ship itself broadcasts over AIS, in whole metres, as entered on board. It is not a register entry. Received via AISstream.io global terrestrial AIS on November 18, 2026.
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.
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 AmsterdamAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at AmsterdamAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Hoek van HollandAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Hoek van HollandAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left RotterdamAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at RotterdamAIS-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 |
|---|---|---|---|
| Amsterdam NLAMS | Nov 13, 2026, 14:24 UTC | Nov 13, 2026, 15:55 UTC | 1 h 31 min |
| Hoek van Holland NLHVH | Nov 12, 2026, 13:32 UTC | Nov 12, 2026, 20:07 UTC | 6 h 34 min |
| Rotterdam NLRTM | Nov 11, 2026, 16:34 UTC | Nov 12, 2026, 12:01 UTC | 19 h 27 min |
| Rotterdam NLRTM | Nov 10, 2026, 15:34 UTC | Nov 11, 2026, 12:46 UTC | 21 h 12 min |
| Amsterdam NLAMS | Nov 3, 2026, 18:16 UTC | Nov 5, 2026, 05:07 UTC | 34 h 51 min |
| Amsterdam NLAMS | Oct 26, 2026, 18:21 UTC | Oct 28, 2026, 14:46 UTC | 44 h 25 min |
| Amsterdam NLAMS | Oct 8, 2026, 23:13 UTC | Oct 9, 2026, 07:50 UTC | 8 h 37 min |
| Amsterdam NLAMS | Oct 5, 2026, 19:58 UTC | Oct 6, 2026, 04:12 UTC | 8 h 15 min |
| Rotterdam NLRTM | Oct 2, 2026, 15:41 UTC | Oct 5, 2026, 11:48 UTC | 2 d 20 h |
| Amsterdam NLAMS | Sep 28, 2026, 09:44 UTC | Sep 29, 2026, 11:32 UTC | 25 h 48 min |
| Amsterdam NLAMS | Sep 24, 2026, 14:40 UTC | Sep 24, 2026, 16:17 UTC | 1 h 37 min |
| Dordrecht NLDOR | Sep 24, 2026, 04:06 UTC | Sep 24, 2026, 05:34 UTC | 1 h 28 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 |
|---|---|---|
| Sep 27, 2026, 17:17 UTC | Alongside another ship Stayed within 90 m of SEMPACHERSEE at low speed for 10 h 50 min, 15 km from the nearest port and outside known anchorages. A candidate ship-to-ship transfer; many such meetings are routine and licensed. SEMPACHERSEE →Method seadar.behaviour.sts_candidate v1 | Medium (70%) |
| Sep 27, 2026, 15:37 UTC | Alongside another ship Stayed within 157 m of NOVALIS at low speed for 13 h 20 min, 15 km from the nearest port and outside known anchorages. A candidate ship-to-ship transfer; many such meetings are routine and licensed. NOVALIS →Method seadar.behaviour.sts_candidate v1 | Medium (60%) |
| Sep 26, 2026, 14:17 UTC | Alongside another ship Stayed within 154 m of CORI-JO at low speed for 12 h 30 min, 15 km from the nearest port and outside known anchorages. A candidate ship-to-ship transfer; many such meetings are routine and licensed. CORI-JO →Method seadar.behaviour.sts_candidate v1 | Medium (60%) |
| Sep 26, 2026, 12:27 UTC | Alongside another ship Stayed within 150 m of GODORF at low speed for 16 h 40 min, 15 km from the nearest port and outside known anchorages. A candidate ship-to-ship transfer; many such meetings are routine and licensed. GODORF →Method seadar.behaviour.sts_candidate v1 | Medium (60%) |
| Sep 26, 2026, 09:27 UTC | Alongside another ship Stayed within 6 m of BENTHE at low speed for 31 h 10 min, 15 km from the nearest port and outside known anchorages. A candidate ship-to-ship transfer; many such meetings are routine and licensed. BENTHE →Method seadar.behaviour.sts_candidate v1 | Medium (70%) |
| Sep 26, 2026, 01:27 UTC | Alongside another ship Stayed within 15 m of PAULINE at low speed for 2 d 3 h, 15 km from the nearest port and outside known anchorages. A candidate ship-to-ship transfer; many such meetings are routine and licensed. PAULINE →Method seadar.behaviour.sts_candidate v1 | Medium (70%) |
| Sep 26, 2026, 00:57 UTC | Alongside another ship Stayed within 110 m of ZELDENRUST at low speed for 2 d 4 h, 15 km from the nearest port and outside known anchorages. A candidate ship-to-ship transfer; many such meetings are routine and licensed. ZELDENRUST →Method seadar.behaviour.sts_candidate v1 | Medium (60%) |
| Sep 24, 2026, 20:27 UTC | Alongside another ship Stayed within 138 m of MIA AMORE at low speed for 9 h 10 min, 15 km from the nearest port and outside known anchorages. A candidate ship-to-ship transfer; many such meetings are routine and licensed. MIA AMORE →Method seadar.behaviour.sts_candidate v1 | Medium (60%) |
| Sep 24, 2026, 20:17 UTC | Alongside another ship Stayed within 147 m of CLAUDIA at low speed for 9 h 20 min, 15 km from the nearest port and outside known anchorages. A candidate ship-to-ship transfer; many such meetings are routine and licensed. CLAUDIA →Method seadar.behaviour.sts_candidate v1 | Medium (60%) |
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
- What kind of ship is LEANBA?
- LEANBA is a cargo ship sailing under the flag of Netherlands.
- What sanctions and inspection records does Voydar hold for LEANBA?
- Voydar has no matched sanctions record displayed for LEANBA 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 LEANBA. Missing records do not establish whether the ship has been detained.
More Cargo ships
Other cargo ships with full Voydar profiles, those under the flag of Netherlands first. A different set each day. All cargo 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/mmsi-244690603Cite this page
LEANBA. Voydar (voydar.com). https://www.voydar.com/vessel/mmsi-244690603-leanba. Retrieved November 19, 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.