Technical Data
Port Specifications
- UNLOCODE
- CAVAN
- Port Type
- Multi-purpose
- Terminals
- 8
- Berth Count
- 30
- Max Draught
- 18.3 m
- Country
- 🇨🇦 Canada
Conditions
Current Weather
Overview
About This Port
Canada's largest port and the third-largest tonnage port in North America. A major gateway for trade with Asia-Pacific, handling containers, coal, grain, and potash.
Location
Coordinates
49.2833°N, 123.1167°W
View on Google Maps →External Resources
Official Website
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.
- · 3 h
- in port
- · 14 h
- · 14 h
- · 6 h
- · 34 h
- · 13 h
- · 14 h
- · 14 h
- · 2 h
- · 19 h
- · 9 h
- · 22 h
- · 14 h
- · 14 h
- · 14 h
- · 15 h
- · 13 h
- · 2 h
- · 20 h
- · 20 h
- · 9 h
- · 9 h
- · 3.8 d
- · 40 h
- in port
- · 2.8 d
- in port
- in port
- · 13 h
Expected arrivals
11 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 |
|---|---|---|---|---|---|
| STAR MARKELLA | Bulk Carrier | 22 nm | 12.6 kn | 30 Jun | 29 Jun |
| EMERALD PRINCESS | Passenger Ship | 64 nm | 9.7 kn | 30 Jun | 30 Jun |
| TORM DAPHNE | Oil or Chemical Tanker | 206 nm | 6.7 kn | 1 Jul | 4 Jul |
| SEA LIBRA | Bulk Carrier | 357 nm | 10.8 kn | 1 Jul | — |
| URSA MAJOR | Bulk Carrier | 2243 nm | 11.6 kn | 8 Jul | 5 Jul |
| TAI HOMAGE | Bulk Carrier | 2243 nm | 12.5 kn | 7 Jul | 5 Jul |
| BBC EMERALD | Heavy Lift Vessel | 2303 nm | 14.2 kn | 7 Jul | 7 Jul |
| GRACE HARMONY | Bulk Carrier | ~4428 nm | 13.5 kn | — | 12 Jul |
| AFRICAN ARROW | Bulk Carrier | ~4431 nm | 10.2 kn | — | 7 Jul |
| ATLAS | Bulk Carrier | ~4437 nm | 11.7 kn | — | 11 Jul |
| INDIGO LAKE | Bulk Carrier | ~4442 nm | 12.4 kn | — | 11 Jul |
Network
Connectivity & hub role
How central Port of Vancouver 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.
- USSan Francisco901 nm
- USPort of Los Angeles1,250 nm
- USPort of Long Beach1,250 nm
- PABalboa4,209 nm
- JPPort of Tokyo4,332 nm
- RUPort of Vostochny4,342 nm
- COPort of Cartagena4,537 nm
- ECGuayaquil4,546 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 Port of Vancouver. 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 67% of the three signals.
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