
Technical Data
Conditions
Overview
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
29.9668°N, 32.5498°E
View on Google Maps →Port Congestion
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.
Vessels underway broadcasting a destination that resolves to this port, closest first. Distance is the real sea route (around land and through canals). Off port is steaming time at the vessel’s passage speed; alongside adds the wait this port has actually kept comparable ships for. Berth waits vary far more than they average, so read the queue as typical, not promised. The crew’s own reported ETA is shown alongside for comparison.
| Vessel | Type | Distance | Speed | Off port | Alongside | Crew ETA |
|---|---|---|---|---|---|---|
| ZAHRA | Oil or Chemical Tanker | 31 nm | 6.3 kn | 27 Aug | 28 Aug+21h | 1 Sept |
| G FORCE | Bulk Carrier | 31 nm | 11.7 kn | 27 Aug | 28 Aug+13h | 26 Aug |
| HACI MUSA UCAK | Container Ship | 73 nm | 9.1 kn | 28 Aug | 29 Aug+26h | — |
| ELINA B | Bulk Carrier | 690 nm | 11.0 kn | 30 Aug | 31 Aug+29h | 30 Aug |
| GRIFFIN T | Oil or Chemical Tanker | 1006 nm | 13.4 kn | 30 Aug | 1 Sept+41h | 30 Aug |
| JACKY GLORY | Bulk Carrier | 1095 nm | 10.7 kn | 31 Aug | 1 Sept+13h | 31 Aug |
| CMA CGM PALAIS ROYAL | Container Ship | 1725 nm | 18.4 kn | 31 Aug | 1 Sept+22h | 31 Aug |
| PEBBLE BEACH | Bulk Carrier | 1743 nm | 12.4 kn | 2 Sept | 2 Sept | 2 Sept |
| XIN HAI TONG 811 | Bulk Carrier | 1944 nm | 14.0 kn | 2 Sept | 2 Sept+0.4h | 4 Sept |
| BAO NING LING | Bulk Carrier | ~4247 nm | 11.1 kn | — | — | 13 Sept |
| SEMA M | Bulk Carrier | ~4261 nm | 11.3 kn | — | — | — |
Network
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 349 other covered ports.
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 350 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 Aug 27, 2026.
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 Aug 27, 2026.
Conditions