developer-stated
Somabay · 10M m²
Destination total; not the measured cropped outline.
Read the size source ↗Reviewed 2026-09-28
From Soma Bay to Makadi Bay. Add the plans, fade them back, and read the real coast underneath.
Loading satellite imagery…
SATELLITE + APPROXIMATE PLAN ALIGNMENT
Drag to pan · + / − to zoom · mouse wheel scrolls the pageAt coast scale, letters match the layers. Zoom in for full names.How the plans were placed ↓
This satellite explorer covers Soma Bay to Makadi Bay. For El Gouna, Hurghada, Sahl Hasheesh and Safaga, use the wider coastal atlas ↗.
PUBLISHED AREAS / SOURCE CHECK
How big are the projects?
These are published or reported totals, not measurements of the illustrated outlines. One million square metres equals one square kilometre. The figures describe different scopes and do not establish construction progress, ownership or access.
developer total not verified
Ras Soma · Official total unverified
No project-wide total verified in the developer materials checked. Broker estimates are omitted; no size inferred from the map outline.
Read the size source ↗Reviewed 2026-09-28
developer brochure figure
Marassi Red Sea · 10M m²
September 2026 official brochure, page 14, directly states total land area of 10 million m². The website says 2,426 acres and an earlier disclosure says 2,426 feddans; those are not equivalent. The brochure figure is used as stated, without inventing a conversion. The suggested 10.09M m² has not been verified in developer material.
Read the size source ↗Published 2026-09 · Reviewed 2026-09-28
developer-stated website figure
Makadi Heights · 3.4M m²
Official website currently states 3.4M m²; older Orascom investor material states total land 3.7M m². These scopes are not reconciled. Supplied newer plan coverage is roughly 5M m² in our registration: do not treat the stated size as a measurement of that footprint or imply updated expansion area confirmed.
Read the size source ↗Reviewed 2026-09-28
developer total not verified
Makadina · Official total unverified
No project-wide total verified in the developer materials checked. Broker estimates are omitted; no size inferred from the map outline.
Read the size source ↗Reviewed 2026-09-28
news-reported; allocation unverified
Qatari Diar · 29M m²
Zawya/Refinitiv citing Asharq unnamed sources. No exact allocation polygon verified.
Read the size source ↗Published 2026-09-23 · Reviewed 2026-09-28
Ras Soma and Makadina totals are omitted until a developer source is verified. Somabay’s supplied plan crops the north. The Makadi Heights website total and wider supplied plan have different, unreconciled scopes.
Qatari Diar: 29 million m² is news-reported. The broad Makadi–Soma description does not establish an allocation polygon. Sentido Naga Bay and Sharm El Naga already exist here; neither their inclusion nor their exclusion has been verified.
Back to the satellite map ↑TWO PROJECTS / ONE WIDER DESTINATION
Read Makadi Bay in layers.
Makadi Heights is shown with its existing southwest neighbourhood and the wider plan you supplied, including the illustrated connection towards the coast.
Makadina has its own residential layer. Switch on Madinat Makadi context to see the golf, water park and hotel areas from the overall plan. These are context, not a single residential boundary.
The artwork describes plans. It does not establish what is open today or which beaches a homeowner can use.
PLACES ALREADY HERE
The north is not empty.
Sentido Naga Bay, Sharm El Naga and the mapped military site are separate landmarks north of the peninsula. A development overlay does not establish ownership of them or public access through them.
ALIGNMENT / SOURCES
Grounded in geography.
Clear about the gaps.
The base is Esri World Imagery. Plan images are positioned in geographic coordinates and move with the map. Image crops remove legends and page backgrounds; they do not assert surveyed property boundaries. Imagery is a mosaic from different dates, not a live construction feed.
Landmark alignment
Somabay
Rotation and scale are tied to the entrance road beside the solar arrays and the Sheraton main pool. The supplied illustration cuts off the far northern peninsula. Its artistic geometry does not align everywhere; this is not a survey or a record of completed construction.
Existing features in satellite imagery. Two matching features do not verify the rest of the illustration. Its far northern end is cropped.
Open supplied original ↗Project source ↗Hotel alignment
Almaza Bay Ras Soma
Rotation and scale are tied to the two identifiable main pools at Steigenberger Ras Soma. Alignment farther from the hotel is less certain; planned lagoons and marinas are not existing water features.
Existing features in satellite imagery. Both fitting points are close together at the hotel. Small differences there can produce larger differences farther west; proposed lagoons are not ground landmarks.
Open supplied original ↗Project source ↗Approximate alignment
Marassi Red Sea
Approximate fit to the satellite coastline and roads, guided by the supplied Marassi Red Sea locator. This wider plan shows more of the marina and waterfront. Lagoons, piers and internal roads depict proposals, not existing features or surveyed boundaries.
Estimated positions from the supplied locator. These three fitting points are illustrated proposals, not existing buildings or surveyed corners. They show how the artwork was positioned, not proof of the parcel.
Open supplied original ↗Project source ↗Reported corridor · exact site unknown
Qatari Diar
Reporting describes the broad corridor between Makadi Bay and Soma Bay. No polygon or point is drawn: the exact site is unknown, not a confirmed allocation. Sentido, Sharm El Naga and the mapped military site remain separate references. Their inclusion in the wider view does not establish inclusion in or exclusion from the project.
Project source ↗Approximate alignment
Makadi Heights
Supplied plan aligned to the southwest perimeter road junction, the pool of the hotel beside its northern access road, and the coastal point at the illustrated beach connection. The eastern coast connection is illustrated in the plan; this does not establish current access or completion. Approximate fit; plan revision unknown.
Existing features in satellite imagery. Matching these features does not verify every road or edge in the supplied plan, or confirm the illustrated coast connection is open.
Open supplied original ↗Project source ↗Approximate alignment
Makadina
Residential artwork fitted through the supplied overall plan, whose road junctions and service compound beside the golf course are aligned to satellite imagery. Artwork versions may differ, so internal streets and parcel edges are approximate. Plans show proposals, not verified construction or beach access.
Positions transferred through the overall plan. These residential corners are transferred references, not independently observed ground landmarks. Different artwork revisions may disagree internally.
Open supplied original ↗Project source ↗Approximate alignment
Madinat Makadi context
The wider context from the third supplied image: golf course, water park and hotel areas. Its residential portion is shown separately as Makadina. Clipped to keep surrounding satellite imagery visible; source graphics do not confirm access rights, ownership boundaries or current operating status.
Existing features in satellite imagery. This is the wider destination context, including golf, water park and hotels. It is not the Makadina residential parcel.
Open supplied original ↗Project source ↗Source record & registration details
Research reviewed 28 September 2026. Supplied plan publication dates are unknown. Landmark coordinates are public map references, not gates. The military site’s naval designation has not been independently confirmed.
- OpenStreetMap local extract · accessed 2026-09-28
- Sentido official hotel page · accessed 2026-09-28
- Emaar September 2026 brochure · accessed 2026-09-28
- Esri World Imagery service · accessed 2026-09-28
- Makadina — official project and masterplan · accessed 2026-09-28
- Makadi Heights — official masterplan · accessed 2026-09-28
Download alignment points and source notes (JSON). This records the visual registration method, not a survey accuracy certificate. Read the fitting-point explanations (JSON); explanations reviewed 3 October, saved registration reviewed 28 September 2026.
Public feature data © OpenStreetMap contributors, ODbL. Imagery © Esri and the providers credited on the map. Original artwork remains attributed to its source.