Radicatel

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T10:47:15Z.

Havn

havn_id:
2331628
navn:
Radicatel
kode:
not reported by source
type:
Havn
kommune:
not reported by source
fylke:
not reported by source
lat:
49.5
lon:
0.5

Port-call and departure connections

34 results

  1. oid:
    2331628
    origin:
    Radicatel
    did:
    2461790
    destination:
    Årebrotsfjorden ankring
  2. oid:
    2331628
    origin:
    Radicatel
    did:
    2461790
    destination:
    Årebrotsfjorden ankring
  3. oid:
    2331628
    origin:
    Radicatel
    did:
    2451494
    destination:
    Stavanger Øst
  4. oid:
    2331628
    origin:
    Radicatel
    did:
    2451494
    destination:
    Stavanger Øst
  5. oid:
    2331628
    origin:
    Radicatel
    did:
    2451494
    destination:
    Stavanger Øst
  6. oid:
    2331628
    origin:
    Radicatel
    did:
    2451494
    destination:
    Stavanger Øst
  7. oid:
    2331628
    origin:
    Radicatel
    did:
    2451494
    destination:
    Stavanger Øst
  8. oid:
    2331628
    origin:
    Radicatel
    did:
    2451494
    destination:
    Stavanger Øst
  9. oid:
    2331628
    origin:
    Radicatel
    did:
    2451494
    destination:
    Stavanger Øst
  10. oid:
    2331628
    origin:
    Radicatel
    did:
    2451494
    destination:
    Stavanger Øst
  11. oid:
    2331628
    origin:
    Radicatel
    did:
    2451494
    destination:
    Stavanger Øst
  12. oid:
    2331628
    origin:
    Radicatel
    did:
    2451494
    destination:
    Stavanger Øst
  13. oid:
    2331628
    origin:
    Radicatel
    did:
    2451494
    destination:
    Stavanger Øst
  14. oid:
    2331628
    origin:
    Radicatel
    did:
    2328162
    destination:
    Freifjorden ankring
  15. oid:
    2331628
    origin:
    Radicatel
    did:
    2328146
    destination:
    Gunhildvågen
  16. oid:
    2331628
    origin:
    Radicatel
    did:
    2328146
    destination:
    Gunhildvågen
  17. oid:
    2331628
    origin:
    Radicatel
    did:
    2328146
    destination:
    Gunhildvågen
  18. oid:
    2331628
    origin:
    Radicatel
    did:
    2328146
    destination:
    Gunhildvågen
  19. oid:
    2331628
    origin:
    Radicatel
    did:
    2328146
    destination:
    Gunhildvågen
  20. oid:
    2331628
    origin:
    Radicatel
    did:
    2328146
    destination:
    Gunhildvågen
  21. oid:
    2328146
    origin:
    Gunhildvågen
    did:
    2331628
    destination:
    Radicatel
  22. oid:
    2451494
    origin:
    Stavanger Øst
    did:
    2331628
    destination:
    Radicatel
  23. oid:
    2328100
    origin:
    Måløy
    did:
    2331628
    destination:
    Radicatel
  24. oid:
    2328100
    origin:
    Måløy
    did:
    2331628
    destination:
    Radicatel
  25. oid:
    2327904
    origin:
    Drammen
    did:
    2331628
    destination:
    Radicatel
  26. oid:
    2331628
    origin:
    Radicatel
    did:
    2328063
    destination:
    Husøy - Karmøy
  27. oid:
    2331628
    origin:
    Radicatel
    did:
    2328063
    destination:
    Husøy - Karmøy
  28. oid:
    2331628
    origin:
    Radicatel
    did:
    2328063
    destination:
    Husøy - Karmøy
  29. oid:
    2331628
    origin:
    Radicatel
    did:
    2328063
    destination:
    Husøy - Karmøy
  30. oid:
    2331628
    origin:
    Radicatel
    did:
    2328063
    destination:
    Husøy - Karmøy
  31. oid:
    2331628
    origin:
    Radicatel
    did:
    2328063
    destination:
    Husøy - Karmøy
  32. oid:
    2331628
    origin:
    Radicatel
    did:
    2328157
    destination:
    Averøy
  33. oid:
    2331628
    origin:
    Radicatel
    did:
    2328157
    destination:
    Averøy
  34. oid:
    2331628
    origin:
    Radicatel
    did:
    2328157
    destination:
    Averøy

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.