- Type
- not stated
- Format
- Tabular — JSON over a documented REST API (public Swagger spec, GET /api/External/Ships), plus structured data feeds and platform/PCS integrations; hosted web application on top of the same store
- Volume
- Master data on 170,000+ seagoing vessels; 200,000+ vessels tracked; structured port calls across 60+ ports; 500,000+ ISPS terminal/ship visits processed per year; continuous AIS-validated event stream per call (status, ETA/ETD, berth, previous/next port). Implies roughly 0.5-1M structured port-call records and several million port-call status events annually.
- Users
- No named-user disclosure; the deployable footprint is 60+ connected port ecosystems (PCS/PMS integrations) plus named anchor authorities (Port of Rotterdam, Port of Antwerp-Bruges, Zeehaven Ijmuiden). Bounded as tens of port-authority tenants plus their terminal/agent communities rather than an open signup base (self-serve trial exists but the product is sold per port/community).
- History
- 4 years
- Update frequency
- not stated
- Growth
- Active and expanding — announced expansion from Europe into North America (US/Canada port partnerships targeted at TPM26, Long Beach Mar 1-4), active event calendar into 2026 (Multimodaal Breda Mar 12, Breakbulk Europe, Posidonia Athens Jun 1-5, Europort Rotterdam), product releases ('New in Ship2Port: complete ship records', migration from Ship2Report to Ship2Port), and hiring signals on its company feed
- Launched
- Ship2Port platform ~2022-2024 (the site documents a migration from the predecessor product 'Ship2Report' to Ship2Port, so the platform is a re-brand/successor rather than a launch from zero); the operating house Royal Dirkzwager dates to 1872 ('175 years' of port-operations heritage)
- Delivery
- not stated
- Entity mapping
- not stated
- Sample
- not stated
- Point-in-time
- not stated
- Licence
- not stated