Grundartangi

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T02:40:21Z.

Havn

havn_id:
2329817
navn:
Grundartangi
kode:
not reported by source
type:
Havn
kommune:
not reported by source
fylke:
not reported by source
lat:
64.3603796
lon:
-21.7758053

Port-call and departure connections

74 results

  1. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328125
    destination:
    Sløvåg Industriområde
  2. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328262
    destination:
    Glomfjord
  3. oid:
    2329817
    origin:
    Grundartangi
    did:
    2327949
    destination:
    Porsgrunn
  4. oid:
    2329817
    origin:
    Grundartangi
    did:
    2327949
    destination:
    Porsgrunn
  5. oid:
    2329817
    origin:
    Grundartangi
    did:
    2327949
    destination:
    Porsgrunn
  6. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328348
    destination:
    Leirpollen
  7. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328348
    destination:
    Leirpollen
  8. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328348
    destination:
    Leirpollen
  9. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328348
    destination:
    Leirpollen
  10. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328348
    destination:
    Leirpollen
  11. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328348
    destination:
    Leirpollen
  12. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328348
    destination:
    Leirpollen
  13. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328348
    destination:
    Leirpollen
  14. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328348
    destination:
    Leirpollen
  15. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328348
    destination:
    Leirpollen
  16. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328348
    destination:
    Leirpollen
  17. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328348
    destination:
    Leirpollen
  18. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328348
    destination:
    Leirpollen
  19. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328348
    destination:
    Leirpollen
  20. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328348
    destination:
    Leirpollen
  21. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328348
    destination:
    Leirpollen
  22. oid:
    2328231
    origin:
    Åheim
    did:
    2329817
    destination:
    Grundartangi
  23. oid:
    2341605
    origin:
    Søvik
    did:
    2329817
    destination:
    Grundartangi
  24. oid:
    2328339
    origin:
    Honningsvåg
    did:
    2329817
    destination:
    Grundartangi
  25. oid:
    2328339
    origin:
    Honningsvåg
    did:
    2329817
    destination:
    Grundartangi
  26. oid:
    2328207
    origin:
    Orkanger
    did:
    2329817
    destination:
    Grundartangi
  27. oid:
    2328207
    origin:
    Orkanger
    did:
    2329817
    destination:
    Grundartangi
  28. oid:
    2327995
    origin:
    Kristiansand
    did:
    2329817
    destination:
    Grundartangi
  29. oid:
    2456998
    origin:
    Ramfjordnes
    did:
    2329817
    destination:
    Grundartangi
  30. oid:
    2456998
    origin:
    Ramfjordnes
    did:
    2329817
    destination:
    Grundartangi
  31. oid:
    2328348
    origin:
    Leirpollen
    did:
    2329817
    destination:
    Grundartangi
  32. oid:
    2328348
    origin:
    Leirpollen
    did:
    2329817
    destination:
    Grundartangi
  33. oid:
    2328348
    origin:
    Leirpollen
    did:
    2329817
    destination:
    Grundartangi
  34. oid:
    2328348
    origin:
    Leirpollen
    did:
    2329817
    destination:
    Grundartangi
  35. oid:
    2328348
    origin:
    Leirpollen
    did:
    2329817
    destination:
    Grundartangi
  36. oid:
    2328348
    origin:
    Leirpollen
    did:
    2329817
    destination:
    Grundartangi
  37. oid:
    2328348
    origin:
    Leirpollen
    did:
    2329817
    destination:
    Grundartangi
  38. oid:
    2328348
    origin:
    Leirpollen
    did:
    2329817
    destination:
    Grundartangi
  39. oid:
    2328348
    origin:
    Leirpollen
    did:
    2329817
    destination:
    Grundartangi
  40. oid:
    2328348
    origin:
    Leirpollen
    did:
    2329817
    destination:
    Grundartangi
  41. oid:
    2328348
    origin:
    Leirpollen
    did:
    2329817
    destination:
    Grundartangi
  42. oid:
    2328348
    origin:
    Leirpollen
    did:
    2329817
    destination:
    Grundartangi
  43. oid:
    2328348
    origin:
    Leirpollen
    did:
    2329817
    destination:
    Grundartangi
  44. oid:
    2328348
    origin:
    Leirpollen
    did:
    2329817
    destination:
    Grundartangi
  45. oid:
    2328348
    origin:
    Leirpollen
    did:
    2329817
    destination:
    Grundartangi
  46. oid:
    2328348
    origin:
    Leirpollen
    did:
    2329817
    destination:
    Grundartangi
  47. oid:
    2328348
    origin:
    Leirpollen
    did:
    2329817
    destination:
    Grundartangi
  48. oid:
    2328348
    origin:
    Leirpollen
    did:
    2329817
    destination:
    Grundartangi
  49. oid:
    2328348
    origin:
    Leirpollen
    did:
    2329817
    destination:
    Grundartangi
  50. oid:
    2328348
    origin:
    Leirpollen
    did:
    2329817
    destination:
    Grundartangi
  51. oid:
    2328361
    origin:
    Tromsø
    did:
    2329817
    destination:
    Grundartangi
  52. oid:
    2328361
    origin:
    Tromsø
    did:
    2329817
    destination:
    Grundartangi
  53. oid:
    2328361
    origin:
    Tromsø
    did:
    2329817
    destination:
    Grundartangi
  54. oid:
    2328361
    origin:
    Tromsø
    did:
    2329817
    destination:
    Grundartangi
  55. oid:
    2328361
    origin:
    Tromsø
    did:
    2329817
    destination:
    Grundartangi
  56. oid:
    2328361
    origin:
    Tromsø
    did:
    2329817
    destination:
    Grundartangi
  57. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328207
    destination:
    Orkanger
  58. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328089
    destination:
    Gudvangen
  59. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328089
    destination:
    Gudvangen
  60. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328274
    destination:
    Mo i Rana
  61. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328274
    destination:
    Mo i Rana
  62. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328274
    destination:
    Mo i Rana
  63. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328274
    destination:
    Mo i Rana
  64. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328012
    destination:
    Rekefjord
  65. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328232
    destination:
    Ålesund
  66. oid:
    2329817
    origin:
    Grundartangi
    did:
    2327974
    destination:
    Frierfjorden ankring
  67. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328227
    destination:
    Verdal
  68. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328227
    destination:
    Verdal
  69. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328227
    destination:
    Verdal
  70. oid:
    2329817
    origin:
    Grundartangi
    did:
    2447352
    destination:
    Honningsvåg - Altsula ankring
  71. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328231
    destination:
    Åheim
  72. oid:
    2329817
    origin:
    Grundartangi
    did:
    2456966
    destination:
    Steinsvika - Volda
  73. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328358
    destination:
    Lillebukt
  74. oid:
    2329817
    origin:
    Grundartangi
    did:
    2328358
    destination:
    Lillebukt

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.