Gryllefjord

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T03:49:33Z.

Havn

havn_id:
2328332
navn:
Gryllefjord
kode:
NOGRY
type:
Havn
kommune:
Senja
fylke:
Troms
lat:
69.36215
lon:
17.06486

Port-call and departure connections

56 results

  1. oid:
    2328332
    origin:
    Gryllefjord
    did:
    2450228
    destination:
    Djupvik
  2. oid:
    2353296
    origin:
    Grøtsundet
    did:
    2328332
    destination:
    Gryllefjord
  3. oid:
    2353329
    origin:
    Tomma
    did:
    2328332
    destination:
    Gryllefjord
  4. oid:
    2465684
    origin:
    Grasmyr/ Klubben
    did:
    2328332
    destination:
    Gryllefjord
  5. oid:
    2451484
    origin:
    Stjernsundet
    did:
    2328332
    destination:
    Gryllefjord
  6. oid:
    2328340
    origin:
    Husøy - Lenvik
    did:
    2328332
    destination:
    Gryllefjord
  7. oid:
    2328251
    origin:
    Bodø
    did:
    2328332
    destination:
    Gryllefjord
  8. oid:
    2328251
    origin:
    Bodø
    did:
    2328332
    destination:
    Gryllefjord
  9. oid:
    2328357
    origin:
    Sommarøy
    did:
    2328332
    destination:
    Gryllefjord
  10. oid:
    2353289
    origin:
    Vikan - Bodø
    did:
    2328332
    destination:
    Gryllefjord
  11. oid:
    2328328
    origin:
    Finnsnes
    did:
    2328332
    destination:
    Gryllefjord
  12. oid:
    2328383
    origin:
    Senjahopen
    did:
    2328332
    destination:
    Gryllefjord
  13. oid:
    2328383
    origin:
    Senjahopen
    did:
    2328332
    destination:
    Gryllefjord
  14. oid:
    2328383
    origin:
    Senjahopen
    did:
    2328332
    destination:
    Gryllefjord
  15. oid:
    2328264
    origin:
    Harstad
    did:
    2328332
    destination:
    Gryllefjord
  16. oid:
    2328264
    origin:
    Harstad
    did:
    2328332
    destination:
    Gryllefjord
  17. oid:
    2328264
    origin:
    Harstad
    did:
    2328332
    destination:
    Gryllefjord
  18. oid:
    2328264
    origin:
    Harstad
    did:
    2328332
    destination:
    Gryllefjord
  19. oid:
    2328264
    origin:
    Harstad
    did:
    2328332
    destination:
    Gryllefjord
  20. oid:
    2328264
    origin:
    Harstad
    did:
    2328332
    destination:
    Gryllefjord
  21. oid:
    2328253
    origin:
    Borkenes
    did:
    2328332
    destination:
    Gryllefjord
  22. oid:
    2328356
    origin:
    Skjervøy
    did:
    2328332
    destination:
    Gryllefjord
  23. oid:
    2456998
    origin:
    Ramfjordnes
    did:
    2328332
    destination:
    Gryllefjord
  24. oid:
    2328290
    origin:
    Sortland
    did:
    2328332
    destination:
    Gryllefjord
  25. oid:
    2328361
    origin:
    Tromsø
    did:
    2328332
    destination:
    Gryllefjord
  26. oid:
    2328361
    origin:
    Tromsø
    did:
    2328332
    destination:
    Gryllefjord
  27. oid:
    2464662
    origin:
    Gavlfjorden
    did:
    2328332
    destination:
    Gryllefjord
  28. oid:
    2328248
    origin:
    Andenes
    did:
    2328332
    destination:
    Gryllefjord
  29. oid:
    2328332
    origin:
    Gryllefjord
    did:
    2328248
    destination:
    Andenes
  30. oid:
    2328332
    origin:
    Gryllefjord
    did:
    2328266
    destination:
    Henningsvær
  31. oid:
    2328332
    origin:
    Gryllefjord
    did:
    2450256
    destination:
    Risøyhamn
  32. oid:
    2328332
    origin:
    Gryllefjord
    did:
    2328361
    destination:
    Tromsø
  33. oid:
    2328332
    origin:
    Gryllefjord
    did:
    2328361
    destination:
    Tromsø
  34. oid:
    2328332
    origin:
    Gryllefjord
    did:
    2328361
    destination:
    Tromsø
  35. oid:
    2328332
    origin:
    Gryllefjord
    did:
    2328361
    destination:
    Tromsø
  36. oid:
    2328332
    origin:
    Gryllefjord
    did:
    2328361
    destination:
    Tromsø
  37. oid:
    2328332
    origin:
    Gryllefjord
    did:
    2328290
    destination:
    Sortland
  38. oid:
    2328332
    origin:
    Gryllefjord
    did:
    2328290
    destination:
    Sortland
  39. oid:
    2328332
    origin:
    Gryllefjord
    did:
    2328290
    destination:
    Sortland
  40. oid:
    2328332
    origin:
    Gryllefjord
    did:
    2328290
    destination:
    Sortland
  41. oid:
    2328332
    origin:
    Gryllefjord
    did:
    2328353
    destination:
    Skaland
  42. oid:
    2328332
    origin:
    Gryllefjord
    did:
    2328353
    destination:
    Skaland
  43. oid:
    2328332
    origin:
    Gryllefjord
    did:
    2451608
    destination:
    Akkarfjord
  44. oid:
    2328332
    origin:
    Gryllefjord
    did:
    2341653
    destination:
    Torsken
  45. oid:
    2328332
    origin:
    Gryllefjord
    did:
    2341653
    destination:
    Torsken
  46. oid:
    2328332
    origin:
    Gryllefjord
    did:
    2328264
    destination:
    Harstad
  47. oid:
    2328332
    origin:
    Gryllefjord
    did:
    2328264
    destination:
    Harstad
  48. oid:
    2328332
    origin:
    Gryllefjord
    did:
    2328264
    destination:
    Harstad
  49. oid:
    2328332
    origin:
    Gryllefjord
    did:
    2328209
    destination:
    Rørvik
  50. oid:
    2328332
    origin:
    Gryllefjord
    did:
    2328232
    destination:
    Ålesund
  51. oid:
    2328332
    origin:
    Gryllefjord
    did:
    2328251
    destination:
    Bodø
  52. oid:
    2328332
    origin:
    Gryllefjord
    did:
    2456952
    destination:
    Kvalfjord
  53. oid:
    2328332
    origin:
    Gryllefjord
    did:
    2456952
    destination:
    Kvalfjord
  54. oid:
    2328332
    origin:
    Gryllefjord
    did:
    2328340
    destination:
    Husøy - Lenvik
  55. oid:
    2328332
    origin:
    Gryllefjord
    did:
    2451484
    destination:
    Stjernsundet
  56. oid:
    2328332
    origin:
    Gryllefjord
    did:
    2328288
    destination:
    Skrolsvik

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.