Skip to content

IMO 8521220

Cruise ship · built 1990

IMO8521220No AIS position on record

In short

IMO 8521220 (Cruise ship) has no AIS position on record with Voydar. It can carry up to 2,053 passengers (source: Wikidata).

Vessel type
Cruise ship
Flag
—
Year built
1990
Gross tonnage
70,310
Size (length × beam)
245 m × 32 m
Registered owner
—

Watch this ship

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

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 IMO 8521220
Photo: Ocean_Village_Two.jpg: Slw1324 contribs) 18:11, 27 January 2009 (UTC) · Licence: Public domain · 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
IMO 8521220
IMO numberWhat is an IMO number?
8521220
Flag
—
Vessel type
Cruise ship
Gross tonnageGross tonnage vs deadweight
70,310
Length overall
245.1 m
Beam
32.3 m
Year built
1990

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 NawiliwiliAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from Port EvergladesAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at Port EvergladesAuthority-reportedUSACE foreign traffic vessel entrances & clearances

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.

Reported by authorities Authority-reported

PortRecordDate (UTC)BerthSource
Nawiliwili USNIJDepartureNov 24, 2002(date only)—USACE foreign traffic vessel entrances & clearances
Port Everglades USPEFDepartureApr 25, 2002(date only)—USACE foreign traffic vessel entrances & clearances
Port Everglades USPEFArrivalApr 24, 2002(date only)—USACE foreign traffic vessel entrances & clearances
San Diego USSANDepartureApr 9, 2002(date only)—USACE foreign traffic vessel entrances & clearances
San Diego USSANArrivalApr 9, 2002(date only)—USACE foreign traffic vessel entrances & clearances
Port Everglades USPEFDepartureMar 25, 2002(date only)—USACE foreign traffic vessel entrances & clearances
Port Everglades USPEFArrivalMar 25, 2002(date only)—USACE foreign traffic vessel entrances & clearances
San Diego USSANDepartureMar 10, 2002(date only)—USACE foreign traffic vessel entrances & clearances
San Diego USSANArrivalMar 10, 2002(date only)—USACE foreign traffic vessel entrances & clearances
OTHER HAWAIIAN ISLANDS AREA PORTS, HAWAII (NET)DepartureMar 4, 2002(date only)—USACE foreign traffic vessel entrances & clearances
OTHER HAWAIIAN ISLANDS AREA PORTS, HAWAII (NET)ArrivalMar 4, 2002(date only)—USACE foreign traffic vessel entrances & clearances
Nawiliwili USNIJDepartureMar 3, 2002(date only)—USACE foreign traffic vessel entrances & clearances

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

About IMO 8521220

Karnika (Formerly as Crown Princess, A'Rosa Blu, AIDAblu, Ocean Village Two & Pacific Jewel) was a cruise ship. Originally debuting in 1990, Pacific Jewel has operated for numerous cruise lines throughout her history. She debuted as Crown Princess for Princess Cruises in 1990 before being transferred to A'Rosa Cruises as A'Rosa Blu in 2002. In 2004, she was transferred to AIDA Cruises as AIDAblu. In 2007, she was transferred to Ocean Village as Ocean Village Two. In 2009, she was transferred to P&O Cruises Australia as Pacific Jewel. In 2018, she was sold to Jalesh Cruises and renamed Karnika, debuting in 2019. Jalesh Cruises ceased operating in October 2020. She was sold for scrap in Alang, India in 2020.

Summary from Wikipedia, licensed CC BY-SA.

Frequently asked questions

Where is IMO 8521220 now?
Voydar has no displayable AIS position for IMO 8521220 in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is IMO 8521220?
IMO 8521220 is a cruise ship, built in 1990 by Fincantieri. The vessel is 245.1 m long with a beam of 32.3 m and has a gross tonnage of 70,310.
What sanctions and inspection records does Voydar hold for IMO 8521220?
Voydar has no matched sanctions record displayed for IMO 8521220 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 IMO 8521220. 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/8521220
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