Skip to content

Orient Queen II

Cruise ship · built 1989

IMO8701193No AIS position on record

In short

Orient Queen II (Cruise ship) has no AIS position on record with Voydar. It can carry up to 300 passengers (source: Wikidata).

Vessel type
Cruise ship
Flag
—
Year built
1989
Gross tonnage
7,478
Size (length × beam)
117 m × 17 m
Registered owner
—

Watch this ship

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

Photo of Orient Queen II
Photo: Trondheim Havn from Trondheim, Norway · Licence: CC BY-SA 2.0 · via Wikimedia Commons

Last reported position

No AIS position on record for this vessel. Identity and particulars are 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
Orient Queen II
IMO numberWhat is an IMO number?
8701193
Flag
—
Vessel type
Cruise ship
Gross tonnageGross tonnage vs deadweight
7,478
Length overall
117.4 m
Beam
16.8 m
Year built
1989

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
Reported departure from ST. THOMAS HARBOR, VIAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at ST. THOMAS HARBOR, VIAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from ST. THOMAS HARBOR, VIAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Former name: VistamarWikidata

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.

Former and other names

Names attested for this ship other than its current name.

NameEvidenceDateSource
VistamarFormer nameJan 1, 1989Wikidata

A sanctions list's date is the earliest date the list shows the name, not when the ship took it. A name on a list is shown as a former name only where AIS shows the ship using another name after that date; otherwise it is listed as a name the list uses. AIS name changes are dated when Voydar saw them.

Source: Wikidata. Licence: CC0 1.0.

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.

Reported by authorities Authority-reported

PortRecordDate (UTC)BerthSource
ST. THOMAS HARBOR, VIDepartureApr 9, 2005(date only)—USACE foreign traffic vessel entrances & clearances
ST. THOMAS HARBOR, VIArrivalApr 9, 2005(date only)—USACE foreign traffic vessel entrances & clearances
ST. THOMAS HARBOR, VIDepartureFeb 22, 2004(date only)—USACE foreign traffic vessel entrances & clearances
ST. THOMAS HARBOR, VIArrivalFeb 20, 2004(date only)—USACE foreign traffic vessel entrances & clearances
San Juan PRSJUDepartureFeb 19, 2004(date only)—USACE foreign traffic vessel entrances & clearances
San Juan PRSJUArrivalFeb 19, 2004(date only)—USACE foreign traffic vessel entrances & clearances
ST. THOMAS HARBOR, VIDepartureMar 11, 2003(date only)—USACE foreign traffic vessel entrances & clearances
ST. THOMAS HARBOR, VIArrivalMar 11, 2003(date only)—USACE foreign traffic vessel entrances & clearances
San Juan PRSJUDepartureMar 10, 2003(date only)—USACE foreign traffic vessel entrances & clearances
San Juan PRSJUArrivalMar 10, 2003(date only)—USACE foreign traffic vessel entrances & clearances
Key West USEYWDepartureFeb 28, 2003(date only)—USACE foreign traffic vessel entrances & clearances
Key West USEYWArrivalFeb 28, 2003(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: December 27, 2002.

About Orient Queen II

Orient Queen was a former cruise ship built in 1989 for the company Mar Lines by the Unión Naval de Levante shipyard in Valencia, Spain. On 4 August 2020, the ship was badly damaged by an explosion in Beirut, Lebanon, near where she was berthed, and subsequently capsized.

Summary from Wikipedia, licensed CC BY-SA.

Frequently asked questions

Where is Orient Queen II now?
Voydar has no displayable AIS position for Orient Queen II in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is Orient Queen II?
Orient Queen II is a cruise ship, built in 1989 by Unión Naval de Levante. The vessel is 117.4 m long with a beam of 16.8 m and has a gross tonnage of 7,478.
What sanctions and inspection records does Voydar hold for Orient Queen II?
Voydar has no matched sanctions record displayed for Orient Queen II 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 Orient Queen 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/8701193
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