# Finland Port Calls & Vessel ETA Tracker (Official Data) (`shelly_fen/finland-port-calls-vessel-eta`) Actor

Finnish port vessel ETA/ETD/ATA/ATD, berth, previous/next port and ship agent from official Fintraffic Digitraffic open data (CC BY 4.0). Filter by UN/LOCODE or IMO; changes-only mode for scheduled tracking.

- **URL**: https://apify.com/shelly_fen/finland-port-calls-vessel-eta.md
- **Developed by:** [shelly_fen](https://apify.com/shelly_fen) (community)
- **Categories:** Travel, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 port call rows

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Vessel ETA API for Finnish Ports – Port Calls, ETA/ETD, Berth (Official Fintraffic Data)

**Vessel ETA and port calls in Finland:** arrival and departure times (ETA, ETD, ATA, ATD), berth, previous/next port and ship agent for Helsinki, HaminaKotka, Hanko, Turku, Rauma, Oulu and all other Finnish ports – as one table, or only the changes since your last run.

| | |
|---|---|
| **Data source** | Fintraffic Digitraffic Port Call API (Finnish state-owned traffic agency) |
| **Licence** | CC BY 4.0 – attribution included in every row |
| **Update frequency** | Queried live on every run; Digitraffic updates as agents and ports report (typically within minutes) |
| **Coverage** | Finnish ports only |
| **Cost example** | Helsinki + Kotka, 50 rows = $0.005 + 50 × $0.002 = **$0.105 per run**. Hourly changes-only monitoring usually bills only a few rows. |

**What it can do:** port schedules, IMO watchlists, change alerts on a schedule.
**What it can't do:** live AIS positions or vessel tracking at sea, ports outside Finland, cargo/manifest details, guarantee ETAs (they are agents' estimates).

***

Stop refreshing port websites to see when your vessel arrives. This Actor returns every upcoming and current port call at Finnish ports - **ETA, ETD, actual arrival/departure, berth, port area, previous and next port, ship agent** - as one clean table, from official Fintraffic open data.

### What does it do?

- Fetches port calls for the Finnish ports you choose (or all Finnish ports) from the official Fintraffic Digitraffic Port Call API.
- Returns one row per port call and port area, with estimated and actual times (UTC) and a simple `status`: `expected`, `in port` or `departed`.
- Optional **IMO watchlist**: only your fleet or booked vessels.
- Optional **changes-only mode**: run it on a schedule and get only new port calls or changed ETA/ETD/ATA/ATD/berth since the last run - you pay only for those rows.

### Who is it for?

- **Freight forwarders and shippers' logistics teams** - know when a vessel with your cargo actually arrives and leaves.
- **Trucking and terminal dispatchers** - plan pick-ups around the latest ETA instead of the booking date.
- **Ship agents and brokers** - one table for many ports instead of checking each port site.
- **Analysts** - build a history of port calls and delays at Helsinki, HaminaKotka, Hanko, Turku, Rauma, Oulu and more.

### How to use it

