Track BNSF Railway inland rail container milestones.

BNSF network and terminal context

BNSF's official intermodal resources describe 27 strategically located facilities and publish facility-specific gate, free-time, flip, FIRMS-code, and driver information. The listed network includes Los Angeles, Oakland International Gateway, Seattle International Gateway, Logistics Park Chicago, Logistics Park Kansas City, Memphis, Alliance, Houston, and other western and central U.S. hubs. For a BNSF-connected import, the useful CargoScope context is the handoff from port discharge into rail departure, inland ramp arrival, availability, and drayage pickup—not a generic railroad status alone.

• Official facility resources cover 27 intermodal locations
• Key port connections include Southern California, Oakland, Seattle, Tacoma, and Portland
• Verify gate hours, free time, flips, and FIRMS codes with the responsible BNSF facility

BNSF rail milestones to watch

Intermodal rail visibility matters after discharge because a container can shift from ocean-carrier planning into inland ramp, train movement, availability, drayage appointment, and final delivery work. CargoScope helps teams keep BNSF rail context attached to the shipment instead of treating the rail leg as a separate manual lookup.

• Freight intermodal network in United States
• Container-number-first tracking workflow
• Rail ramp, availability, and handoff context where available
• Useful for importers, forwarders, drayage teams, and customer updates

Why inland rail visibility affects container operations

The inland leg often creates the operational pressure that customers feel most: a container may arrive at the port, transfer to rail, wait at a ramp, become available, miss an appointment, or create free-time exposure before a team notices. A practical visibility workflow gives operations a shared place to review what changed and decide which containers need action today.

• Reduce status checks across separate portals and emails
• Give customer-facing teams clearer update context
• Spot shipment changes before they become avoidable exceptions

Milestones to monitor around rail moves

Rail-connected container workflows usually depend on a sequence of events rather than one final status. Teams may review vessel discharge, rail departure, rail arrival, ramp availability, outgate, delivery, and empty-return context where that data is available. CargoScope keeps those signals attached to the container record so teams do not lose context between ocean, rail, and truck handoffs.

• Discharge and rail departure context
• Rail arrival, unloaded, and availability signals
• Outgate, delivery appointment, and empty-return context

Container-first rail tracking

Start with the container number when evaluating rail-connected shipment visibility. CargoScope keeps available inland rail events attached to the ocean shipment record so teams can review the handoff without treating the rail leg as a separate shipment.

What you'll see in CargoScope

The journey summary keeps the port of discharge and the final destination apart, so a container that continues inland by rail is not read as delivered at the port.

Official sources

Questions