Djupivogur

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-08-03T07:13:02Z.

Havn

havn_id:
2329808
navn:
Djupivogur
kode:
not reported by source
type:
Havn
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

16 results

  1. oid:
    2329808
    origin:
    Djupivogur
    did:
    2451610
    destination:
    Hjelset
  2. oid:
    2329808
    origin:
    Djupivogur
    did:
    2328234
    destination:
    Valsneset
  3. oid:
    2447404
    origin:
    Storesund
    did:
    2329808
    destination:
    Djupivogur
  4. oid:
    2329808
    origin:
    Djupivogur
    did:
    2328158
    destination:
    Bjugn
  5. oid:
    2329808
    origin:
    Djupivogur
    did:
    2328158
    destination:
    Bjugn
  6. oid:
    2328339
    origin:
    Honningsvåg
    did:
    2329808
    destination:
    Djupivogur
  7. oid:
    2328232
    origin:
    Ålesund
    did:
    2329808
    destination:
    Djupivogur
  8. oid:
    2329808
    origin:
    Djupivogur
    did:
    2328291
    destination:
    Stokmarknes
  9. oid:
    2329808
    origin:
    Djupivogur
    did:
    2328158
    destination:
    Bjugn
  10. oid:
    2329808
    origin:
    Djupivogur
    did:
    2328189
    destination:
    Kristiansund
  11. oid:
    2329808
    origin:
    Djupivogur
    did:
    2353256
    destination:
    Lovund
  12. oid:
    2329808
    origin:
    Djupivogur
    did:
    2328189
    destination:
    Kristiansund
  13. oid:
    2328232
    origin:
    Ålesund
    did:
    2329808
    destination:
    Djupivogur
  14. oid:
    2328232
    origin:
    Ålesund
    did:
    2329808
    destination:
    Djupivogur
  15. oid:
    2329808
    origin:
    Djupivogur
    did:
    2328028
    destination:
    Haugesund
  16. oid:
    2328232
    origin:
    Ålesund
    did:
    2329808
    destination:
    Djupivogur

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.