Technical Data
Port Specifications
- UNLOCODE
- EGSUZ
- Port Type
- General
- Terminals
- 6
- Berth Count
- 49
- Max Draught
- 14.6 m
- Country
- 🇪🇬 Egypt
Conditions
Current Weather
Overview
About This Port
A port at the southern entrance of the Suez Canal on the Red Sea. Serves as a transit and bunkering point for vessels transiting the canal.
Location
Coordinates
29.9668°N, 32.5498°E
View on Google Maps →Live Data
Port Congestion
30-Day Berth Occupancy Trend
Waiting Vessels Trend
Port-call activity
Arrivals, time in port and cargo operations detected from AIS — the position-inferred congestion signal, with the full dwell distribution rather than a single average.
Expected arrivals
15 inboundVessels underway broadcasting a destination that resolves to this port, closest first. Distance is the real sea route (around land and through canals); the computed ETA is at the vessel’s passage speed. The crew’s own reported ETA is shown alongside for comparison.
| Vessel | Type | Distance | Speed | ETA (computed) | Crew ETA |
|---|---|---|---|---|---|
| JAADOR | Bulk Carrier | 0 nm | 7.7 kn | 30 Jun | 29 Jun |
| NCC SHAMS | Oil or Chemical Tanker | 31 nm | 11.6 kn | 30 Jun | — |
| FLOURISH | Bulk Carrier | 31 nm | 11.4 kn | 30 Jun | 28 Jun |
| CAPE LAYLA | Bulk Carrier | 58 nm | 8.0 kn | 30 Jun | — |
| SAILON | General Cargo | 58 nm | 9.4 kn | 30 Jun | 29 Jun |
| LB GREEN | Bulk Carrier | 58 nm | 9.4 kn | 30 Jun | — |
| LONG XIANG | Crude Oil Tanker | 73 nm | 2.1 kn | 30 Jun | — |
| MXD QUANZHOU | Bulk Carrier | 193 nm | 9.6 kn | 1 Jul | — |
| AMOY FORTUNE | Bulk Carrier | 470 nm | 11.2 kn | 2 Jul | 1 Jul |
| HDX HONGYUAN | General Cargo | 659 nm | 10.7 kn | 2 Jul | 2 Jul |
| INVICTA | Crude Oil Tanker | 2349 nm | 1.0 kn | 9 Jul | 7 Jul |
| GOLDEN SUCCESSFUL 82 | Bulk Carrier | 3791 nm | 10.0 kn | 16 Jul | 14 Jul |
| VIRA 1 | Container Ship | 4249 nm | 11.1 kn | 16 Jul | 17 Jul |
| HT HONOR | Container Ship | ~4313 nm | 10.6 kn | — | 21 Jul |
| TAI XING | General Cargo | ~4396 nm | 11.0 kn | — | 14 Jul |
Network
Connectivity & hub role
How central Suez sits in the sea-route network we cover — a connectivity score across navigable distances. A higher score means the port is navigationally close to many other well-connected ports, the maritime signature of a hub.
Directly routable to 179 other covered ports.
- EGPort Said73 nm
- EGAlexandria238 nm
- CYLimassol317 nm
- TRMersin443 nm
- TRIskenderun467 nm
- GRKali Limenes512 nm
- SAPort of Jeddah643 nm
- GRPort of Piraeus669 nm
Method. A connectivity score across our own route network: a port reads higher when it is navigationally close to many other well-connected ports. The score is rescaled 0–100 within the snapshot, so the single most-connected port reads 100. Distances are Suez / Panama / Malacca-aware navigable sea miles.
Coverage. The route network spans the 180 largest commercial ports, so this ranks hubs within that covered network, not against every port on earth. The number is deterministic — no confidence grade is invented. Computed Jun 30, 2026.
Risk & quality
Port risk & quality
A coverage-weighted blend of recorded Port-State-Control detentions, marine casualties and live congestion at Suez. Higher means more risk exposure for a ship calling here — it is a count of recorded events, not a judgement of the port's management.
Built from 33% of the three signals (scored on a single signal — treat as indicative).
Method. Each signal is normalised to 0–10 against an empirical cap, then blended weighting safety (detentions 0.40, casualties 0.35) above operational congestion (0.25). A port is scored only on the signals it has data for, and the weights renormalise — a missing signal is never credited as a safe 0.
Coverage. PSC and casualty data here is regional (US, UK, Canada), so most ports show only congestion and carry a low-confidence flag. Detention/casualty counts come from a country-scoped name match (≈60% of US detentions resolve); unmatched records are dropped, not force-fit.
Detention and casualty signals are screened against open port-state-control and marine-casualty records, combined with our own AIS-derived congestion. Updated Jun 23, 2026.
Community
Port Comments