Brickroad
Brickroad
IndexSignalsBlog
/Index//

Product

  • Information Frontier Agent
  • Vendor Management Agent
  • Product tour
  • Pricing

Solutions

  • Utility estimation
  • Context assembly
  • Market intelligence

Suppliers

  • Sell your data
  • Start onboarding
  • Programmatic Data License

Community

  • Public index
  • Signals
  • Blog

Company

  • About
  • Team
  • Careers
  • Brand

Connect

  • LinkedIn
  • X
PrivacyTermsCookies

© 2026 Brickroad

/Index/Cargoshipday/Cargoshipday
C

Cargoshipday

CARGOSHIPDAYManage supplier listing

Terminal-level vessel berthing and departure schedule dataset for Korean container ports, harvested continuously from ~19 individual terminal operators and — critically — versioned: every change to ETB, ETD or berth is captured with its previous value and a field-level change timestamp, producing an audit trail of schedule revisions rather than a single snapshot. Also includes container gate-in/gate-out (반출입) cut-off status by terminal, a COPINO booking-reference lookup, terminal/code reference tables and a freight-rate page. Secondary byproduct: user watchlists and feature-request intake.

Open buyer room →
Cargoshipday/Cargoshipday
SampleCoverage

Sample

Brickroad customers

Sample this dataset before you buy it.

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

Start 7-day trial→Nothing is charged until the trial ends.

Coverage

Universe, instruments and categories.

Industry
Marine Transportation
Instruments
equitiescommodities
Categories
Alternative
Supply Chain
Geospatial
Reference
Regions
USAPAC
Sample tickers
005300.KS011200.KS009180.KS010130.KS006490.KS
Dataset card
Type
not stated
Format
Tabular schedule records (vessel, voyage, terminal, berth, ETB/ETD, status) with field-level revision history, downloadable via one-click Excel export with custom templates; served from web/API collection pipelines with a system-monitoring status view
Volume
Est. 200-400 vessel calls per week across 19 covered terminals (10 Busan, 2 Gwangyang, 4 Incheon, 2 Pyeongtaek, 2 Ulsan), each call carrying ETB/ETD/berth fields plus multiple revisions — so roughly 10^5 schedule records and a comparable or larger volume of field-level change events per month
Users
Small early-stage user base — est. hundreds to low thousands of Korean logistics/shipping users (social-login signup via Kakao, Google, Naver launched with the service in March 2026; free schedule search, no published user count)
History
3 years
Update frequency
not stated
Growth
Active and very early-stage — terms of service and privacy policy both dated/effective 16-17 March 2026, an open feature-request channel ('Build with Shipday') with Add Terminal requests, active system-collection monitoring, and a companion enterprise automation/AI consulting arm
Launched
2026 (Terms of Service announcement and effective date both 17 March 2026; Privacy Policy 16 March 2026 — the earliest dated artefact on the site)
Delivery
not stated
Entity mapping
not stated
Sample
not stated
Point-in-time
not stated
Licence
not stated

supplier index read from their site

Cargoshipday has not added their own details yet. Not yet on file:

  • Dataset
  • Data dictionary
  • Coverage
  • Provenance
  • Rights & data handling