Skip to content

AASLI

Cargo ship · Cyprus · built 1994 · AIS Class A

IMO9060778MMSI212811000Call sign5BTS6Last AIS position Oct 2, 2026, 00:33 UTC

In short

AASLI (Cargo ship, Cyprus flag) was last seen on AIS on , under way at 9.7 kn, in the North Sea. Its crew-entered AIS destination is NLEEM (Eemshaven), with an ETA of Oct 2, 2026, 23:00 UTC; its reported draught is 7 m (voyage report via BarentsWatch AIS API, received Oct 2, 2026, 00:11 UTC).

Current voyage: from Rekefjord (departed Oct 1, 2026, 16:15 UTC) to NLEEM (Eemshaven)

Vessel type
Cargo ship
Flag
Cyprus
Year built
1994
Gross tonnage
3,968
Size (length × beam)
101 m × 16 m
Registered owner
—

Watch this ship

Get an email when AASLI 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 AASLI.

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.

Photo of Globe
Photo: Leo Johannes · Licence: CC BY-SA 4.0 · via Wikimedia Commons

Last reported position

received
Position
56.9972° N, 6.3393° E
Area
North Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
9.7 kn
Course
174°
Heading
178°
56.9972° N, 6.3393° E
Open the full live map →

Last 30 days: 2 port calls (Rekefjord and Eydehavn).

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-up

Identity & particulars

Name
AASLI
IMO numberWhat is an IMO number?
9060778
MMSIWhat is an MMSI?
212811000
Call signWhat is a call sign?
5BTS6
Flag
Cyprus
Vessel type
Cargo ship
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
3,968
Length overall
100.7 m
Beam
15.9 m
Year built
1994

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.

Builder
Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026

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.

DateEventSource
Left RekefjordAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at RekefjordAIS-detectedVoydar port-call detector (AIS geofence)
Left EydehavnAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at EydehavnAIS-detectedVoydar port-call detector (AIS geofence)
Left Lindholm HavnAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Lindholm HavnAIS-detectedVoydar 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

PortArrivedDepartedTime in port
Rekefjord NOREKSep 30, 2026, 23:42 UTCOct 1, 2026, 16:15 UTC16 h 33 min
Eydehavn NOEYDSep 21, 2026, 08:01 UTCSep 21, 2026, 21:51 UTC13 h 50 min
Lindholm Havn DKLHHJun 13, 2026, 04:34 UTCJun 13, 2026, 19:31 UTC14 h 57 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.

WhenWhat we observedConfidence
Oct 1, 2026, 09:37 UTC
Draught change

Reported draught went from 4.4 m to 7 m while in port at Rekefjord. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

High (75%)

Source: BarentsWatch AIS API. Contains data under NLOD made available by BarentsWatch. Licence: NLOD 2.0 (probable).

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.

How these are computed →

Frequently asked questions

Where is AASLI now?
AASLI (Cargo ship, Cyprus flag) was last seen on AIS on Oct 2, 2026, 00:33 UTC, under way at 9.7 kn, in the North Sea. The crew-entered destination was NLEEM (voyage report via BarentsWatch AIS API, received Oct 2, 2026, 00:11 UTC). This report does not confirm the ship’s current route.
What kind of ship is AASLI?
AASLI is a cargo ship sailing under the flag of Cyprus, built in 1994 by Bodewes Shipyards. The vessel is 100.7 m long with a beam of 15.9 m and has a gross tonnage of 3,968.
What sanctions and inspection records does Voydar hold for AASLI?
Voydar has no matched sanctions record displayed for AASLI 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 AASLI. 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/9060778
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

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.

See plans