Ocean-carrier schedule-adherence ground truth

Ocean-carrier schedule-adherence ground truth: for each sailing, the schedule a carrier FIRST declared versus the departure/berth time it actually made (observed to the minute), rolled up into carrier-and-lane on-time reliability, observed median/p90 transit times, port congestion and dwell levels, blank-sailing and cut-off-slip events, plus live storm exposure on trade lanes. Collected from 26 upstream connectors with five fallback transport paths, and paired with 72,000+ forward sailings across 60+ carriers and 255 ports.

Open buyer room →

Sample

Brickroad customers

Sample this dataset before you buy it.

Your sourcing agent asks Npm 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: Marine Shipping
Instruments: equitiescommodities
Categories: AlternativeSupply Chain

Dataset card

Type: not stated
Format: Tabular/JSON records via a REST API and a hosted MCP server (sub-second cached responses); DCSA v2-style transport-event JSON (actual/estimated, departure/arrival, vessel IM0 + UN location codes); schedule tables with ETD/ETA and cut-offs
Volume: Printed on the product: 72,000+ forward sailings tracked, 4,200+ observed port calls scored, 60+ carriers live (42 carriers scored), 5,000+ lanes listed with 134 lanes scored so far, 255 ports, and 26 upstream connectors. Plus a fused port-congestion series with confidence scores and a live cyclone/storm-exposure layer.
Users: ~Low hundreds of self-serve key holders (inferred from a young self-serve startup with free migration offers, no sales call to start, a public demo key and a personal-key tier — no user count published)
History: 1 years
Update frequency: not stated
Growth: Active and early — the vendor describes scored coverage as 'growing daily' and labels thin lanes early-data; the server package is at v0.1.0 and connector count (26) and scored-lane count are still climbing from a small base.
Launched: ~2026 for SchedulesMCP (package v0.1.0 published roughly two months before the date reviewed); the shared data backbone behind it predates it, having been built for the sister container-tracking product TrackingMCP.
Delivery: not stated
Entity mapping: not stated
Sample: not stated
Point-in-time: not stated
Licence: not stated

supplier index read from their site