LEE LOO
Port tender · Poland · AIS Class B
In short
LEE LOO (Port tender, Poland flag) was last seen on AIS on , not moving, near Gdansk (Baltic Sea). Its last detected port call was at Gdynia: arrived Jun 16, 2026, left Aug 5, 2026.
- Vessel type
- Port tender
- Flag
- Poland
- Year built
- —
- Gross tonnage
- —
- Size (length × beam)
- —
- Registered owner
- —
Watch this ship
Get an email when LEE LOO 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 LEE LOO.
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
- 54.35° N, 18.7598° E
- Area
- Baltic Sea
- StatusWhat do AIS statuses mean?
- Unknown
- Speed
- 0 kn
- Course
- —
- Heading
- —
Voydar detected no port call in the last 30 days.
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
- LEE LOO
- IMO numberWhat is an IMO number?
- —
- MMSIWhat is an MMSI?
- 261007767
- Call signWhat is a call sign?
- SPG5926
- Flag
- Poland
- Vessel type
- Port tender
- Gross tonnageGross tonnage vs deadweight
- —
- Length overall
- —
- Beam
- —
- Year built
- —
PolandA 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 GdyniaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at GdyniaAIS-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 |
|---|---|---|---|
| Gdynia PLGDY | Jun 16, 2026, 07:21 UTC | Aug 5, 2026, 11:36 UTC | 50 d 4 h |
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.
Frequently asked questions
- Where is LEE LOO now?
- LEE LOO (Port tender, Poland flag) was last seen on AIS on Oct 3, 2026, 19:33 UTC, not moving, near Gdansk (Baltic Sea).
- What kind of ship is LEE LOO?
- LEE LOO is a port tender sailing under the flag of Poland.
- What sanctions and inspection records does Voydar hold for LEE LOO?
- Voydar has no matched sanctions record displayed for LEE LOO 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 LEE LOO. 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-261007767Using 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.