Flushing

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T04:42:19Z.

Havn

havn_id:
2447952
navn:
Flushing
kode:
not reported by source
type:
Havn
kommune:
not reported by source
fylke:
not reported by source
lat:
50.15
lon:
-5.06666666666667

Port-call and departure connections

30 results

  1. oid:
    2447952
    origin:
    Flushing
    did:
    2328099
    destination:
    Mongstad
  2. oid:
    2447952
    origin:
    Flushing
    did:
    2328303
    destination:
    Salten
  3. oid:
    2447952
    origin:
    Flushing
    did:
    2328303
    destination:
    Salten
  4. oid:
    2447952
    origin:
    Flushing
    did:
    2328303
    destination:
    Salten
  5. oid:
    2447952
    origin:
    Flushing
    did:
    2328303
    destination:
    Salten
  6. oid:
    2447952
    origin:
    Flushing
    did:
    2327955
    destination:
    Herøya
  7. oid:
    2447952
    origin:
    Flushing
    did:
    2458542
    destination:
    Lødingen ankring
  8. oid:
    2447952
    origin:
    Flushing
    did:
    2327974
    destination:
    Frierfjorden ankring
  9. oid:
    2447952
    origin:
    Flushing
    did:
    2328275
    destination:
    Mosjøen
  10. oid:
    2328090
    origin:
    Husnes
    did:
    2447952
    destination:
    Flushing
  11. oid:
    2328034
    origin:
    Kårstø
    did:
    2447952
    destination:
    Flushing
  12. oid:
    2328034
    origin:
    Kårstø
    did:
    2447952
    destination:
    Flushing
  13. oid:
    2328034
    origin:
    Kårstø
    did:
    2447952
    destination:
    Flushing
  14. oid:
    2328034
    origin:
    Kårstø
    did:
    2447952
    destination:
    Flushing
  15. oid:
    2328034
    origin:
    Kårstø
    did:
    2447952
    destination:
    Flushing
  16. oid:
    2328034
    origin:
    Kårstø
    did:
    2447952
    destination:
    Flushing
  17. oid:
    2328034
    origin:
    Kårstø
    did:
    2447952
    destination:
    Flushing
  18. oid:
    2328034
    origin:
    Kårstø
    did:
    2447952
    destination:
    Flushing
  19. oid:
    2327949
    origin:
    Porsgrunn
    did:
    2447952
    destination:
    Flushing
  20. oid:
    2327949
    origin:
    Porsgrunn
    did:
    2447952
    destination:
    Flushing
  21. oid:
    2327949
    origin:
    Porsgrunn
    did:
    2447952
    destination:
    Flushing
  22. oid:
    2327949
    origin:
    Porsgrunn
    did:
    2447952
    destination:
    Flushing
  23. oid:
    2327949
    origin:
    Porsgrunn
    did:
    2447952
    destination:
    Flushing
  24. oid:
    2328279
    origin:
    Narvik
    did:
    2447952
    destination:
    Flushing
  25. oid:
    2327958
    origin:
    Rafnes
    did:
    2447952
    destination:
    Flushing
  26. oid:
    2327958
    origin:
    Rafnes
    did:
    2447952
    destination:
    Flushing
  27. oid:
    2466374
    origin:
    Valderhaugfjorden ankring
    did:
    2447952
    destination:
    Flushing
  28. oid:
    2447952
    origin:
    Flushing
    did:
    2353311
    destination:
    Narvikbukta ankring
  29. oid:
    2447952
    origin:
    Flushing
    did:
    2447455
    destination:
    Risavika
  30. oid:
    2447952
    origin:
    Flushing
    did:
    2328182
    destination:
    Holla

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.