Lindø Havn

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T05:07:21Z.

Havn

havn_id:
2329069
navn:
Lindø Havn
kode:
not reported by source
type:
Havn
kommune:
not reported by source
fylke:
not reported by source
lat:
55.4672192
lon:
10.5382926

Port-call and departure connections

55 results

  1. oid:
    2329069
    origin:
    Lindø Havn
    did:
    2327904
    destination:
    Drammen
  2. oid:
    2329069
    origin:
    Lindø Havn
    did:
    2327998
    destination:
    Mandal
  3. oid:
    2329069
    origin:
    Lindø Havn
    did:
    2328129
    destination:
    Ågotnes
  4. oid:
    2329069
    origin:
    Lindø Havn
    did:
    2328018
    destination:
    Hausvikstrand
  5. oid:
    2329069
    origin:
    Lindø Havn
    did:
    2327988
    destination:
    Egersund
  6. oid:
    2329069
    origin:
    Lindø Havn
    did:
    2327988
    destination:
    Egersund
  7. oid:
    2329069
    origin:
    Lindø Havn
    did:
    2327927
    destination:
    Slagentangen
  8. oid:
    2329069
    origin:
    Lindø Havn
    did:
    2327927
    destination:
    Slagentangen
  9. oid:
    2329069
    origin:
    Lindø Havn
    did:
    2327955
    destination:
    Herøya
  10. oid:
    2329069
    origin:
    Lindø Havn
    did:
    2327995
    destination:
    Kristiansand
  11. oid:
    2329069
    origin:
    Lindø Havn
    did:
    2327995
    destination:
    Kristiansand
  12. oid:
    2329069
    origin:
    Lindø Havn
    did:
    2327989
    destination:
    Eydehavn - Arendal
  13. oid:
    2329069
    origin:
    Lindø Havn
    did:
    2447669
    destination:
    Boknafjorden
  14. oid:
    2329069
    origin:
    Lindø Havn
    did:
    2328120
    destination:
    Sture
  15. oid:
    2329069
    origin:
    Lindø Havn
    did:
    2327926
    destination:
    Sarpsborg
  16. oid:
    2329069
    origin:
    Lindø Havn
    did:
    2327948
    destination:
    Larvik
  17. oid:
    2327923
    origin:
    Oslo
    did:
    2329069
    destination:
    Lindø Havn
  18. oid:
    2450257
    origin:
    Rypefjord
    did:
    2329069
    destination:
    Lindø Havn
  19. oid:
    2447416
    origin:
    Hanøytangen
    did:
    2329069
    destination:
    Lindø Havn
  20. oid:
    2447416
    origin:
    Hanøytangen
    did:
    2329069
    destination:
    Lindø Havn
  21. oid:
    2447385
    origin:
    Skogsvåg
    did:
    2329069
    destination:
    Lindø Havn
  22. oid:
    2457009
    origin:
    Hordvik
    did:
    2329069
    destination:
    Lindø Havn
  23. oid:
    2327908
    origin:
    Fredrikstad
    did:
    2329069
    destination:
    Lindø Havn
  24. oid:
    2327908
    origin:
    Fredrikstad
    did:
    2329069
    destination:
    Lindø Havn
  25. oid:
    2327908
    origin:
    Fredrikstad
    did:
    2329069
    destination:
    Lindø Havn
  26. oid:
    2327908
    origin:
    Fredrikstad
    did:
    2329069
    destination:
    Lindø Havn
  27. oid:
    2327908
    origin:
    Fredrikstad
    did:
    2329069
    destination:
    Lindø Havn
  28. oid:
    2327908
    origin:
    Fredrikstad
    did:
    2329069
    destination:
    Lindø Havn
  29. oid:
    2327908
    origin:
    Fredrikstad
    did:
    2329069
    destination:
    Lindø Havn
  30. oid:
    2327908
    origin:
    Fredrikstad
    did:
    2329069
    destination:
    Lindø Havn
  31. oid:
    2327908
    origin:
    Fredrikstad
    did:
    2329069
    destination:
    Lindø Havn
  32. oid:
    2327908
    origin:
    Fredrikstad
    did:
    2329069
    destination:
    Lindø Havn
  33. oid:
    2327988
    origin:
    Egersund
    did:
    2329069
    destination:
    Lindø Havn
  34. oid:
    2327988
    origin:
    Egersund
    did:
    2329069
    destination:
    Lindø Havn
  35. oid:
    2327998
    origin:
    Mandal
    did:
    2329069
    destination:
    Lindø Havn
  36. oid:
    2328056
    origin:
    Jelsa
    did:
    2329069
    destination:
    Lindø Havn
  37. oid:
    2327911
    origin:
    Halden
    did:
    2329069
    destination:
    Lindø Havn
  38. oid:
    2327904
    origin:
    Drammen
    did:
    2329069
    destination:
    Lindø Havn
  39. oid:
    2327904
    origin:
    Drammen
    did:
    2329069
    destination:
    Lindø Havn
  40. oid:
    2327904
    origin:
    Drammen
    did:
    2329069
    destination:
    Lindø Havn
  41. oid:
    2327904
    origin:
    Drammen
    did:
    2329069
    destination:
    Lindø Havn
  42. oid:
    2327904
    origin:
    Drammen
    did:
    2329069
    destination:
    Lindø Havn
  43. oid:
    2327904
    origin:
    Drammen
    did:
    2329069
    destination:
    Lindø Havn
  44. oid:
    2327904
    origin:
    Drammen
    did:
    2329069
    destination:
    Lindø Havn
  45. oid:
    2327904
    origin:
    Drammen
    did:
    2329069
    destination:
    Lindø Havn
  46. oid:
    2327904
    origin:
    Drammen
    did:
    2329069
    destination:
    Lindø Havn
  47. oid:
    2327904
    origin:
    Drammen
    did:
    2329069
    destination:
    Lindø Havn
  48. oid:
    2327904
    origin:
    Drammen
    did:
    2329069
    destination:
    Lindø Havn
  49. oid:
    2327904
    origin:
    Drammen
    did:
    2329069
    destination:
    Lindø Havn
  50. oid:
    2329069
    origin:
    Lindø Havn
    did:
    2450257
    destination:
    Rypefjord
  51. oid:
    2329069
    origin:
    Lindø Havn
    did:
    2328064
    destination:
    Ølen
  52. oid:
    2329069
    origin:
    Lindø Havn
    did:
    2327923
    destination:
    Oslo
  53. oid:
    2329069
    origin:
    Lindø Havn
    did:
    2327923
    destination:
    Oslo
  54. oid:
    2329069
    origin:
    Lindø Havn
    did:
    2328063
    destination:
    Husøy - Karmøy
  55. oid:
    2329069
    origin:
    Lindø Havn
    did:
    2466738
    destination:
    Oslo Hjortneskaien

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.