Molouky
Dahabiya. Operated by Dahabeyat.
Not verified as sailing checked 12 Sep 2026
We have not confirmed that this vessel is currently in service. That is a statement about our checking, not a claim that it has stopped.
Our view
A six suite boat on a fifty metre hull with three decks, which reads well, and an operator whose booking calendar has been returning a server error. Every figure we have is published for Molouky and its sister jointly, so nothing here is confirmed for this boat alone. One phone call would settle both the status and the rate, and until someone makes it this record stays unverified.
Who it suits
- Travellers who want an all suite boat at six rooms
- Anyone who wants a seven night sailing rather than the usual five
- Groups chartering the whole boat
Who it does not suit
- Anyone who wants to book online, the embarkation dates page and the calendar behind it both return a server error
- Travellers who want figures for this hull, every specification published covers Molouky and its sister together
- Anyone who wants a price, no rate is published anywhere on the operator's site
- Guests who want a pool, there is none
- Anyone who needs evidence it is currently sailing, the status here is unverified and the broken calendar is the reason
- Service style
- Six suite sailing boat run by a Cairo dahabiya brand, sold direct as five and seven night Luxor to Aswan trips, always described together with its sister ship.
- The cabin we would book
- Any of the six, chosen from the shared deck plan. The operator publishes one suites page for two boats and does not distinguish the rooms within it.
- Nearest alternative: Lazuli Karnak
- Two Egyptian dahabiyas whose operators publish nothing at hull level and sell from fleet pages. Molouky is all suite at six rooms with a broken booking calendar. Lazuli Karnak is ten cabins with a published rate and no page of its own. See its record →
Identity · 3 of 4 on file
The vessel · 7 of 13 on file
How it operates · 5 of 9 on file
Price · 0 of 5 on file
Reputation · 0 of 3 on file
What we could not establish
Every empty cell above has a reason. These are the reasons for this vessel, written down at the time the record was made, including the places where published sources contradict each other.
Molouky is operated by Dahabeyat, dahabeyat.com, address Travco Center, 26th of July Corridor, Sheikh Zayed City, Giza 12588, Egypt, info@dahabeyat.com, +20 127 999 9872, hotline 19380. No operator record has been created for this vessel on the site yet.
Dahabeyat appears to be a Travco or Jaz brand rather than an independent dahabiya house. The site footer links to linkedin.com/company/jazhotelgroup and to the JazHotelsandResorts YouTube channel, and the postal address is the Travco Center. The corporate structure was not confirmed, only those links.
The Dahabeyat fleet consists of Molouky, Yakouta, and Farouz El Nil. Molouky and Yakouta are sister ships that share one suites page and one deck plan. Every specification recorded for Molouky comes from a page that covers both vessels together, so none of it is confirmed for this hull alone. It is not known which figures, if any, differ between the two.
Farouz El Nil appears to be off sale. Its entry in the Select Liner dropdown is commented out in the page source, and its embarkation dates page states that dates are not available. Molouky and Yakouta is the only selectable liner. That is not evidence that Molouky sails; it is only evidence that it is the one the operator is still offering.
The Molouky embarkation dates page and the calendar endpoint behind it both return HTTP 500, so no bookable date can be read from outside the operator. The operating status is therefore unconfirmed.
The flag and registration are not published anywhere on the operator site. No rates, no launch year, and no refit year are published either.
The domain molouky.com is registered and redirects via 301 to dahabeyat.com.
Recorded 12 September 2026. If you can settle any of these, tell us and we will correct the record in public.
Something here wrong? Say so and we will correct it in public, with the old value left visible. See the corrections log.