Pelorus (yacht)
motor yacht built by Lürssen
Pelorus is a luxury yacht and is 115 metres (377 ft) in length.
History
Commissioned by Saudi Arabian businessman Sheikh Abdul Mohsen Abdulmalik Al-Sheikh, Pelorus was built at the Lürssen subsidiary repair shipyard in Schacht-Audorf Rendsburg, Germany. The conceptual design was completed in 1999 by Tim Heywood, work began in 2000, and the yacht entered service in 2003. It was sold to Roman Abramovich during its maiden voyage, who had it altered by Blohm & Voss, adding a second helicopter pad (on top of the wheelhouse), two B&V active fin stabilizers replaced by four zero-speed stabilizers, and modifications to the underwater exhaust, mast, and stern.
Pelorus is powered by two Wärtsilä (formerly Stork Werkspoor) 12v 26 engines designed to give continuous 3900 kW at 1000 r.p.m. On the builder's sea trial Pelorus reached the contract speed of 20 knots, but often cruises between 12 and 14 knots. While owned by Abramovich, the yacht had a full-time crew of up to 46, in addition to a large security contingent that travelled with his family. Pelorus would cruise the western Mediterranean Sea during the summers, and commonly ventured down through the Suez Canal for the winters.
In 2005, Abramovich lent Pelorus to Frank Lampard and John Terry for two weeks as a bonus for being the two best players at his English football club Chelsea F.C. the previous season, and allowed Terry to honeymoon with his new wife, Toni Poole, on the yacht in 2007.
Abramovich sold it via broker Merle Wood to David Geffen in 2011 for around US$300 million.
The public source identifies “Pelorus (yacht)” as motor yacht built by Lürssen. This brief keeps that definition visible, then builds a research path around Pelorus, yacht and motor.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Pelorus (yacht)”, the useful work is to connect “motor yacht built by Lürssen” to the records capable of establishing context and consequence.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Jun 4, 2026. The linked authority identifier is Q2036118. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1999, 2000, 2003 and 1000.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Pelorus (yacht)”, its source revision and the description used here.
- Expand the search: follow Pelorus (yacht) primary sources, Pelorus (yacht) archive and Pelorus research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Pelorus (yacht)”?
- Which institution is responsible for the underlying evidence?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “Pelorus (yacht)” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.