Inverness

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-11-04T14:04:48Z.

Havn

havn_id:
2329456
navn:
Inverness
kode:
not reported by source
type:
Havn
kommune:
not reported by source
fylke:
not reported by source
lat:
57.4833333333333
lon:
-4.21666666666667

Port-call and departure connections

34 results

  1. oid:
    2329456
    origin:
    Inverness
    did:
    2328171
    destination:
    Follafoss
  2. oid:
    2328274
    origin:
    Mo i Rana
    did:
    2329456
    destination:
    Inverness
  3. oid:
    2329456
    origin:
    Inverness
    did:
    2328171
    destination:
    Follafoss
  4. oid:
    2328100
    origin:
    Måløy
    did:
    2329456
    destination:
    Inverness
  5. oid:
    2329456
    origin:
    Inverness
    did:
    2328171
    destination:
    Follafoss
  6. oid:
    2329456
    origin:
    Inverness
    did:
    2328171
    destination:
    Follafoss
  7. oid:
    2328112
    origin:
    Svelgen
    did:
    2329456
    destination:
    Inverness
  8. oid:
    2329456
    origin:
    Inverness
    did:
    2327995
    destination:
    Kristiansand
  9. oid:
    2329456
    origin:
    Inverness
    did:
    2327923
    destination:
    Oslo
  10. oid:
    2329456
    origin:
    Inverness
    did:
    2328171
    destination:
    Follafoss
  11. oid:
    2447404
    origin:
    Storesund
    did:
    2329456
    destination:
    Inverness
  12. oid:
    2329456
    origin:
    Inverness
    did:
    2327995
    destination:
    Kristiansand
  13. oid:
    2329456
    origin:
    Inverness
    did:
    2328012
    destination:
    Rekefjord
  14. oid:
    2329456
    origin:
    Inverness
    did:
    2327995
    destination:
    Kristiansand
  15. oid:
    2329456
    origin:
    Inverness
    did:
    2327995
    destination:
    Kristiansand
  16. oid:
    2329456
    origin:
    Inverness
    did:
    2327995
    destination:
    Kristiansand
  17. oid:
    2329456
    origin:
    Inverness
    did:
    2327995
    destination:
    Kristiansand
  18. oid:
    2328232
    origin:
    Ålesund
    did:
    2329456
    destination:
    Inverness
  19. oid:
    2329456
    origin:
    Inverness
    did:
    2328171
    destination:
    Follafoss
  20. oid:
    2328078
    origin:
    Bergen
    did:
    2329456
    destination:
    Inverness
  21. oid:
    2329456
    origin:
    Inverness
    did:
    2327995
    destination:
    Kristiansand
  22. oid:
    2329456
    origin:
    Inverness
    did:
    2327995
    destination:
    Kristiansand
  23. oid:
    2329456
    origin:
    Inverness
    did:
    2447392
    destination:
    Knarrevik
  24. oid:
    2329456
    origin:
    Inverness
    did:
    2327995
    destination:
    Kristiansand
  25. oid:
    2329456
    origin:
    Inverness
    did:
    2328048
    destination:
    Stavanger
  26. oid:
    2329456
    origin:
    Inverness
    did:
    2328048
    destination:
    Stavanger
  27. oid:
    2328048
    origin:
    Stavanger
    did:
    2329456
    destination:
    Inverness
  28. oid:
    2328078
    origin:
    Bergen
    did:
    2329456
    destination:
    Inverness
  29. oid:
    2329456
    origin:
    Inverness
    did:
    2452204
    destination:
    Ukjent lokasjon Norge
  30. oid:
    2329456
    origin:
    Inverness
    did:
    2455773
    destination:
    Byfjorden - Kristiansand
  31. oid:
    2329456
    origin:
    Inverness
    did:
    2328048
    destination:
    Stavanger
  32. oid:
    2328048
    origin:
    Stavanger
    did:
    2329456
    destination:
    Inverness
  33. oid:
    2328078
    origin:
    Bergen
    did:
    2329456
    destination:
    Inverness
  34. oid:
    2329456
    origin:
    Inverness
    did:
    2327995
    destination:
    Kristiansand

Continue exploring

How an AI agent should use this page

Ground rule: Navigate with HTML GET links to keep explanations and relationships. Use the page's JSON alternative only when concrete values must be extracted, compared or computed.

How to use the port page

Use the port ID and code for identification. Port-call connections describe reported relations in the selected period, not necessarily a current timetable.

Open the port as a place for weather, vessels, charging and geographic context. Use Entur separately if the question concerns onward public transport from the port.