Port-to-port route

Shipping from Qingdao to San Juan

Port of Qingdao, China → Port of San Juan, Puerto Rico

Ocean freight from the Port of Qingdao to the Port of San Juan is an actively tracked port-to-port route on bexy, with 412 shipments on record loaded at Qingdao and discharged at San Juan. Planned port-to-port transit from Qingdao to San Juan has a median of 50 days (middle half 46–56 days, 90% within 59 days), an estimate measured from the loaded-on-board date at Qingdao to the first planned arrival at San Juan in the carrier's routing, across 28 shipments.

Shipments tracked
412
Median planned port-to-port
50 days
Median actual transit
52 days
Planned via a hub
36%

Planned port-to-port transit · Qingdao → San Juan

50days median

Middle half
46–56 days
90% within
59 days
Shipments
28

From the loaded-on-board date at Qingdao to the first planned arrival at San Juan in the carrier's routing — the carrier's planned dates, port to port, with no inland leg; spans over 120 days are left out. The middle half runs from the 25th to the 75th percentile.

Actual transit (from carrier discharge events)

52days median

Middle half 52–58 days · 90% within 73 days · n = 36 shipments with a recorded discharge

Loaded on board at Qingdao → container discharged at San Juan, from the carrier's container events: actual dates, not estimates, for only the shipments whose discharge is on record — most Bills of Lading are read after the container has been returned empty.

Qingdao to San Juan ocean freight

Measured from the carrier's container events instead of its estimates, the actual transit from Qingdao to San Juan — loaded on board to a container discharged at the port of discharge, with no inland leg — has a median of 52 days (middle half 52–58 days, 90% within 73 days) across 36 shipments with a recorded discharge at the port of discharge.

In the carrier's planned routing at the time bexy read each Bill of Lading, 36% of the 28 Qingdao-to-San Juan shipments with a planned routing to the port of discharge were planned via at least one transshipment port, most often Colon Container Terminal; the rest were planned direct from the port of loading to the port of discharge. A transshipment port here is a planned stop between those two ports that is not the place of receipt or delivery, and routings can change after booking.

By place of receipt and delivery, this cargo travels mostly on the China to Puerto Rico trade lane.

Track an Evergreen (EGLV) shipment from Qingdao to San Juan by its Bill of Lading or container number on bexy for the vessel, voyage, port milestones and container status — free, with no account needed.

Trade lanes on this route

By place of receipt and delivery; the count is this route's shipments on each lane.

Planned routing: 36% of 28 shipments with a planned routing to San Juan are planned via a transshipment port, most often Colon Container Terminal (10); the rest are planned direct. This is the carrier's planned routing when bexy read each Bill of Lading, and it can change after booking.

Recent shipments · Qingdao → San Juan

Frequently asked questions

How long does it take to ship from Qingdao to San Juan?
Planned port-to-port transit from Qingdao to San Juan has a median of 50 days (middle half 46–56 days, 90% within 59 days), an estimate measured from the loaded-on-board date at Qingdao to the first planned arrival at San Juan in the carrier's routing, across 28 shipments. These are the carrier's planned dates, port to port; any inland leg after discharge at San Juan adds time.
How long does shipping from Qingdao to San Juan actually take?
Actual transit from Qingdao to San Juan, from the carrier's container discharge events, has a median of 52 days (middle half 52–58 days, 90% within 73 days), measured from the loaded-on-board date at Qingdao to the day a container was discharged at San Juan, across 36 shipments with a recorded discharge at San Juan. These are actual dates from the carrier's container events, not estimates, port to port, and any inland leg after discharge adds time. They cover only shipments whose discharge at San Juan is on record: for most Bills of Lading bexy first reads the record after the container has been returned empty, when the discharge is no longer shown.
Is cargo from Qingdao to San Juan shipped direct or transshipped?
In the carrier's planned routing at the time bexy read each Bill of Lading, 36% of the 28 Qingdao-to-San Juan shipments with a planned routing to the port of discharge were planned via at least one transshipment port, most often Colon Container Terminal; the rest were planned direct from the port of loading to the port of discharge. A transshipment port here is a planned stop between those two ports that is not the place of receipt or delivery, and routings can change after booking.
Which trade lanes use the Qingdao to San Juan route?
By place of receipt and delivery, cargo loaded at Qingdao and discharged at San Juan travels mostly on the China to Puerto Rico trade lane on bexy.
How many shipments are tracked from Qingdao to San Juan?
bexy has 412 shipments on record loaded at Qingdao and discharged at San Juan, the most recent departing Oct 16, 2026. These are the Evergreen (EGLV) shipments on record, not the ports' total throughput.
How do I track a shipment from Qingdao to San Juan?
Enter the Evergreen (EGLV) Bill of Lading or container number on bexy to see the vessel and voyage, port milestones and estimated arrival — free, with no login required.

Browse shipments from Qingdao to San Juan

by place of receipt and delivery · filterable by date & weight

View shipments

Aggregated from 412 tracked Bills of Lading loaded at Qingdao and discharged at San Juan · planned port-to-port transit over 28 shipments · actual transit to discharge over 36 shipments with a recorded discharge · data refreshed Oct 19, 2026 · how these figures are built.

Cite this page

bexy, "Qingdao to San Juan Shipping Time — Port to Port", data as of 2026-10-19, n = 412 tracked shipments. https://bexy.io/routes/qingdao-to-san-juan

Definitions, thresholds and limitations are on the methodology page.