Bellvika

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T04:58:12Z.

Havn

havn_id:
2452158
navn:
Bellvika
kode:
NOBEL
type:
Havn
kommune:
Tromsø
fylke:
Troms
lat:
69.78673
lon:
18.76293

Port-call and departure connections

34 results

  1. oid:
    2452158
    origin:
    Bellvika
    did:
    2450228
    destination:
    Djupvik
  2. oid:
    2452158
    origin:
    Bellvika
    did:
    2328351
    destination:
    Reinfjord
  3. oid:
    2452158
    origin:
    Bellvika
    did:
    2451829
    destination:
    Olderdalen
  4. oid:
    2328263
    origin:
    Hammerfall
    did:
    2452158
    destination:
    Bellvika
  5. oid:
    2451489
    origin:
    Bergsfjord
    did:
    2452158
    destination:
    Bellvika
  6. oid:
    2465684
    origin:
    Grasmyr/ Klubben
    did:
    2452158
    destination:
    Bellvika
  7. oid:
    2451482
    origin:
    Sammelsund
    did:
    2452158
    destination:
    Bellvika
  8. oid:
    2467368
    origin:
    Maurnes ankring
    did:
    2452158
    destination:
    Bellvika
  9. oid:
    2353239
    origin:
    Grøtavær
    did:
    2452158
    destination:
    Bellvika
  10. oid:
    2328356
    origin:
    Skjervøy
    did:
    2452158
    destination:
    Bellvika
  11. oid:
    2328356
    origin:
    Skjervøy
    did:
    2452158
    destination:
    Bellvika
  12. oid:
    2328353
    origin:
    Skaland
    did:
    2452158
    destination:
    Bellvika
  13. oid:
    2328353
    origin:
    Skaland
    did:
    2452158
    destination:
    Bellvika
  14. oid:
    2328290
    origin:
    Sortland
    did:
    2452158
    destination:
    Bellvika
  15. oid:
    2328290
    origin:
    Sortland
    did:
    2452158
    destination:
    Bellvika
  16. oid:
    2328361
    origin:
    Tromsø
    did:
    2452158
    destination:
    Bellvika
  17. oid:
    2328361
    origin:
    Tromsø
    did:
    2452158
    destination:
    Bellvika
  18. oid:
    2328361
    origin:
    Tromsø
    did:
    2452158
    destination:
    Bellvika
  19. oid:
    2328361
    origin:
    Tromsø
    did:
    2452158
    destination:
    Bellvika
  20. oid:
    2451588
    origin:
    Hansnes
    did:
    2452158
    destination:
    Bellvika
  21. oid:
    2452158
    origin:
    Bellvika
    did:
    2328361
    destination:
    Tromsø
  22. oid:
    2452158
    origin:
    Bellvika
    did:
    2456882
    destination:
    Årstein-Gratangen
  23. oid:
    2452158
    origin:
    Bellvika
    did:
    2328353
    destination:
    Skaland
  24. oid:
    2452158
    origin:
    Bellvika
    did:
    2328356
    destination:
    Skjervøy
  25. oid:
    2452158
    origin:
    Bellvika
    did:
    2328356
    destination:
    Skjervøy
  26. oid:
    2452158
    origin:
    Bellvika
    did:
    2447367
    destination:
    Anfinnsletta
  27. oid:
    2452158
    origin:
    Bellvika
    did:
    2451879
    destination:
    Lauksundet
  28. oid:
    2452158
    origin:
    Bellvika
    did:
    2451879
    destination:
    Lauksundet
  29. oid:
    2452158
    origin:
    Bellvika
    did:
    2451879
    destination:
    Lauksundet
  30. oid:
    2452158
    origin:
    Bellvika
    did:
    2451879
    destination:
    Lauksundet
  31. oid:
    2452158
    origin:
    Bellvika
    did:
    2451879
    destination:
    Lauksundet
  32. oid:
    2452158
    origin:
    Bellvika
    did:
    2451879
    destination:
    Lauksundet
  33. oid:
    2452158
    origin:
    Bellvika
    did:
    2467368
    destination:
    Maurnes ankring
  34. oid:
    2452158
    origin:
    Bellvika
    did:
    2328335
    destination:
    Hammerfest

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.