Botingé

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T11:20:28Z.

Havn

havn_id:
2331956
navn:
Botingé
kode:
not reported by source
type:
Havn
kommune:
not reported by source
fylke:
not reported by source
lat:
56.0666666666667
lon:
21.1166666666667

Port-call and departure connections

55 results

  1. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  2. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  3. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  4. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  5. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  6. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  7. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  8. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  9. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  10. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  11. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  12. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  13. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  14. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  15. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  16. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  17. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  18. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  19. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  20. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  21. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  22. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  23. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  24. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  25. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  26. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  27. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  28. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  29. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  30. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  31. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  32. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  33. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  34. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  35. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  36. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  37. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  38. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  39. oid:
    2331956
    origin:
    Botingé
    did:
    2328099
    destination:
    Mongstad
  40. oid:
    2331956
    origin:
    Botingé
    did:
    2328034
    destination:
    Kårstø
  41. oid:
    2331956
    origin:
    Botingé
    did:
    2328034
    destination:
    Kårstø
  42. oid:
    2331956
    origin:
    Botingé
    did:
    2328120
    destination:
    Sture
  43. oid:
    2331956
    origin:
    Botingé
    did:
    2328120
    destination:
    Sture
  44. oid:
    2331956
    origin:
    Botingé
    did:
    2328120
    destination:
    Sture
  45. oid:
    2331956
    origin:
    Botingé
    did:
    2328120
    destination:
    Sture
  46. oid:
    2331956
    origin:
    Botingé
    did:
    2328120
    destination:
    Sture
  47. oid:
    2331956
    origin:
    Botingé
    did:
    2328120
    destination:
    Sture
  48. oid:
    2331956
    origin:
    Botingé
    did:
    2328120
    destination:
    Sture
  49. oid:
    2331956
    origin:
    Botingé
    did:
    2328120
    destination:
    Sture
  50. oid:
    2328120
    origin:
    Sture
    did:
    2331956
    destination:
    Botingé
  51. oid:
    2328120
    origin:
    Sture
    did:
    2331956
    destination:
    Botingé
  52. oid:
    2328099
    origin:
    Mongstad
    did:
    2331956
    destination:
    Botingé
  53. oid:
    2328099
    origin:
    Mongstad
    did:
    2331956
    destination:
    Botingé
  54. oid:
    2328099
    origin:
    Mongstad
    did:
    2331956
    destination:
    Botingé
  55. oid:
    2328099
    origin:
    Mongstad
    did:
    2331956
    destination:
    Botingé

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.