TRANOY
Passenger ship · Norway · built 1990 · AIS Class A
In short
TRANOY (Passenger ship, Norway flag) was last seen on AIS on , moored, near Stokmarknes (Norwegian Sea). Its crew-entered AIS destination is BOGNES-LODINGEN; its reported draught is 4.5 m (voyage report via BarentsWatch AIS API, received Oct 2, 2026, 12:05 UTC). It can carry up to 399 passengers (source: Wikidata).
Current voyage: from Svolvar Osan (departed Oct 1, 2026, 12:20 UTC) to BOGNES-LODINGEN
- Vessel type
- Passenger ship
- Flag
- Norway
- Year built
- 1990
- Gross tonnage
- 3,997
- Size (length × beam)
- 92 m
- Registered owner
- —
Watch this ship
Get an email when TRANOY 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 TRANOY.
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
- 68.4973° N, 14.8008° E
- Area
- Norwegian Sea
- StatusWhat do AIS statuses mean?
- Moored
- Speed
- 0 kn
- Course
- 251°
- Heading
- 74°
Last 30 days: at least 12 port calls (Svolvar Osan and Skrova).
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
- TRANOY
- IMO numberWhat is an IMO number?
- 8917340
- MMSIWhat is an MMSI?
- 257310500
- Call signWhat is a call sign?
- LCSA
- Flag
- Norway
- Vessel type
- Passenger ship
- AIS ship type
- Passenger
- Gross tonnageGross tonnage vs deadweight
- 3,997
- Length overall
- 92 m
- Beam
- —
- Year built
- 1990
- Passengers (maximum)
- Source: Wikidata, record Q16172050. Added to Voydar on September 23, 2026. Licence: CC0 1.0.399
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.
| Date | Event | Source |
|---|---|---|
| Left Svolvar OsanAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Svolvar OsanAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Svolvar OsanAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Svolvar OsanAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Svolvar OsanAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Svolvar OsanAIS-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 |
|---|---|---|---|
| Svolvar Osan NOSOS | Oct 1, 2026, 07:47 UTC | Oct 1, 2026, 12:20 UTC | 4 h 33 min |
| Svolvar Osan NOSOS | Oct 1, 2026, 05:51 UTC | Oct 1, 2026, 06:50 UTC | 1 h 0 min |
| Svolvar Osan NOSOS | Sep 30, 2026, 19:27 UTC | Oct 1, 2026, 05:00 UTC | 9 h 34 min |
| Svolvar Osan NOSOS | Sep 30, 2026, 13:18 UTC | Sep 30, 2026, 14:36 UTC | 1 h 18 min |
| Svolvar Osan NOSOS | Sep 30, 2026, 07:48 UTC | Sep 30, 2026, 12:21 UTC | 4 h 33 min |
| Svolvar Osan NOSOS | Sep 30, 2026, 05:57 UTC | Sep 30, 2026, 06:50 UTC | 54 min |
| Svolvar Osan NOSOS | Sep 29, 2026, 20:35 UTC | Sep 30, 2026, 05:00 UTC | 8 h 26 min |
| Svolvar Osan NOSOS | Sep 29, 2026, 15:37 UTC | Sep 29, 2026, 19:51 UTC | 4 h 14 min |
| Skrova NOSRO | Sep 29, 2026, 14:47 UTC | Sep 29, 2026, 15:30 UTC | 42 min |
| Svolvar Osan NOSOS | Sep 29, 2026, 13:22 UTC | Sep 29, 2026, 14:36 UTC | 1 h 14 min |
| Svolvar Osan NOSOS | Sep 28, 2026, 07:48 UTC | Sep 29, 2026, 12:21 UTC | 28 h 33 min |
| Svolvar Osan NOSOS | Sep 27, 2026, 20:41 UTC | Sep 28, 2026, 05:07 UTC | 8 h 26 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 TRANOY now?
- TRANOY (Passenger ship, Norway flag) was last seen on AIS on Oct 2, 2026, 12:11 UTC, moored, near Stokmarknes (Norwegian Sea). The crew-entered destination was BOGNES-LODINGEN (voyage report via BarentsWatch AIS API, received Oct 2, 2026, 12:05 UTC). This report does not confirm the ship’s current route.
- What kind of ship is TRANOY?
- TRANOY is a passenger ship sailing under the flag of Norway, built in 1990 by Trønderverftet. The vessel is 92 m long and has a gross tonnage of 3,997.
- What sanctions and inspection records does Voydar hold for TRANOY?
- Voydar has no matched sanctions record displayed for TRANOY 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 TRANOY. 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/8917340Using 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.