Vikkilen

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-11-04T12:32:04Z.

Havn

havn_id:
2328016
navn:
Vikkilen
kode:
NOVKK
type:
Havn
kommune:
Grimstad
fylke:
Agder
lat:
58.36055
lon:
8.61212

Port-call and departure connections

33 results

  1. oid:
    2328023
    origin:
    Dusavik
    did:
    2328016
    destination:
    Vikkilen
  2. oid:
    2328016
    origin:
    Vikkilen
    did:
    2447768
    destination:
    Forsand
  3. oid:
    2327911
    origin:
    Halden
    did:
    2328016
    destination:
    Vikkilen
  4. oid:
    2328016
    origin:
    Vikkilen
    did:
    2328038
    destination:
    Randaberg
  5. oid:
    2327922
    origin:
    Moss
    did:
    2328016
    destination:
    Vikkilen
  6. oid:
    2328016
    origin:
    Vikkilen
    did:
    2327922
    destination:
    Moss
  7. oid:
    2328016
    origin:
    Vikkilen
    did:
    2447768
    destination:
    Forsand
  8. oid:
    2447768
    origin:
    Forsand
    did:
    2328016
    destination:
    Vikkilen
  9. oid:
    2328016
    origin:
    Vikkilen
    did:
    2328048
    destination:
    Stavanger
  10. oid:
    2328016
    origin:
    Vikkilen
    did:
    2447768
    destination:
    Forsand
  11. oid:
    2327957
    origin:
    Rønningen
    did:
    2328016
    destination:
    Vikkilen
  12. oid:
    2328016
    origin:
    Vikkilen
    did:
    2328028
    destination:
    Haugesund
  13. oid:
    2327988
    origin:
    Egersund
    did:
    2328016
    destination:
    Vikkilen
  14. oid:
    2328016
    origin:
    Vikkilen
    did:
    2451550
    destination:
    Stord base
  15. oid:
    2329253
    origin:
    Aberdeen
    did:
    2328016
    destination:
    Vikkilen
  16. oid:
    2328016
    origin:
    Vikkilen
    did:
    2329094
    destination:
    Odense
  17. oid:
    2329094
    origin:
    Odense
    did:
    2328016
    destination:
    Vikkilen
  18. oid:
    2328016
    origin:
    Vikkilen
    did:
    2329094
    destination:
    Odense
  19. oid:
    2329118
    origin:
    Søby Havn
    did:
    2328016
    destination:
    Vikkilen
  20. oid:
    2328016
    origin:
    Vikkilen
    did:
    2329094
    destination:
    Odense
  21. oid:
    2327940
    origin:
    Langøya
    did:
    2328016
    destination:
    Vikkilen
  22. oid:
    2328016
    origin:
    Vikkilen
    did:
    2330477
    destination:
    Rotterdam
  23. oid:
    2328866
    origin:
    Mukran
    did:
    2328016
    destination:
    Vikkilen
  24. oid:
    2328016
    origin:
    Vikkilen
    did:
    2330499
    destination:
    Rouen
  25. oid:
    2330193
    origin:
    Härnösand
    did:
    2328016
    destination:
    Vikkilen
  26. oid:
    2328016
    origin:
    Vikkilen
    did:
    2329030
    destination:
    Fredericia
  27. oid:
    2328048
    origin:
    Stavanger
    did:
    2328016
    destination:
    Vikkilen
  28. oid:
    2328016
    origin:
    Vikkilen
    did:
    2329094
    destination:
    Odense
  29. oid:
    2327989
    origin:
    Eydehavn - Arendal
    did:
    2328016
    destination:
    Vikkilen
  30. oid:
    2328016
    origin:
    Vikkilen
    did:
    2329094
    destination:
    Odense
  31. oid:
    2327923
    origin:
    Oslo
    did:
    2328016
    destination:
    Vikkilen
  32. oid:
    2328016
    origin:
    Vikkilen
    did:
    2457813
    destination:
    Kristiansand ankring
  33. oid:
    2456632
    origin:
    Lyngør
    did:
    2328016
    destination:
    Vikkilen

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.