1. Enter one or more **port UN/LOCODEs** (for example `FIHEL` Helsinki, `FIKTK` Kotka, `FIHKO` Hanko, `FITKU` Turku, `FIRAU` Rauma). Leave empty for all Finnish ports.
2. Optionally add **IMO numbers** to track only specific vessels.
3. For monitoring, turn on **Only new or changed ETA/ETD since last run** and add a [schedule](https://docs.apify.com/platform/schedules) (for example hourly). Use a different **state name** for each watchlist.
4. Run it and download the table as JSON, CSV or Excel, or connect it to Google Sheets, Slack, Zapier or Make through Apify integrations.

#### Input example

```json
{
  "ports": ["FIHEL", "FIKTK"],
  "imoNumbers": [],
  "changesOnly": false,
  "maxResults": 50
}
```

#### Input fields

| Field | Description |
|---|---|
| `ports` | UN/LOCODEs of Finnish ports. Empty = all Finnish ports. |
| `imoNumbers` | Optional list of IMO numbers. Only those vessels are returned. |
| `changesOnly` | If true, returns only new port calls or calls whose ETA/ETD/ATA/ATD/berth changed since the last run (state kept in a named key-value store). |
| `stateKey` | Name of that state, so separate watchlists don't mix. Default `fi-port-calls-state`. |
| `maxResults` | Safety cap on billable rows per run (default 500, max 5000). |

### Output

One row per port call and port area. Example (real row, shortened):

```json
{
  "portCallId": 3348188,
  "port": "FIHKO",
  "portArea": "LÄNSISATAMA",
  "berth": "Roro 3",
  "vesselName": "Finntide",
  "imo": 9468920,
  "mmsi": 230631000,
  "callSign": "OJPS",
  "flag": "FI",
  "vesselTypeCode": 40,
  "previousPort": "PLGDY",
  "nextPort": "PLGDY",
  "eta": "2026-10-11T09:00:00.000Z",
  "ata": "2026-10-11T09:15:00.000Z",
  "etd": "2026-10-11T15:00:00.000Z",
  "atd": "2026-10-11T14:45:00.000Z",
  "etaSource": "Agent",
  "etdSource": "Agent",
  "arrivalWithCargo": true,
  "domesticArrival": false,
  "agents": ["Finnlines Oyj"],
  "lastUpdated": "2026-10-11T14:58:33.000Z",
  "status": "departed",
  "attribution": "Source: Fintraffic / digitraffic.fi, license CC 4.0 BY (https://creativecommons.org/licenses/by/4.0/)"
}
```

#### Output fields

`portCallId, port, portArea, berth, vesselName, imo, mmsi, callSign, flag, vesselTypeCode, previousPort, nextPort, eta, ata, etd, atd, etaSource, etdSource, arrivalWithCargo, domesticArrival, agents, lastUpdated, status, attribution` (+ `change` = `new` / `updated` in changes-only mode). All times are UTC (ISO 8601).

### How much does it cost? (pay per event)

- $0.005 per run start
- $0.002 per port-call row returned (in changes-only mode, only new or changed rows are billed)

Examples: all Helsinki calls (~40 rows) ≈ $0.09. An hourly changes-only watch that returns 0 new rows costs only the $0.005 start per run (plus nothing per row). `maxResults` caps the rows you can be billed for in one run.

### FAQ

**How fresh is the data?** Each run reads the live Digitraffic Port Call API at run time. ETA/ETD are reported by ship agents and can change; `lastUpdated` shows when the port call was last updated at the source.

**Which ports are covered?** Finnish ports that report to the Finnish Port Community System via Digitraffic. Use UN/LOCODEs starting with `FI`.

**Why do I see the same port call twice?** A call can visit several port areas (for example two terminals). Each port area is a separate row with its own berth and times.

**Does it include personal data?** No. Ship master names and free-text fields are dropped. Agents are companies.

**Can I get only changes?** Yes - enable changes-only mode and schedule the Actor. The first run returns everything (all rows are "new"); later runs return only differences.

### Limitations

- Coverage and accuracy depend on what agents report to the official system; times can be missing or revised.
- Only Finnish ports. Not for navigation or safety-critical use.

### Data source and licence

Source: Fintraffic / digitraffic.fi, license CC 4.0 BY. Official open data from the Finnish traffic management company; this Actor is independent and not endorsed by Fintraffic. Every row carries the attribution text.

### More from this author

- [Italy Fuel Prices for Fleets & Logistics](https://apify.com/shelly_fen/eu-fuel-prices-official) — official MIMIT station prices for Italy (diesel, petrol, LPG, CNG, LNG).
- [England Property Planning Constraints Bulk Checker](https://apify.com/shelly_fen/england-planning-constraints-checker) — bulk planning-constraint flags for England properties (official open data).

### Further reading

- Source: [digitraffic.fi Port Call API](https://www.digitraffic.fi/en/marine-traffic/)
- [SEO for Actors (Apify Help)](https://help.apify.com/en/articles/2644024-seo-for-actors)

# Changelog

This Actor's version history is a separate document: https://apify.com/shelly_fen/finland-port-calls-vessel-eta/changelog.md

# Actor input Schema

## `ports` (type: `array`):

e.g. FIHEL (Helsinki), FIKTK (Kotka), FIHKO (Hanko), FITKU (Turku), FIRAU (Rauma). Leave empty for all Finnish ports.

## `imoNumbers` (type: `array`):

Optional. Track just your fleet or booked vessels.

## `changesOnly` (type: `boolean`):

Remembers the last run (named key-value store) and returns only new port calls or changed times/berths. Ideal for scheduled runs - you only pay for changes.

## `stateKey` (type: `string`):

Use different names for different watchlists.

## `maxResults` (type: `integer`):

Safety cap on billable rows per run.

## Actor input object example

```json
{
  "ports": [
    "FIHEL"
  ],
  "changesOnly": false,
  "stateKey": "fi-port-calls-state",
  "maxResults": 500
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

## `full` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "ports": [
        "FIHEL"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("shelly_fen/finland-port-calls-vessel-eta").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "ports": ["FIHEL"] }

# Run the Actor and wait for it to finish
run = client.actor("shelly_fen/finland-port-calls-vessel-eta").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "ports": [
    "FIHEL"
  ]
}' |
apify call shelly_fen/finland-port-calls-vessel-eta --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,shelly_fen/finland-port-calls-vessel-eta"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/PyO1VZbPgXHxI9P46/builds/g3B0I7G9MQPA05kgZ/openapi.json