Transport

Transport Co. / BKS timetable resources.

Official intercity-bus booking/search surface used for destination-selector and route-search support. Useful for proving official route-search presence and overland direction context, but brittle for detailed daily departures unless a stable documented endpoint is available.

Restricted Public booking/search HTML surface and internal selector JSON Free public for human lookup; use low-frequency automation and do not treat it as booking inventory Operational search surface; validate daily or on route updates Open source
Runtime role

Decision driving

Access class

Restricted

Access type

Public booking/search HTML surface and internal selector JSON

Free status

Free public for human lookup; use low-frequency automation and do not treat it as booking inventory

Cadence

Operational search surface; validate daily or on route updates

Last verified

2026-05-11

Access class note

Exists and matters, but direct operational access is limited to authorized users or agencies.

Used in layers

source health, observation ingest, signal compute, decision compute

Useful fields

agency, route_id, stop_id, stop name, station type, lat/lon, trip_id, stop_times, route shape, fare, operator, terminal owner, timetable, service days, source license

Reliability rating

High for official context; validate endpoint availability before automation.

Runtime truth

Runtime role

Decision driving

Production ready

Yes

Entity scope

route, station, airport, pier, destination, terminal, bus_terminal

Observation scope

official_intercity_bus_search_support_score

Decision scope

where_to_go_today, where_to_stay, route_check

Runtime note

Feeds active observations and signals that currently influence traveler-facing decisions.

How this helps travel recommendations

Turns bus travel from vague advice into station, route, timetable, terminal, and confidence logic for Bangkok pivots, intercity routes, and lower-cost overland itineraries.

Endpoint and API notes

Official intercity-bus booking/search surface used for destination-selector and route-search support. Useful for proving official route-search presence and overland direction context, but brittle for detailed daily departures unless a stable documented endpoint is available.

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

Developer reference

Best endpoint

Use Namtang GTFS as the route/stop spine, MOT passenger bus terminals as the official terminal master, BKS timetable/facility resources for intercity context, and OSM/Transitland as validation layers.

Recommended refresh

Refresh every 15-60 minutes, with caching and backoff when the upstream fails.

Travel scoring role

Turns bus travel from vague advice into station, route, timetable, terminal, and confidence logic for Bangkok pivots, intercity routes, and lower-cost overland itineraries.

Comparable / backup source

MOT, DLT, Namtang/OTP, Transport Co./BKS, BMTA, Thai Smile Bus, OpenStreetMap/Overpass, Transitland, Mobility Database, and official operator pages.

Example request

# Verify the documented bus endpoint before production use.
curl -L "https://tcl99web.transport.co.th/" -H "Accept: application/json"

Failure modes

  • Static GTFS does not mean realtime vehicle positions.
  • App-visible realtime is not automatically a public ingest API.
  • Station coordinates and X/Y labels need validation.
  • Intercity timetable pages can be brittle without documented JSON APIs.
  • Commercial booking inventory usually requires partner access.

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.