Brickroad
Brickroad
IndexSignalsBlog
/Index//

Product

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

Solutions

  • All Solutions
  • Atlas
  • Wayfinder
  • Horizon

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/Portflow/Predictive tanker port-congestion and ETA dataset built on public AIS
P

Predictive tanker port-congestion and ETA dataset built on public AIS

PORTFLOWManage supplier listing

Predictive tanker port-congestion and ETA dataset built on public AIS. Concretely: per-voyage predicted ETAs continuously refreshed for every trackable vessel (tanker, container, bulk, general, RoRo) approaching or anchoring at any of 51 digitised ports (including ARA, Hamburg, Algeciras, Fujairah, Singapore, Houston, Sabine Pass, Ras Laffan), scored against the crew-broadcast ETA with an open, published RMSE/MAE benchmark computed over exactly the same closed voyages for both series — the operator states the broadcast baseline excludes sentinel placeholder ETAs beyond 7 days so the comparison is honest. Derived layers: live congestion indices and waiting times per port; transit counts, dwell time and deviation at 12-13 chokepoints (Hormuz, Suez, Bosphorus, Malacca); a per-voyage lifecycle state machine (open, arrival-moored, departure) derived from navigation status and motion; cargo-class assignment fusing AIS ship type with a name-and-destination text heuristic tuned per port; dwell-at-anchor anomaly flags with thresholds tuned by cargo class; delay attribution; multi-regime sanctions screening across four regimes in one pass with audit trail; and behavioural AIS-gap and dark-event detection in contested waters. Architecture matters for a buyer: source AIS is a community real-time stream plus vessel-broadcast static messages, with no proprietary feed integrated in v1 (commercial satellite AIS is roadmap, not integrated), so every asset here is derived — but the platform also stores rate-limited per-vessel position snapshots explicitly to enable backtesting and model replay, plus relational storage with timestamped lineage so any metric is reproducible at a given instant.

Open buyer room →
Portflow/Predictive tanker port-congestion and ETA dataset built on public AIS
SampleCoverage

Sample

Brickroad customers

Sample this dataset before you buy it.

Your sourcing agent asks Portflow 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
Oil & Gas Storage & Transportation
Instruments
commoditiesequitiesfreight_derivativesoptions
Categories
AlternativeSupply ChainPriceGeospatial
Regions
USUKOtherEurope
Sample tickers
FROSTNGTNKINSWDHTNATTRMDMPCVLOPSX
Dataset card
Type
not stated
Format
Deliberately agent-friendly: a JSON API and CSV export, plus alert delivery over webhook, Slack, Telegram and email; relational SQL backing store with timestamped lineage and rate-limited per-vessel position snapshots; a roadmap item for daily columnar export to object storage for clients' data scientists. Sold as a web application with a tiered subscription.
Volume
Compact, and the operator is explicit about how little history is kept. Live universe is 51 ports and 12-13 chokepoints, so per-closed-voyage records number in the low thousands per year. Published retention commitments cap the asset: 7 days of in-memory KPIs and SQLite storage with 90-day compaction, so recent detail is fine while older history is thinned. Position snapshots are written per vessel at a rate-limited cadence rather than full-resolution logging, and source AIS static messages arrive roughly every 6 minutes per vessel, so at best a partial position archive rather than a complete track history. Realistically megabytes to low gigabytes, with any deep-history claim explicitly unsupported.
Users
Not disclosed and almost certainly very small — a self-declared solo/MVP operation (no employees on record, based in Rethel, France) with a card-free self-serve funnel across a free tier and three paid tiers at 97, 149 and 374 euros per month, and a professional-network page with only a couple of followers. Estimate low-hundreds registrations site-wide and low-tens of paying seats; the no-signup, no-card demo session funnel implies acquisition is still manual and founder-led.
History
not stated
Update frequency
not stated

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

  • Dataset
  • Data dictionary
  • Coverage
  • Provenance
  • Rights & data handling
Growth
Active with an unusually concrete roadmap. The operator publishes dated build plans rather than marketing claims: a Mediterranean coastal software-defined-radio AIS receiver plus an AIS-exchange integration to unlock western Mediterranean coverage (about 150 euros of hardware, targeted Q3 2026), a bring-your-own-key commercial AIS activation already wired for Pro+ customers who hold their own provider contract, EU reported-emissions data on the enrichment list, and daily columnar export to object storage. The ETA-model roadmap names congestion, tides, weather and vessel-specific historical speed. The site is live at retrieval with real pricing tiers, so this is early build-out, honestly labelled v1 and MVP throughout.
Launched
~2026 — the company profile was created in 2026, the professional-network page's earliest posts are roughly four months old at retrieval, and the operator self-describes the platform as v1 and MVP with premium data sources still on the roadmap. Treat as launched within 2026.
Delivery
not stated
Entity mapping
not stated
Sample
not stated
Point-in-time
not stated
Licence
not stated

supplier index read from their site