Ramsund

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-11-04T16:18:10Z.

Havn

havn_id:
2328281
navn:
Ramsund
kode:
NORAM
type:
Havn
kommune:
Tjeldsund
fylke:
Troms
lat:
68.4939
lon:
16.50809

Port-call and departure connections

58 results

  1. oid:
    2328281
    origin:
    Ramsund
    did:
    2328361
    destination:
    Tromsø
  2. oid:
    2328063
    origin:
    Husøy - Karmøy
    did:
    2328281
    destination:
    Ramsund
  3. oid:
    2328281
    origin:
    Ramsund
    did:
    2328256
    destination:
    Drag
  4. oid:
    2328260
    origin:
    Fjelldal
    did:
    2328281
    destination:
    Ramsund
  5. oid:
    2447641
    origin:
    Barentshavet
    did:
    2328281
    destination:
    Ramsund
  6. oid:
    2447641
    origin:
    Barentshavet
    did:
    2328281
    destination:
    Ramsund
  7. oid:
    2328281
    origin:
    Ramsund
    did:
    2447641
    destination:
    Barentshavet
  8. oid:
    2447641
    origin:
    Barentshavet
    did:
    2328281
    destination:
    Ramsund
  9. oid:
    2328281
    origin:
    Ramsund
    did:
    2447641
    destination:
    Barentshavet
  10. oid:
    2447641
    origin:
    Barentshavet
    did:
    2328281
    destination:
    Ramsund
  11. oid:
    2328281
    origin:
    Ramsund
    did:
    2447759
    destination:
    Fornes
  12. oid:
    2447759
    origin:
    Fornes
    did:
    2328281
    destination:
    Ramsund
  13. oid:
    2328281
    origin:
    Ramsund
    did:
    2447759
    destination:
    Fornes
  14. oid:
    2328262
    origin:
    Glomfjord
    did:
    2328281
    destination:
    Ramsund
  15. oid:
    2328281
    origin:
    Ramsund
    did:
    2328264
    destination:
    Harstad
  16. oid:
    2328264
    origin:
    Harstad
    did:
    2328281
    destination:
    Ramsund
  17. oid:
    2328281
    origin:
    Ramsund
    did:
    2328264
    destination:
    Harstad
  18. oid:
    2328264
    origin:
    Harstad
    did:
    2328281
    destination:
    Ramsund
  19. oid:
    2328281
    origin:
    Ramsund
    did:
    2328264
    destination:
    Harstad
  20. oid:
    2328251
    origin:
    Bodø
    did:
    2328281
    destination:
    Ramsund
  21. oid:
    2328281
    origin:
    Ramsund
    did:
    2328078
    destination:
    Bergen
  22. oid:
    2451567
    origin:
    Stokksund
    did:
    2328281
    destination:
    Ramsund
  23. oid:
    2328281
    origin:
    Ramsund
    did:
    2328361
    destination:
    Tromsø
  24. oid:
    2328251
    origin:
    Bodø
    did:
    2328281
    destination:
    Ramsund
  25. oid:
    2328281
    origin:
    Ramsund
    did:
    2328078
    destination:
    Bergen
  26. oid:
    2328291
    origin:
    Stokmarknes
    did:
    2328281
    destination:
    Ramsund
  27. oid:
    2328281
    origin:
    Ramsund
    did:
    2447759
    destination:
    Fornes
  28. oid:
    2447759
    origin:
    Fornes
    did:
    2328281
    destination:
    Ramsund
  29. oid:
    2328281
    origin:
    Ramsund
    did:
    2447759
    destination:
    Fornes
  30. oid:
    2328262
    origin:
    Glomfjord
    did:
    2328281
    destination:
    Ramsund
  31. oid:
    2328281
    origin:
    Ramsund
    did:
    2328264
    destination:
    Harstad
  32. oid:
    2451419
    origin:
    Laksevåg
    did:
    2328281
    destination:
    Ramsund
  33. oid:
    2330169
    origin:
    Göteborg
    did:
    2328281
    destination:
    Ramsund
  34. oid:
    2328281
    origin:
    Ramsund
    did:
    2328092
    destination:
    Haakonsvern
  35. oid:
    2328092
    origin:
    Haakonsvern
    did:
    2328281
    destination:
    Ramsund
  36. oid:
    2328281
    origin:
    Ramsund
    did:
    2462622
    destination:
    Jan Mayen
  37. oid:
    2328281
    origin:
    Ramsund
    did:
    2462622
    destination:
    Jan Mayen
  38. oid:
    2328281
    origin:
    Ramsund
    did:
    2462622
    destination:
    Jan Mayen
  39. oid:
    2328281
    origin:
    Ramsund
    did:
    2328296
    destination:
    Tovik
  40. oid:
    2328251
    origin:
    Bodø
    did:
    2328281
    destination:
    Ramsund
  41. oid:
    2328281
    origin:
    Ramsund
    did:
    2328291
    destination:
    Stokmarknes
  42. oid:
    2328279
    origin:
    Narvik
    did:
    2328281
    destination:
    Ramsund
  43. oid:
    2328281
    origin:
    Ramsund
    did:
    2456998
    destination:
    Ramfjordnes
  44. oid:
    2456998
    origin:
    Ramfjordnes
    did:
    2328281
    destination:
    Ramsund
  45. oid:
    2328281
    origin:
    Ramsund
    did:
    2328264
    destination:
    Harstad
  46. oid:
    2328264
    origin:
    Harstad
    did:
    2328281
    destination:
    Ramsund
  47. oid:
    2328281
    origin:
    Ramsund
    did:
    2328264
    destination:
    Harstad
  48. oid:
    2328264
    origin:
    Harstad
    did:
    2328281
    destination:
    Ramsund
  49. oid:
    2328281
    origin:
    Ramsund
    did:
    2328290
    destination:
    Sortland
  50. oid:
    2328361
    origin:
    Tromsø
    did:
    2328281
    destination:
    Ramsund
  51. oid:
    2328281
    origin:
    Ramsund
    did:
    2332022
    destination:
    Longyearbyen
  52. oid:
    2328281
    origin:
    Ramsund
    did:
    2447641
    destination:
    Barentshavet
  53. oid:
    2447641
    origin:
    Barentshavet
    did:
    2328281
    destination:
    Ramsund
  54. oid:
    2328141
    origin:
    Fedje
    did:
    2328281
    destination:
    Ramsund
  55. oid:
    2328281
    origin:
    Ramsund
    did:
    2447641
    destination:
    Barentshavet
  56. oid:
    2328281
    origin:
    Ramsund
    did:
    2332022
    destination:
    Longyearbyen
  57. oid:
    2328281
    origin:
    Ramsund
    did:
    2452195
    destination:
    Harstad ankring
  58. oid:
    2447641
    origin:
    Barentshavet
    did:
    2328281
    destination:
    Ramsund

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.