Skip to content

← All sections

Nearest vessels reporting AIS positions

Latest AIS position per vessel within roughly 10 km of the address from the last six hours, with ship name, type, speed, course and destination. A snapshot of shipping activity, not a traffic statistic.

vessel_traffic8 fields8 of these fields open in the demo
Source
BarentsWatch / Kystverket AIS snapshot
Geography
Around the address
Reported stale after
2 hours
Access
Requires an API key granted this section
Contract version
1
In packages
environment_nuisance, traffic_and_sensors

Read about this data source →

Status right now

State
Within budget
Combined section status is within the age and schedule budget. Check the separate data timestamp for data freshness.
Last loaded
22 Nov 2026
Data freshness evidence
Within budget
Newest stored data record 22 Nov 2026
Newest record
22 Nov 2026
Municipalities with data
10

Measured 22 Nov 2026. This is about the section as a whole, not one address: an address outside coverage still gets “not covered”, never “no”.

Available with: trial key (open fields) · bundle or agreed plan, subject to field policy and source grants · Pricing

Source terms and reuse

These are declarations from the catalogue contract, not a new rights approval. Customer access, source agreements and privacy need separate assessment. A licence label does not establish coverage or reviewed content.

Declared licence or terms
unverified
Declared redistribution
Not established
Catalogue basis
Unverified

API warnings

The API returns these notes in warnings.

  • Latest known position per vessel within 11 km of the address point, from the last six hours; a snapshot of shipping activity, not a traffic statistic. Vessel identifiers are public AIS data.

Provider-contract fields

2 of 8 fields are value fields — the ones that decide whether a record actually says anything. The rest are context: identifiers, codes and timestamps. Fields marked “open” also occur in the demo projection, which may have different field definitions. Other fields require the appropriate field policy and source access, not just a key.

FieldTypeRoleDemo
mmsistring | nullcontextopen
ship_namestring | nullvalueopen
ship_typeinteger | nullcontextopen
speednumber | nullcontextopen
coursenumber | nullcontextopen
destinationstring | nullcontextopen
straight_line_distance_minteger | null (m)valueopen
updated_atstring | nullcontextopen

Fetch this section

Send the key in the X-API-Key header. The section can be fetched with the rest of the address, or on its own with pagination.

curl --disable --fail-with-body --silent --show-error --connect-timeout 10 --max-time 30 \
  -H "X-API-Key: ${APPROACH_API_KEY:?APPROACH_API_KEY is not set}" \
  'https://api.approach.no/api/v1/addresses/285717643?include=vessel_traffic'

# paginated, one section at a time
curl --disable --fail-with-body --silent --show-error --connect-timeout 10 --max-time 30 \
  -H "X-API-Key: ${APPROACH_API_KEY:?APPROACH_API_KEY is not set}" \
  'https://api.approach.no/api/v1/addresses/285717643/sections/vessel_traffic?limit=25'

Try it now

This is a real call against the public demo, from here. What appears below is what the API returned — not a sample.