Normalised multi-source container lifecycle and port-availability data

Normalised multi-source container lifecycle and port-availability data: milestone and event records for ocean containers covering all carriers touching North America, joined to US terminal data (FIRMS code, last free day, holds, fees, yard locations), inland rail movement and vessel AIS positions, with carrier data refreshed several times daily and terminal data within minutes. A dedicated data-quality layer and custom-fields capability mean the asset is a curated, reconciled event history per container and shipment rather than a raw feed relay.

Open buyer room →

Sample

Brickroad customers

Sample this dataset before you buy it.

Your sourcing agent asks Terminal49 and files the sample in your catalog — private to you.

Start 7-day trialNothing is charged until the trial ends.

Coverage

Universe, instruments and categories.

Industry: TruckingApplication Software
Instruments: equitiescommodities
Categories

Dataset card

Type: not stated
Format: REST API with published developer documentation, free developer keys, an uptime status page and an assistant/app integration endpoint; delivered as JSON milestone and event records alongside a web dashboard, custom fields and document hub. Bulk historical export is a negotiated arrangement rather than a listed product.
Volume: Very large: claiming all carriers touching North America implies essentially all US import containerisation — roughly 25-30 million TEU landing in US ports annually, each generating 10-20 tracked milestone and exception events, so tens to hundreds of millions of event records per year refreshed intraday, plus terminal availability, rail and AIS layers on top.
Users: Est. low thousands of registered accounts (a free self-serve tracking tier plus paid seats and free developer keys; inferred from a public registration funnel run by a 13-person Series A company).
History: 7 years
Update frequency: not stated
Growth: Active — Series A funded with $6.5M total raised, shipping into new distribution channels (listed in an AI assistant app directory with a model-context endpoint), maintaining a public changelog, and expanding into custom fields, documents hub and integrations.
Launched: ~2018 (the provider's organisation record for this entity dates to early 2018, matching a San Francisco venture founding of that vintage with the container-tracking API as the founding product).
Delivery: not stated
Entity mapping: not stated
Sample: not stated
Point-in-time: not stated
Licence: not stated

supplier index read from their site