Herreflaket ankring

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-11-04T08:45:24Z.

Havn

havn_id:
2466365
navn:
Herreflaket ankring
kode:
NOZER
type:
Ankerplass
kommune:
Skien
fylke:
Telemark
lat:
59.11201
lon:
9.574498

Port-call and departure connections

33 results

  1. oid:
    2466365
    origin:
    Herreflaket ankring
    did:
    2341694
    destination:
    Voll - Skien
  2. oid:
    2328061
    origin:
    Mekjarvik
    did:
    2466365
    destination:
    Herreflaket ankring
  3. oid:
    2466365
    origin:
    Herreflaket ankring
    did:
    2327955
    destination:
    Herøya
  4. oid:
    2327948
    origin:
    Larvik
    did:
    2466365
    destination:
    Herreflaket ankring
  5. oid:
    2466365
    origin:
    Herreflaket ankring
    did:
    2327949
    destination:
    Porsgrunn
  6. oid:
    2327996
    origin:
    Kvinesdal
    did:
    2466365
    destination:
    Herreflaket ankring
  7. oid:
    2466365
    origin:
    Herreflaket ankring
    did:
    2341694
    destination:
    Voll - Skien
  8. oid:
    2447401
    origin:
    Bøneset - Karmøy
    did:
    2466365
    destination:
    Herreflaket ankring
  9. oid:
    2466365
    origin:
    Herreflaket ankring
    did:
    2450098
    destination:
    Dunkirk
  10. oid:
    2341694
    origin:
    Voll - Skien
    did:
    2466365
    destination:
    Herreflaket ankring
  11. oid:
    2466365
    origin:
    Herreflaket ankring
    did:
    2327949
    destination:
    Porsgrunn
  12. oid:
    2329139
    origin:
    Vejle
    did:
    2466365
    destination:
    Herreflaket ankring
  13. oid:
    2466365
    origin:
    Herreflaket ankring
    did:
    2327949
    destination:
    Porsgrunn
  14. oid:
    2327996
    origin:
    Kvinesdal
    did:
    2466365
    destination:
    Herreflaket ankring
  15. oid:
    2466365
    origin:
    Herreflaket ankring
    did:
    2327949
    destination:
    Porsgrunn
  16. oid:
    2327966
    origin:
    Snekkevik - Kragerø
    did:
    2466365
    destination:
    Herreflaket ankring
  17. oid:
    2466365
    origin:
    Herreflaket ankring
    did:
    2327949
    destination:
    Porsgrunn
  18. oid:
    2329045
    origin:
    Hirtshals
    did:
    2466365
    destination:
    Herreflaket ankring
  19. oid:
    2466365
    origin:
    Herreflaket ankring
    did:
    2341694
    destination:
    Voll - Skien
  20. oid:
    2447401
    origin:
    Bøneset - Karmøy
    did:
    2466365
    destination:
    Herreflaket ankring
  21. oid:
    2466365
    origin:
    Herreflaket ankring
    did:
    2327969
    destination:
    Valberg - Kragerø
  22. oid:
    2327949
    origin:
    Porsgrunn
    did:
    2466365
    destination:
    Herreflaket ankring
  23. oid:
    2466365
    origin:
    Herreflaket ankring
    did:
    2327949
    destination:
    Porsgrunn
  24. oid:
    2328043
    origin:
    Sauda
    did:
    2466365
    destination:
    Herreflaket ankring
  25. oid:
    2466365
    origin:
    Herreflaket ankring
    did:
    2327949
    destination:
    Porsgrunn
  26. oid:
    2330507
    origin:
    Gdynia
    did:
    2466365
    destination:
    Herreflaket ankring
  27. oid:
    2466365
    origin:
    Herreflaket ankring
    did:
    2327949
    destination:
    Porsgrunn
  28. oid:
    2327996
    origin:
    Kvinesdal
    did:
    2466365
    destination:
    Herreflaket ankring
  29. oid:
    2466365
    origin:
    Herreflaket ankring
    did:
    2327949
    destination:
    Porsgrunn
  30. oid:
    2330496
    origin:
    Gdansk
    did:
    2466365
    destination:
    Herreflaket ankring
  31. oid:
    2466365
    origin:
    Herreflaket ankring
    did:
    2327949
    destination:
    Porsgrunn
  32. oid:
    2466365
    origin:
    Herreflaket ankring
    did:
    2327949
    destination:
    Porsgrunn
  33. oid:
    2329393
    origin:
    Flixborough
    did:
    2466365
    destination:
    Herreflaket ankring

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.