Transport

Ferry operator commercial context.

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 Commercial booking/search pages and operator schedule context; API or bulk access requires partnership or explicit permission Public consumer site plus commercial/partner integrations On request / timetable and availability change frequently Open source
Runtime role

Catalog only

Access class

Commercial

Access type

Commercial booking/search pages and operator schedule context; API or bulk access requires partnership or explicit permission

Free status

Public consumer site plus commercial/partner integrations

Cadence

On request / timetable and availability change frequently

Last verified

2026-05-11

Access class note

Usually needs payment, partner approval, or a commercial agreement before production use.

Used in layers

page reference only

Useful fields

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

Reliability rating

High for official context; validate endpoint availability before automation.

Runtime truth

Runtime role

Catalog only

Production ready

Not yet

Entity scope

No runtime entity scope yet.

Observation scope

No live observation ingestion yet.

Decision scope

Not wired into active decisions yet.

Runtime note

Profiled in the atlas and public pages, but not yet connected to live graph computation.

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

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.

Open the source endpoint or documentation. Return to the Thailand data atlas.

Developer reference

Best endpoint

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.

Recommended refresh

Refresh weekly or when the catalog metadata changes; many agency catalogs update irregularly.

Travel scoring role

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.

Comparable / backup source

Marine Department, PAT, OSM piers, Namtang stop and pier downloads, official operator pages, and commercial ferry booking/search surfaces where authorized.

Example request

# Verify the documented ferry endpoint before production use.
curl -L "https://12go.asia/en" -H "Accept: application/json"

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.