Decision driving
Transport
Marine Department Berth Status.
Marine 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.
Public
Official public berth-status and ship-visit surface
Free public web access
Operational / event-driven on the public surface
2026-05-11
Public web, file, catalog, or documented endpoint access with no paid gate implied in the source profile.
source health, observation ingest, signal compute, decision compute
pier name, route family, operator, lat/lon, address, first or last boat context where available, booking window, cancellation rule, weather sensitivity, port or pier owner, connected transfer, source ID
High for official context; validate endpoint availability before automation.
Runtime truth
Decision driving
Yes
route, station, airport, pier, destination, terminal, island
official_berth_status_surface_score
where_to_go_today, route_check, ferry_check
Feeds active observations and signals that currently influence traveler-facing decisions.
How this helps travel recommendations
Turns ferry planning into source-backed decisions about which pier matters, how fragile an island transfer is, where the last-boat risk sits, what should stay refundable, and whether a route needs a mainland or airport backup.
Endpoint and API notes
Marine 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.
Open the source endpoint or documentation. Return to the Thailand data atlas.
Developer reference
Use Marine Department and PAT pages for official pier and port context, OSM for landing and pier geometry, Namtang static pier/station layers where useful, and commercial operator or booking feeds only when you need live schedules, fares, or availability.
Refresh weekly or when the catalog metadata changes; many agency catalogs update irregularly.
Turns ferry planning into source-backed decisions about which pier matters, how fragile an island transfer is, where the last-boat risk sits, what should stay refundable, and whether a route needs a mainland or airport backup.
Marine Department, PAT, OSM piers, Namtang stop and pier downloads, official operator pages, and commercial ferry booking/search surfaces where authorized.
Example request
# Source landing/download page; inspect linked resources before automation.
curl -L "https://nsw.md.go.th/msberthmanagement/PublicBerthStatus.aspx"Failure modes
- There is no single public national Thailand ferry timetable API.
- Pier identity, operator schedule, and weather reality often come from different systems.
- Consumer booking sites can show routes or timings that need operator or marine confirmation.
- Last-boat timing, cancellation policy, and same-day sea-state risk can change faster than static pier pages.
Last checked and source confidence
Last checked: 2026-05-11.
Source confidence: Treat this profile as strongest for the exact role named above. It is weaker when the source is stretched into live availability, legal proof, or traveler-fit decisions it does not directly prove.