Vessels

Know which ships are coming to port, and when.

The ships bound for a port with our ETA and the crew’s beside it, the calls they made, and where any ship is now. In the dashboard, through the API, or by webhook.

NLRTMRotterdamExpected arrivals
ShipOur ETAStatus
Nordic Harbour
Container ship · from Hamburg
Today 17:20
Waiting
Atlantic Crest
Tanker · from Antwerp
Tue 06:40
On the way
Ever Bright
Container ship · from Felixstowe
Wed 22:10
On the way
Baltic Meridian
General cargo · from Le Havre
Mon 09:15
Overdue
An example of what a port’s arrivals look likeHow we estimate →

What you get

Expected arrivals

The cargo ships and tankers bound for a port, how likely each is to call, and the range it should arrive in. Ships waiting off the port, and those overdue, are marked.

Read the docs →

Port calls

The ships in port and those that left lately: when each arrived and left, and the terminals and anchorages it stopped at.

  1. Sat 04:10Arrived · anchorage
  2. Sat 11:35Berthed · container terminal
  3. Sun 19:50Left
Read the docs →

Vessel records

Any ship by its IMO number or MMSI: where it was last heard, where it is bound and when, its particulars, and where recorded, its inspections, sanctions and emissions.

Read the docs →

Watchlist and webhooks

Watch the ports and ships you care about, and hear when a ship is expected, arrives or leaves.

port.arrival.expectedport.call.arrivedvessel.call.departedvessel.inspection.recorded
Read the docs →

How we estimate

Every estimate says what it rests on, so you can weigh it.

Where a ship is bound
From the destination its crew typed, matched to a port. Where that names no port but the one it just left, from where the ship, and ships like it, went from there before.
When it arrives
From the distance left to sail along the sea lanes, at the speed it is making, with the range ships arrived in around such an estimate. The crew’s ETA comes alongside, as they broadcast it.
How likely it is
How often ships like it called where we said, that far ahead. Inland barges stop along the way more often than seagoing ships, and their odds say so.
How far to trust a port
Each port comes with how many calls we heard there lately, and once enough ships have arrived, how often we named it a day ahead and how far the estimate a day out fell.

Where we hear ships

Ships broadcast where they are, and receivers along the coasts pick them up. We hear busy coasts and ports best; far out at sea, and in some regions, we hear ships less often or not yet at all.

A ship that goes unheard keeps the position it was last heard at, and one not heard since it was due stays expected, marked overdue, as it may have reached port where no one hears it.

For developers

The same API and keys as locations, and webhooks for what changes.

API reference →Webhooks →
# Ships expected at Rotterdam in the next three dayscurl -H "Authorization: Bearer $WAYKITE_KEY" "https://waykite.com/api/v1/ports/NLRTM/arrivals?within=72"
# Where a ship is nowcurl -H "Authorization: Bearer $WAYKITE_KEY" "https://waykite.com/api/v1/vessels/imo:9987196/position"
# Watch a port, to hear of ships expected there, arriving and leavingcurl -X POST -H "Authorization: Bearer $WAYKITE_KEY" -H "Content-Type: application/json" \  -d '{"port": "NLRTM"}' "https://waykite.com/api/v1/watchlist"

Webhook · port.call.arrived

{  "type": "port.call.arrived",  "timestamp": "2026-10-26T08:00:00Z",  "data": {    "port": "NLRTM",    "imo": 9300000,    "name": "NORTHERN STAR",    "ship_category": "cargo",    "arrived_at": "2026-10-26T08:00:00Z",    …  }}

Keep reading