Carrier-sourced container vessel schedule data delivered as bulk files

Carrier-sourced container vessel schedule data delivered as bulk files: operational vessel schedules in port-rotation format with one record per port call (carrier code and name, service code and name, vessel IMO, name and voyage, port code and name, estimated arrival and departure, port-call sequence and total, plus two update timestamps), origin-destination port-pair commercial schedules with transhipment legs, a vessel register layer (flag, call sign, deadweight, TEU and reefer capacity, ship type, port of registry, year built), terminal names and codes in industry formats, port gate cut-off dates and times, and as an upgrade actual arrival and departure timestamps derived from vessel position data for scheduled-versus-actual comparison. A daily change notice stream reports port and vessel schedule changes.

Open buyer room →

Sample

Brickroad customers

Sample this dataset before you buy it.

Your sourcing agent asks Linescape 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: MarineApplication Software
Instruments: equitiescommoditiesderivatives

Dataset card

Type: not stated
Format: Comma-separated bulk files pulled from the vendor's file server or pushed to the customer's secure file server, designed for direct load into a transport-management or internal system; a programmatic interface tier and tailor-made feed layouts, including formats aligned to a specific carrier or electronic data interchange publication, are also offered.
Volume: Large and daily: with one record per port call, a global liner network of roughly 5,000-7,000 active sailings each making 8-12 port calls yields on the order of 50,000-80,000 port-call records per snapshot, reissued as carriers batch-update — so multi-million row deliveries per month plus a daily change stream and the vessel register.
Users: N/A — enterprise data-feed subscriptions integrated into client systems rather than a registered-user application; customers consume files programmatically, so seat counts are not the relevant metric (the firm is recorded at about ten staff with an implied revenue band).
History: not stated
Update frequency: not stated
Growth: Mature — an established feed catalogue (operational schedules, origin-destination schedules, vessel register, change notices) with a priced enhancement ladder and an implied revenue band at about ten staff; the product surface is stable rather than expanding, with no funding history or recent launch signals.
Launched: Est. 2008-2012 (the provider organisation record dates to 2014 and the firm presents as an established long-running schedule-data specialist with a mature catalogue and an implied revenue band; no launch date is printed).
Delivery: not stated
Entity mapping: not stated
Sample: not stated
Point-in-time: not stated
Licence: not stated

supplier index read from their site