OOCL Container Tracking Scraper

🚢 OOCL Container Tracking Scraper

Track OOCL shipments in bulk. Paste container numbers, bills of lading or booking numbers and get one clean row per shipment: status, route, vessel and voyage, departure and arrival times, cargo release and customs status, and every container event with its date and place. No login, no API key, and numbers OOCL doesn't know cost nothing.

✨ Why use OOCL Container Tracking Scraper?

• 📦 Bulk tracking: hundreds or thousands of containers, bills of lading and bookings in one run, looked up in parallel.
• 🧭 Ready-to-use summary: status, origin and destination, ports of loading and discharge, vessel, voyage, ETA and the latest event on every row.
• 🛃 Release and customs status: cargo release, freight release, customs clearance, original B/L received and advance manifest filings (e.g. US 24-hour rule) for bills of lading.
• 🕓 Full event history: every container event OOCL shows, from empty pick-up to empty return, with local times and time zones.
• 🔓 No login: works from OOCL's public cargo tracking; you don't need an OOCL account.
• 💸 Pay only for shipments found: unknown or mistyped numbers are free.

🎯 Use cases

• 🚛 Freight forwarders and NVOCCs: refresh every open OOCL booking each morning and push status changes to customers.
• 🏭 Importers and exporters: know when a container is loaded, departs, arrives and is released for pick-up.
• 🛃 Customs brokers: watch cargoReleaseStatus, customsClearanceStatus and the advance manifest status per bill of lading.
• ⏰ Exception alerts: compare arrivalTime and finalDestinationEta between scheduled runs and flag delays or changed vessels.
• 🧾 Demurrage and detention control: track gate-out and empty-return events and the empty return location.
• 📊 Logistics dashboards: feed transit times, ports, vessels and services into BI tools or a TMS.

🚀 How to use

1. Paste your OOCL container, bill of lading or booking numbers into Tracking numbers, one per line.
2. Leave Number type on Auto-detect (or pick one type to skip the detection).
3. Optionally keep only shipments that are still on their way or already arrived, or shorten the event history.
4. Click Start.
5. Download the results as JSON, CSV, Excel or HTML, or read them through the API. Schedule the run to keep your list up to date.

📥 Input

{
  "trackingNumbers": ["OOCU0127070", "OOLU2162169420"],
  "trackingType": "auto",
  "shipmentStatus": "any"
}

📤 Output

One row per tracked number. The Containers and Route views show one row per container and per route leg.

Example (from a real run, shortened; party names replaced):

{
  "trackingNumber": "OOLU2162169420",
  "numberType": "billOfLading",
  "found": true,
  "status": "Completed",
  "bookingNumber": "2162169420",
  "bookingStatus": "Confirmed",
  "billOfLadingNumbers": ["2162169420"],
  "billOfLadingStatus": "B/L Ready",
  "origin": "Hong Kong",
  "destination": "Long Beach",
  "portOfLoading": "Hong Kong",
  "portOfDischarge": "Long Beach",
  "vesselName": "XIN FEI ZHOU",
  "voyage": "104E",
  "service": "PSX",
  "departureTime": "2025-09-20T15:46",
  "departureIsActual": true,
  "arrivalTime": "2025-10-07T06:05",
  "arrivalIsActual": true,
  "finalDestinationEta": "2025-10-10T17:00",
  "cargoCutoff": "2025-09-19T19:00",
  "quantity": "1169 CT",
  "currentStage": "Inbound",
  "latestEvent": "Empty Return",
  "latestEventTime": "2025-10-21T06:15",
  "latestEventLocation": "Long Beach Container Terminal (Pier E)",
  "containerCount": 1,
  "containerNumbers": ["OOLU9679728"],
  "shipper": "Example Logistics (Hong Kong) Ltd",
  "consignee": "Example Imports Inc",
  "cargoReleaseStatus": "Cleared",
  "freightReleaseStatus": "Cleared",
  "customsClearanceStatus": "Cleared",
  "customsClearanceCode": "WAC8",
  "originalBillOfLadingReceived": "N.A.(Under Sea Waybill)",
  "advancedManifestStatus": "US24 (United States): Release",
  "containers": [
    {
      "containerNumber": "OOLU9679728",
      "sizeType": "40HQ",
      "grossWeight": "6755 KG",
      "verifiedGrossMass": "10559 KG (Amended)",
      "latestEvent": "Empty Return",
      "latestEventTime": "2025-10-21T06:15",
      "latestEventTimezone": "PDT",
      "emptyPickupLocation": "HIT - Hongkong International Terminals",
      "emptyReturnLocation": "Long Beach Container Terminal (Pier E)",
      "events": [
        {
          "event": "Empty Return",
          "dateTime": "2025-10-21T06:15",
          "timezone": "PDT",
          "location": "Long Beach Container Terminal (Pier E)",
          "facilityCode": "LGB10",
          "stage": "Inbound",
          "transportMode": "Truck"
        }
      ]
    }
  ],
  "trackingUrl": "https://www.oocl.com/Pages/ExpressLink.aspx?eltype=ct&businessType=blNumber&businessNumber=OOLU2162169420&language=en",
  "trackedAt": "2026-10-21T22:09:30Z"
}

💰 Pricing

You pay $0.007 per shipment found ($7 per 1,000 results), plus platform usage for compute and residential proxy traffic, which is small: under $0.001 for a 10-number run and about $0.02 per 1,000 numbers on long lists in our test runs. Numbers OOCL doesn't know, invalid entries and shipments skipped by your filters are not charged.

Example: tracking 1,000 containers that all exist costs about $7.02 in total; a run of 10 costs about $0.071.

❓ FAQ

Is it legal to track OOCL shipments? The actor reads the same public cargo tracking OOCL offers on its website, for the numbers you supply. Only track shipments you have a business reason to follow, and check the terms that apply to you. This actor is not affiliated with OOCL.

Do I need an OOCL account or a proxy? No account is needed. The actor uses residential exits by default because OOCL's tracking service refuses datacenter addresses; that traffic is part of the usage charge (about 5 KB per number on long lists, up to 25 KB on very short ones).

How many numbers can I track per run? As many as you like. Numbers are tracked in parallel and results are saved as they arrive, so long lists stream in steadily.

What if a number isn't found or a field is empty? Unknown numbers are skipped and not charged (turn on includeNotFound to get a free row for each). Fields stay empty when OOCL has no value yet, e.g. release and customs status before arrival, or the ATA before the vessel arrives.

Booking or bill of lading? Auto-detect handles both: a container number is recognised by its format, other numbers are tried as a booking and as a bill of lading. With or without the OOLU prefix works.

Can I schedule it or use the API? Yes. Schedule the actor to refresh your list daily and connect it to webhooks, or start runs and read the dataset through the API.

⚠️ Limits

• Only OOCL shipments. Numbers of other carriers return no result.
• One row per tracked number. When OOCL lists more than one shipment for a reused container, the row shows the first (current) one and otherShipments says how many more exist.
• Times are local times as OOCL shows them, with the time zone in separate fields.
• Party names, references and release details appear only when OOCL shows them for that number.