Oseberg Sør

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-11-04T15:56:26Z.

Havn

havn_id:
2456540
navn:
Oseberg Sør
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

33 results

  1. oid:
    2328078
    origin:
    Bergen
    did:
    2456540
    destination:
    Oseberg Sør
  2. oid:
    2456540
    origin:
    Oseberg Sør
    did:
    2328078
    destination:
    Bergen
  3. oid:
    2328078
    origin:
    Bergen
    did:
    2456540
    destination:
    Oseberg Sør
  4. oid:
    2456540
    origin:
    Oseberg Sør
    did:
    2328078
    destination:
    Bergen
  5. oid:
    2328078
    origin:
    Bergen
    did:
    2456540
    destination:
    Oseberg Sør
  6. oid:
    2456540
    origin:
    Oseberg Sør
    did:
    2328078
    destination:
    Bergen
  7. oid:
    2328063
    origin:
    Husøy - Karmøy
    did:
    2456540
    destination:
    Oseberg Sør
  8. oid:
    2456540
    origin:
    Oseberg Sør
    did:
    2328063
    destination:
    Husøy - Karmøy
  9. oid:
    2456540
    origin:
    Oseberg Sør
    did:
    2328128
    destination:
    Rubbestadneset
  10. oid:
    2456540
    origin:
    Oseberg Sør
    did:
    2328189
    destination:
    Kristiansund
  11. oid:
    2328189
    origin:
    Kristiansund
    did:
    2456540
    destination:
    Oseberg Sør
  12. oid:
    2328078
    origin:
    Bergen
    did:
    2456540
    destination:
    Oseberg Sør
  13. oid:
    2456540
    origin:
    Oseberg Sør
    did:
    2328078
    destination:
    Bergen
  14. oid:
    2328078
    origin:
    Bergen
    did:
    2456540
    destination:
    Oseberg Sør
  15. oid:
    2328128
    origin:
    Rubbestadneset
    did:
    2456540
    destination:
    Oseberg Sør
  16. oid:
    2456540
    origin:
    Oseberg Sør
    did:
    2328128
    destination:
    Rubbestadneset
  17. oid:
    2328078
    origin:
    Bergen
    did:
    2456540
    destination:
    Oseberg Sør
  18. oid:
    2456540
    origin:
    Oseberg Sør
    did:
    2328078
    destination:
    Bergen
  19. oid:
    2328078
    origin:
    Bergen
    did:
    2456540
    destination:
    Oseberg Sør
  20. oid:
    2456540
    origin:
    Oseberg Sør
    did:
    2328129
    destination:
    Ågotnes
  21. oid:
    2328078
    origin:
    Bergen
    did:
    2456540
    destination:
    Oseberg Sør
  22. oid:
    2456540
    origin:
    Oseberg Sør
    did:
    2328078
    destination:
    Bergen
  23. oid:
    2328078
    origin:
    Bergen
    did:
    2456540
    destination:
    Oseberg Sør
  24. oid:
    2456540
    origin:
    Oseberg Sør
    did:
    2328078
    destination:
    Bergen
  25. oid:
    2451419
    origin:
    Laksevåg
    did:
    2456540
    destination:
    Oseberg Sør
  26. oid:
    2456540
    origin:
    Oseberg Sør
    did:
    2451419
    destination:
    Laksevåg
  27. oid:
    2454916
    origin:
    Fram
    did:
    2456540
    destination:
    Oseberg Sør
  28. oid:
    2328124
    origin:
    Mongstadbase
    did:
    2456540
    destination:
    Oseberg Sør
  29. oid:
    2456540
    origin:
    Oseberg Sør
    did:
    2328124
    destination:
    Mongstadbase
  30. oid:
    2328124
    origin:
    Mongstadbase
    did:
    2456540
    destination:
    Oseberg Sør
  31. oid:
    2456540
    origin:
    Oseberg Sør
    did:
    2328125
    destination:
    Sløvåg Industriområde
  32. oid:
    2456540
    origin:
    Oseberg Sør
    did:
    2328078
    destination:
    Bergen
  33. oid:
    2328124
    origin:
    Mongstadbase
    did:
    2456540
    destination:
    Oseberg Sør

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.