Allemannsdata Wiki
Manual search

Hartlepool

Port information and reported port connections from Kystdatahuset.

Programmatic access to port data (JSON)

Source: Kystdatahuset. Retrieved 2026-09-20T06:53:13Z.

Havn

Open the place page for this point

havn_id:
2329449
navn:
Hartlepool
kode:
not reported by source
type:
Havn
kommune:
not reported by source
fylke:
not reported by source
lat:
54.6833333333333
lon:
-1.21666666666667

Port-call and departure connections

72 results

  1. oid:
    2329449
    origin:
    Hartlepool
    did:
    2328155
    destination:
    Aukra
  2. oid:
    2328189
    origin:
    Kristiansund
    did:
    2329449
    destination:
    Hartlepool
  3. oid:
    2328224
    origin:
    Ulsteinvik
    did:
    2329449
    destination:
    Hartlepool
  4. oid:
    2328263
    origin:
    Hammerfall
    did:
    2329449
    destination:
    Hartlepool
  5. oid:
    2328263
    origin:
    Hammerfall
    did:
    2329449
    destination:
    Hartlepool
  6. oid:
    2328263
    origin:
    Hammerfall
    did:
    2329449
    destination:
    Hartlepool
  7. oid:
    2328263
    origin:
    Hammerfall
    did:
    2329449
    destination:
    Hartlepool
  8. oid:
    2328263
    origin:
    Hammerfall
    did:
    2329449
    destination:
    Hartlepool
  9. oid:
    2328263
    origin:
    Hammerfall
    did:
    2329449
    destination:
    Hartlepool
  10. oid:
    2328263
    origin:
    Hammerfall
    did:
    2329449
    destination:
    Hartlepool
  11. oid:
    2328263
    origin:
    Hammerfall
    did:
    2329449
    destination:
    Hartlepool
  12. oid:
    2328263
    origin:
    Hammerfall
    did:
    2329449
    destination:
    Hartlepool
  13. oid:
    2328263
    origin:
    Hammerfall
    did:
    2329449
    destination:
    Hartlepool
  14. oid:
    2328061
    origin:
    Mekjarvik
    did:
    2329449
    destination:
    Hartlepool
  15. oid:
    2328061
    origin:
    Mekjarvik
    did:
    2329449
    destination:
    Hartlepool
  16. oid:
    2447660
    origin:
    Nordsjøen
    did:
    2329449
    destination:
    Hartlepool
  17. oid:
    2328023
    origin:
    Dusavik
    did:
    2329449
    destination:
    Hartlepool
  18. oid:
    2328100
    origin:
    Måløy
    did:
    2329449
    destination:
    Hartlepool
  19. oid:
    2328100
    origin:
    Måløy
    did:
    2329449
    destination:
    Hartlepool
  20. oid:
    2328100
    origin:
    Måløy
    did:
    2329449
    destination:
    Hartlepool
  21. oid:
    2328100
    origin:
    Måløy
    did:
    2329449
    destination:
    Hartlepool
  22. oid:
    2328100
    origin:
    Måløy
    did:
    2329449
    destination:
    Hartlepool
  23. oid:
    2328100
    origin:
    Måløy
    did:
    2329449
    destination:
    Hartlepool
  24. oid:
    2328100
    origin:
    Måløy
    did:
    2329449
    destination:
    Hartlepool
  25. oid:
    2328100
    origin:
    Måløy
    did:
    2329449
    destination:
    Hartlepool
  26. oid:
    2328100
    origin:
    Måløy
    did:
    2329449
    destination:
    Hartlepool
  27. oid:
    2328100
    origin:
    Måløy
    did:
    2329449
    destination:
    Hartlepool
  28. oid:
    2328100
    origin:
    Måløy
    did:
    2329449
    destination:
    Hartlepool
  29. oid:
    2328100
    origin:
    Måløy
    did:
    2329449
    destination:
    Hartlepool
  30. oid:
    2328160
    origin:
    Brattvåg
    did:
    2329449
    destination:
    Hartlepool
  31. oid:
    2328286
    origin:
    Sandnessjøen
    did:
    2329449
    destination:
    Hartlepool
  32. oid:
    2451550
    origin:
    Stord base
    did:
    2329449
    destination:
    Hartlepool
  33. oid:
    2451550
    origin:
    Stord base
    did:
    2329449
    destination:
    Hartlepool
  34. oid:
    2451550
    origin:
    Stord base
    did:
    2329449
    destination:
    Hartlepool
  35. oid:
    2451550
    origin:
    Stord base
    did:
    2329449
    destination:
    Hartlepool
  36. oid:
    2451550
    origin:
    Stord base
    did:
    2329449
    destination:
    Hartlepool
  37. oid:
    2451550
    origin:
    Stord base
    did:
    2329449
    destination:
    Hartlepool
  38. oid:
    2451550
    origin:
    Stord base
    did:
    2329449
    destination:
    Hartlepool
  39. oid:
    2451550
    origin:
    Stord base
    did:
    2329449
    destination:
    Hartlepool
  40. oid:
    2451550
    origin:
    Stord base
    did:
    2329449
    destination:
    Hartlepool
  41. oid:
    2451550
    origin:
    Stord base
    did:
    2329449
    destination:
    Hartlepool
  42. oid:
    2451550
    origin:
    Stord base
    did:
    2329449
    destination:
    Hartlepool
  43. oid:
    2451550
    origin:
    Stord base
    did:
    2329449
    destination:
    Hartlepool
  44. oid:
    2329449
    origin:
    Hartlepool
    did:
    2451550
    destination:
    Stord base
  45. oid:
    2329449
    origin:
    Hartlepool
    did:
    2451550
    destination:
    Stord base
  46. oid:
    2329449
    origin:
    Hartlepool
    did:
    2451550
    destination:
    Stord base
  47. oid:
    2329449
    origin:
    Hartlepool
    did:
    2451550
    destination:
    Stord base
  48. oid:
    2329449
    origin:
    Hartlepool
    did:
    2451550
    destination:
    Stord base
  49. oid:
    2329449
    origin:
    Hartlepool
    did:
    2451550
    destination:
    Stord base
  50. oid:
    2329449
    origin:
    Hartlepool
    did:
    2451550
    destination:
    Stord base
  51. oid:
    2329449
    origin:
    Hartlepool
    did:
    2451550
    destination:
    Stord base
  52. oid:
    2329449
    origin:
    Hartlepool
    did:
    2451550
    destination:
    Stord base
  53. oid:
    2329449
    origin:
    Hartlepool
    did:
    2451550
    destination:
    Stord base
  54. oid:
    2329449
    origin:
    Hartlepool
    did:
    2328082
    destination:
    Eikefet
  55. oid:
    2329449
    origin:
    Hartlepool
    did:
    2328082
    destination:
    Eikefet
  56. oid:
    2329449
    origin:
    Hartlepool
    did:
    2328361
    destination:
    Tromsø
  57. oid:
    2329449
    origin:
    Hartlepool
    did:
    2466372
    destination:
    Leirvik ankring
  58. oid:
    2329449
    origin:
    Hartlepool
    did:
    2466372
    destination:
    Leirvik ankring
  59. oid:
    2329449
    origin:
    Hartlepool
    did:
    2466372
    destination:
    Leirvik ankring
  60. oid:
    2329449
    origin:
    Hartlepool
    did:
    2328099
    destination:
    Mongstad
  61. oid:
    2329449
    origin:
    Hartlepool
    did:
    2327908
    destination:
    Fredrikstad
  62. oid:
    2329449
    origin:
    Hartlepool
    did:
    2327908
    destination:
    Fredrikstad
  63. oid:
    2329449
    origin:
    Hartlepool
    did:
    2330477
    destination:
    Rotterdam
  64. oid:
    2329449
    origin:
    Hartlepool
    did:
    2328315
    destination:
    Lessremman
  65. oid:
    2329449
    origin:
    Hartlepool
    did:
    2328315
    destination:
    Lessremman
  66. oid:
    2329449
    origin:
    Hartlepool
    did:
    2330091
    destination:
    Vlissingen
  67. oid:
    2329449
    origin:
    Hartlepool
    did:
    2450098
    destination:
    Dunkirk
  68. oid:
    2329449
    origin:
    Hartlepool
    did:
    2328012
    destination:
    Rekefjord
  69. oid:
    2329449
    origin:
    Hartlepool
    did:
    2328012
    destination:
    Rekefjord
  70. oid:
    2329449
    origin:
    Hartlepool
    did:
    2328069
    destination:
    Breiviga
  71. oid:
    2329449
    origin:
    Hartlepool
    did:
    2328061
    destination:
    Mekjarvik
  72. oid:
    2329449
    origin:
    Hartlepool
    did:
    2452200
    destination:
    Skipavik-Gulen

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.

AI agent? Read the complete navigation and programming guide.