Skip to content

Home/Sectors/Ports & terminals

AIS data for ports and terminals, measured where your traffic actually is.

Live movement across the approaches, the roadstead and the berth pockets, with the port call record that substantiates it. AIS data for ports and terminals collected on our own network, delivered as raw NMEA or over an API, provenance intact on every message.

100,000+

Vessels tracked / day

49M+

AIS positions / day

40+

Countries covered

<5s

Antenna to your API

A berth plan is only as good as the arrival data underneath it.

Berth allocation is still planned against declared times rather than measured ones, and the arrival moves by hours.

  • Congestion is disputed without a common measurementAn agent submits an estimate, pilotage, towage and mooring are committed against it, and the arrival moves by hours. Without independent measurement of anchorage waiting time and berth occupancy, the port holds one figure, the line another, and neither can be corroborated.

  • Coverage thins where traffic concentratesVHF is line of sight, roughly 20 to 40 nautical miles, and dense traffic causes message collision. The approaches, the roadstead, the pilot boarding place and the berth pocket are therefore where a global ocean picture degrades most.

  • Every position carries a trust scoreGNSS jamming and AIS spoofing introduce false positions and phantom port calls into the operating picture. We operate our own physical infrastructure, terrestrial and ship-borne, with satellite feeds for open ocean, and every position is nanosecond time-stamped and scored for trust by our anomaly detection models.

Submit your port area.Send the polygon covering your approaches and anchorage, and we will show you what our network collects inside it, trust scores attached.

See live data for your port

From live traffic in the approaches to port call times measured rather than declared.

  • Measured arrival and departure times, not declared ones

    Derive ETA, ATA and ATD from observed vessel behaviour rather than a declared estimate, and commit pilotage, towage and mooring gangs against the vessel's actual movement. The same records provide a defensible basis for just-in-time arrival arrangements with the lines calling at your berths.

  • A feed that ingests directly into VTS, PMIS and the port community system

    Take raw NMEA and AIVDM over TCP, a REST API or a WebSocket stream, with SAPIENT compliant output to the BSI Flex 335 interface where the port runs sensor fusion or counter-UAS alongside its traffic picture. Licence terms can cover redistribution within your port community, so terminals, agents and the pilot service do not each procure the same positions separately.

  • Anchorage waiting time and berth occupancy as evidence

    Measure time in the roadstead, time alongside and turnaround from the underlying position record rather than negotiating it with lines and terminals. Berth productivity and port emissions inventory figures then reconcile to raw messages, which carries weight the first time a board, a customer or a regulator challenges one.

  • Traffic measurement for capacity, channel and conservancy work

    Movement at port approach granularity feeds capacity and anchorage modelling, channel and dredging design, environmental impact submissions, and the reconstruction of an incident or near miss. You work from the underlying messages rather than a summary of them.

  • Screen the caller before the berth is committed

    The port is the primary inspection point and carries the exposure. Review the AIS gaps, dark activity, flag changes, MMSI reuse, IMO mismatches and ship-to-ship transfers behind a vessel before it takes a berth, on positions you can audit rather than a dashboard image you cannot.

  • An independent second source alongside what you already run

    Commercial AIS supply has consolidated into fewer owners, which presents a continuity and procurement risk for a port renewing a feed contract. We are independent and operate our own network, so we can run alongside your existing source for business continuity rather than replace it.

How the data is produced,
and how you can check it.

Every station runs the same dedicated, standardised hardware, encrypting each message at the point of capture.

Monitor

Cover the approaches and the roadstead

Track 100,000+ vessels a day across 40+ countries, so traffic accumulating outside the port is measured continuously rather than reconstructed once the congestion has arrived.

Verify

Know which receiver collected it

Every position is nanosecond time-stamped and scored for trust by our anomaly detection models, so a manipulated or interference-corrupted position is flagged rather than written into the port call record unchallenged.

Act

Into VTS, the PCS or the berth plan

Ingest it as raw NMEA over TCP, a REST API or a WebSocket stream, in under five seconds from antenna to your API, and retain the underlying records behind every figure you publish.

AIS data for ports and terminals: what harbour masters and port IT ask.

How much does AIS data cost for a port authority?

It depends on what the port requires, and any figure quoted before that is established is guesswork. The variables are the area covered, message volume, the delivery method, and the licence, particularly whether the feed can be redistributed within your port community. Tell us the port area, the systems it must feed and who needs access, and we will price against that rather than against a tier.

Can we redistribute the feed to terminals, agents and the pilot service?

That is a licensing question and we treat it as one rather than as an exception. A port normally needs the same movements within a port community system, a terminal operating system and on the pilot side, and a licence that prohibits this obliges one port community to procure the same positions repeatedly. Tell us who requires access and the redistribution scope is written into the agreement.

Is terrestrial AIS better than satellite AIS for port approaches?

For a port the geometry usually favours it. VHF is line of sight, so reception in the approaches, the roadstead and the berth pockets depends largely on receiver proximity, and dense port traffic causes message collision that worsens with distance from the receiver. Global ocean coverage addresses a different requirement from the one a harbour master faces in the approaches.

How do you detect false port calls caused by GNSS jamming?

By scoring each position rather than accepting it, and by comparing what independent receivers collected for the same area and window. Every message is nanosecond time-stamped and given a trust score by our anomaly detection models, so a position that jumps hundreds of kilometres or arrives without corroboration is flagged rather than merged into a clean track and recorded as an arrival.

Do you cover our port, and how do we check?

Send us the polygon covering your approaches and anchorage and we will answer precisely, including where we are thin. We supply only what our own network collected, and a global coverage figure says almost nothing about one specific body of water. Ask for the raw result for your own approaches rather than a coverage map, and judge us on that.

Can we host an AIS receiver at our port?

Yes, and we treat it as a commercial arrangement rather than a favour. Ports hold some of the most valuable terrestrial AIS positions available, and the customary arrangement returns a viewer in exchange. Host or connect a receiver with us and it runs the same standardised hardware as every other station, encrypting each message at capture, on agreed commercial terms and with access to the feed for your own use.

Start with your own approaches.

Send us the port area, and we will show you what our network collects there, the origin of each message, and where our coverage is thin.

See live data for your port