VESLEO II
Passenger ship · Norway · built 1980 · AIS Class A
In short
VESLEO II (Passenger ship, Norway flag) was last seen on AIS on , under way at 10.5 kn, in the Baltic Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its crew-entered AIS destination is STROMSTAD-SKJH VV; its reported draught is 2.5 m (voyage report via BarentsWatch AIS API, received Sep 26, 2026, 14:21 UTC).
Current voyage: from Fredrikstad (departed Aug 22, 2026, 21:09 UTC) to STROMSTAD-SKJH VV
- Vessel type
- Passenger ship
- Flag
- Norway
- Year built
- 1980
- Gross tonnage
- —
- Size (length × beam)
- 33 m
- Registered owner
- —
Watch this ship
Get an email when VESLEO II 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 VESLEO II.
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
- 58.9586° N, 11.1167° E
- Area
- Baltic Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 10.5 kn
- Course
- 164°
- Heading
- 164°
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
- VESLEO II
- IMO numberWhat is an IMO number?
- 7922867
- MMSIWhat is an MMSI?
- 259491000
- Call signWhat is a call sign?
- LJCU
- Flag
- Norway
- Vessel type
- Passenger ship
- AIS ship type
- Passenger
- Gross tonnageGross tonnage vs deadweight
- —
- Length overall
- 33.1 m
- Beam
- —
- Year built
- 1980
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.
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 FredrikstadAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at FredrikstadAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left SkjarhaldenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at SkjarhaldenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left SkjarhaldenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at SkjarhaldenAIS-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 |
|---|---|---|---|
| Fredrikstad NOFRK | Aug 22, 2026, 18:30 UTC | Aug 22, 2026, 21:09 UTC | 2 h 39 min |
| Skjarhalden NOSKH | Jul 31, 2026, 12:01 UTC | Jul 31, 2026, 14:10 UTC | 2 h 9 min |
| Skjarhalden NOSKH | Jul 27, 2026, 10:09 UTC | Jul 27, 2026, 11:28 UTC | 1 h 19 min |
| Skjarhalden NOSKH | Jul 27, 2026, 07:57 UTC | Jul 27, 2026, 10:08 UTC | 2 h 10 min |
| Skjarhalden NOSKH | Jul 15, 2026, 07:26 UTC | Jul 15, 2026, 08:17 UTC | 50 min |
| Skjarhalden NOSKH | Jul 15, 2026, 01:04 UTC | Jul 15, 2026, 01:48 UTC | 44 min |
| Skjarhalden NOSKH | Jul 14, 2026, 22:24 UTC | Jul 14, 2026, 23:17 UTC | 53 min |
| Skjarhalden NOSKH | Jul 14, 2026, 21:26 UTC | Jul 14, 2026, 22:24 UTC | 58 min |
| Skjarhalden NOSKH | Jul 14, 2026, 20:44 UTC | Jul 14, 2026, 21:26 UTC | 41 min |
| Skjarhalden NOSKH | Jul 14, 2026, 20:01 UTC | Jul 14, 2026, 20:44 UTC | 43 min |
| Skjarhalden NOSKH | Jul 14, 2026, 18:33 UTC | Jul 14, 2026, 20:00 UTC | 1 h 27 min |
| Skjarhalden NOSKH | Jul 14, 2026, 17:43 UTC | Jul 14, 2026, 18:33 UTC | 50 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.
Frequently asked questions
- Where is VESLEO II now?
- VESLEO II (Passenger ship, Norway flag) was last seen on AIS on Sep 26, 2026, 14:39 UTC, under way at 10.5 kn, in the Baltic Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was STROMSTAD-SKJH VV (voyage report via BarentsWatch AIS API, received Sep 26, 2026, 14:21 UTC). This report does not confirm the ship’s current route.
- What kind of ship is VESLEO II?
- VESLEO II is a passenger ship sailing under the flag of Norway, built in 1980. The vessel is 33.1 m long.
- What sanctions and inspection records does Voydar hold for VESLEO II?
- Voydar has no matched sanctions record displayed for VESLEO II 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 VESLEO II. 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/7922867Using 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.