Skirne

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T05:43:03Z.

Havn

havn_id:
2456547
navn:
Skirne
kode:
not reported by source
type:
Offshoreinstallasjon
kommune:
not reported by source
fylke:
not reported by source
lat:
not reported by source
lon:
not reported by source

Port-call and departure connections

54 results

  1. oid:
    2456547
    origin:
    Skirne
    did:
    2328049
    destination:
    Tananger
  2. oid:
    2456547
    origin:
    Skirne
    did:
    2328051
    destination:
    Åmøyfjorden ankring
  3. oid:
    2456547
    origin:
    Skirne
    did:
    2447455
    destination:
    Risavika
  4. oid:
    2456547
    origin:
    Skirne
    did:
    2447455
    destination:
    Risavika
  5. oid:
    2456547
    origin:
    Skirne
    did:
    2447455
    destination:
    Risavika
  6. oid:
    2456547
    origin:
    Skirne
    did:
    2447455
    destination:
    Risavika
  7. oid:
    2456547
    origin:
    Skirne
    did:
    2447455
    destination:
    Risavika
  8. oid:
    2456547
    origin:
    Skirne
    did:
    2447455
    destination:
    Risavika
  9. oid:
    2456547
    origin:
    Skirne
    did:
    2447455
    destination:
    Risavika
  10. oid:
    2456547
    origin:
    Skirne
    did:
    2447455
    destination:
    Risavika
  11. oid:
    2456547
    origin:
    Skirne
    did:
    2447455
    destination:
    Risavika
  12. oid:
    2456547
    origin:
    Skirne
    did:
    2447455
    destination:
    Risavika
  13. oid:
    2456547
    origin:
    Skirne
    did:
    2447455
    destination:
    Risavika
  14. oid:
    2456547
    origin:
    Skirne
    did:
    2447455
    destination:
    Risavika
  15. oid:
    2456547
    origin:
    Skirne
    did:
    2447455
    destination:
    Risavika
  16. oid:
    2456547
    origin:
    Skirne
    did:
    2447455
    destination:
    Risavika
  17. oid:
    2456547
    origin:
    Skirne
    did:
    2447455
    destination:
    Risavika
  18. oid:
    2456547
    origin:
    Skirne
    did:
    2447455
    destination:
    Risavika
  19. oid:
    2456547
    origin:
    Skirne
    did:
    2447455
    destination:
    Risavika
  20. oid:
    2456547
    origin:
    Skirne
    did:
    2447455
    destination:
    Risavika
  21. oid:
    2456547
    origin:
    Skirne
    did:
    2447455
    destination:
    Risavika
  22. oid:
    2456547
    origin:
    Skirne
    did:
    2447455
    destination:
    Risavika
  23. oid:
    2456547
    origin:
    Skirne
    did:
    2447455
    destination:
    Risavika
  24. oid:
    2456547
    origin:
    Skirne
    did:
    2447455
    destination:
    Risavika
  25. oid:
    2456547
    origin:
    Skirne
    did:
    2447455
    destination:
    Risavika
  26. oid:
    2456547
    origin:
    Skirne
    did:
    2447455
    destination:
    Risavika
  27. oid:
    2456547
    origin:
    Skirne
    did:
    2447455
    destination:
    Risavika
  28. oid:
    2447455
    origin:
    Risavika
    did:
    2456547
    destination:
    Skirne
  29. oid:
    2447455
    origin:
    Risavika
    did:
    2456547
    destination:
    Skirne
  30. oid:
    2447455
    origin:
    Risavika
    did:
    2456547
    destination:
    Skirne
  31. oid:
    2447455
    origin:
    Risavika
    did:
    2456547
    destination:
    Skirne
  32. oid:
    2447455
    origin:
    Risavika
    did:
    2456547
    destination:
    Skirne
  33. oid:
    2447455
    origin:
    Risavika
    did:
    2456547
    destination:
    Skirne
  34. oid:
    2447455
    origin:
    Risavika
    did:
    2456547
    destination:
    Skirne
  35. oid:
    2447455
    origin:
    Risavika
    did:
    2456547
    destination:
    Skirne
  36. oid:
    2447455
    origin:
    Risavika
    did:
    2456547
    destination:
    Skirne
  37. oid:
    2447455
    origin:
    Risavika
    did:
    2456547
    destination:
    Skirne
  38. oid:
    2447455
    origin:
    Risavika
    did:
    2456547
    destination:
    Skirne
  39. oid:
    2447455
    origin:
    Risavika
    did:
    2456547
    destination:
    Skirne
  40. oid:
    2447455
    origin:
    Risavika
    did:
    2456547
    destination:
    Skirne
  41. oid:
    2447455
    origin:
    Risavika
    did:
    2456547
    destination:
    Skirne
  42. oid:
    2447455
    origin:
    Risavika
    did:
    2456547
    destination:
    Skirne
  43. oid:
    2447455
    origin:
    Risavika
    did:
    2456547
    destination:
    Skirne
  44. oid:
    2447455
    origin:
    Risavika
    did:
    2456547
    destination:
    Skirne
  45. oid:
    2447455
    origin:
    Risavika
    did:
    2456547
    destination:
    Skirne
  46. oid:
    2447455
    origin:
    Risavika
    did:
    2456547
    destination:
    Skirne
  47. oid:
    2447455
    origin:
    Risavika
    did:
    2456547
    destination:
    Skirne
  48. oid:
    2447455
    origin:
    Risavika
    did:
    2456547
    destination:
    Skirne
  49. oid:
    2447455
    origin:
    Risavika
    did:
    2456547
    destination:
    Skirne
  50. oid:
    2447455
    origin:
    Risavika
    did:
    2456547
    destination:
    Skirne
  51. oid:
    2447455
    origin:
    Risavika
    did:
    2456547
    destination:
    Skirne
  52. oid:
    2328051
    origin:
    Åmøyfjorden ankring
    did:
    2456547
    destination:
    Skirne
  53. oid:
    2328051
    origin:
    Åmøyfjorden ankring
    did:
    2456547
    destination:
    Skirne
  54. oid:
    2328049
    origin:
    Tananger
    did:
    2456547
    destination:
    Skirne

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.