Best use for travel intelligence
For travel decisions, ferry and pier data is strongest when it shows the real fragility of an island move: which pier matters, where the last boat risk sits, and what should stay refundable.
Data cluster
Pier, ferry, marine-department, port, OSM, and operator-context layers for Thai island transfers and last-boat risk.
For travel decisions, ferry and pier data is strongest when it shows the real fragility of an island move: which pier matters, where the last boat risk sits, and what should stay refundable.
6 of 8 sources look official or agency-backed.
5 sources expose API, feed, CKAN/DataStore, JSON, XML, or similar machine-readable access.
2 sources have live, hourly, event-driven, warning, or frequent update language.
Keep official pier identity, map geometry, operator schedule context, and commercial booking or fare feeds separate so weather and transfer risk do not get buried inside one generic ferry record.
Last checked: 2026-05-11.
Source confidence: This cluster is strongest when several sources describe the same traveler problem from different angles: official context, machine-readable feeds, and slower fallback documentation.
These pages turn the dataset layer into a stay, route, or transfer call.
Commercial ferry and boat-transfer context for operator discovery, route families, booking windows, last-boat risk, and cancellation-policy patterns across Thai island and coastal transfers. Useful for traveler booking reality, not an official national ferry timetable feed.
Commercial booking/search pages and operator schedule context; API or bulk access requires partnership or explicit permission TransportMarine Department Single Window berth-status surface exposing public port selectors and visible ship-visit rows such as arrival or departure indicators, ETB times, and vessel names. Useful as berth and movement evidence for coastal and ferry-sensitive planning, not as ferry schedule, seat, or ticket truth.
Official public berth-status and ship-visit surface TransportMarine Department berth, pier, port, terminal, navigation, and service-information context for Thai river, gulf, coastal, and border-water piers. The public berth registry is useful for official passenger-pier support, berth depth, berth length, and route-family context. It is not a verified national realtime ferry schedule, closure, queue, or seat-inventory API.
Official public Marine Department dataset plus site pages; berth registry JSON/CSV is publicly reachable TransportStatic stop, station, pier, connected-mode, and park-and-ride context; pair with GTFS stops and OSM for station pages.
Compressed text downloads and GTFS-related static data TransportFree pier and ferry map layer for amenity=ferry_terminal, man_made=pier, route=ferry, landings, and nearby boat-access context. Useful for coordinates, nearby transfers, and fallback mapping, not official route confirmation.
OpenStreetMap Overpass API and ODbL geospatial data TransportOfficial Port Authority catalog layer for Bangkok Port, Laem Chabang, and other PAT-managed port statistics and reference datasets. Useful for major-port identity, cargo, and logistics context; low direct traveler value and not an island-ferry schedule, ticket, or berth-queue feed.
CKAN-style PAT Data Catalog with CSV/XLS/RDF/JPEG resources for port statistics, organization data, and official port datasets TransportPort Authority of Thailand context for Bangkok Port, Laem Chabang, Chiang Saen, Chiang Khong, Ranong, and related port operations. Useful for major-port identity and shipping context, not a public island-ferry timetable feed.
Official public website, port profiles, contact pages, and annual-report resources Weather, environment, and disastersPublic Gulf of Thailand and Andaman / Malacca shipping forecast text for wind, wave, thunder, and heavy-rain marine context. Use as sea-state burden and ferry-risk evidence, not operator closure, ticket, or seat truth.
Public webpage