LEANBA
Cargo ship · Netherlands · AIS Class A
In short
LEANBA (Cargo ship, Netherlands flag) was last seen on AIS on , not moving, in the port of Rotterdam. Its crew-entered AIS destination is ROTTERDAM, with an ETA of Oct 2, 2026, 16:00 UTC (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 00:13 UTC). It arrived there on Oct 2, 2026, 15:41 UTC.
- Vessel type
- Cargo ship
- Flag
- Netherlands
- Year built
- —
- Gross tonnage
- —
- Size (length × beam)
- —
- Registered owner
- —
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.
We email you a link and a code. That creates a free account, no password or card, and follows LEANBA.
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
- 51.8992° N, 4.4894° E
- Area
- North Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 0 kn
- Course
- 0°
- Heading
- —
Last 30 days: 1 port call (Rotterdam).
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
- 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
- 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 |
|---|---|---|
| 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 |
|---|---|---|---|
| Rotterdam NLRTM | Oct 2, 2026, 15:41 UTC | in port | — |
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
- Where is LEANBA now?
- LEANBA (Cargo ship, Netherlands flag) was last seen on AIS on Oct 3, 2026, 00:40 UTC, not moving, in the port of Rotterdam. The crew-entered destination was ROTTERDAM (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 00:13 UTC). This report does not confirm the ship’s current route.
- 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 and the New Zealand Russia Sanctions 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.
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-244690603Using 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.