St Petersburg

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-11-04T10:28:46Z.

Havn

havn_id:
2330405
navn:
St Petersburg
kode:
not reported by source
type:
Havn
kommune:
not reported by source
fylke:
not reported by source
lat:
59.8833333333333
lon:
30.25

Port-call and departure connections

32 results

  1. oid:
    2330405
    origin:
    St Petersburg
    did:
    2328361
    destination:
    Tromsø
  2. oid:
    2330405
    origin:
    St Petersburg
    did:
    2328361
    destination:
    Tromsø
  3. oid:
    2330405
    origin:
    St Petersburg
    did:
    2452438
    destination:
    Rechechefjorden
  4. oid:
    2330405
    origin:
    St Petersburg
    did:
    2328100
    destination:
    Måløy
  5. oid:
    2330405
    origin:
    St Petersburg
    did:
    2328290
    destination:
    Sortland
  6. oid:
    2330405
    origin:
    St Petersburg
    did:
    2328100
    destination:
    Måløy
  7. oid:
    2330405
    origin:
    St Petersburg
    did:
    2328327
    destination:
    Båtsfjord
  8. oid:
    2330405
    origin:
    St Petersburg
    did:
    2451419
    destination:
    Laksevåg
  9. oid:
    2330405
    origin:
    St Petersburg
    did:
    2451419
    destination:
    Laksevåg
  10. oid:
    2330405
    origin:
    St Petersburg
    did:
    2328100
    destination:
    Måløy
  11. oid:
    2330405
    origin:
    St Petersburg
    did:
    2451419
    destination:
    Laksevåg
  12. oid:
    2330405
    origin:
    St Petersburg
    did:
    2328100
    destination:
    Måløy
  13. oid:
    2330405
    origin:
    St Petersburg
    did:
    2328361
    destination:
    Tromsø
  14. oid:
    2330405
    origin:
    St Petersburg
    did:
    2328168
    destination:
    Ellingsøy
  15. oid:
    2327923
    origin:
    Oslo
    did:
    2330405
    destination:
    St Petersburg
  16. oid:
    2327923
    origin:
    Oslo
    did:
    2330405
    destination:
    St Petersburg
  17. oid:
    2451494
    origin:
    Stavanger Øst
    did:
    2330405
    destination:
    St Petersburg
  18. oid:
    2328218
    origin:
    Sunndalsøra
    did:
    2330405
    destination:
    St Petersburg
  19. oid:
    2328218
    origin:
    Sunndalsøra
    did:
    2330405
    destination:
    St Petersburg
  20. oid:
    2327908
    origin:
    Fredrikstad
    did:
    2330405
    destination:
    St Petersburg
  21. oid:
    2328218
    origin:
    Sunndalsøra
    did:
    2330405
    destination:
    St Petersburg
  22. oid:
    2327908
    origin:
    Fredrikstad
    did:
    2330405
    destination:
    St Petersburg
  23. oid:
    2328119
    origin:
    Årdalstangen
    did:
    2330405
    destination:
    St Petersburg
  24. oid:
    2328119
    origin:
    Årdalstangen
    did:
    2330405
    destination:
    St Petersburg
  25. oid:
    2328119
    origin:
    Årdalstangen
    did:
    2330405
    destination:
    St Petersburg
  26. oid:
    2327908
    origin:
    Fredrikstad
    did:
    2330405
    destination:
    St Petersburg
  27. oid:
    2328218
    origin:
    Sunndalsøra
    did:
    2330405
    destination:
    St Petersburg
  28. oid:
    2330405
    origin:
    St Petersburg
    did:
    2328361
    destination:
    Tromsø
  29. oid:
    2330405
    origin:
    St Petersburg
    did:
    2328343
    destination:
    Kirkenes
  30. oid:
    2328122
    origin:
    Tyssedal
    did:
    2330405
    destination:
    St Petersburg
  31. oid:
    2330405
    origin:
    St Petersburg
    did:
    2450409
    destination:
    Nordspissen - Tromsø
  32. oid:
    2330405
    origin:
    St Petersburg
    did:
    2328343
    destination:
    Kirkenes

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.