Taxi, ride-hailing, airports, and last-mile confidence
Thailand taxi intelligence only works when legal registry, fares, airport rules, GPS analytics, stands, complaints, and ride-hailing stay separate. Use DLT for legal vehicle, driver-license, operator-license, Taxi OK/VIP, GPS-linked oversight, complaints, and ride-hailing certification; OTP/MOT for aggregate taxi GPS trip analytics and pickup/dropoff zones; AOT for airport taxi counters, surcharge, baggage, Grab, CABB, EV taxi, and limousine rules; OSM and licensed POI APIs for stands and pickup points; and platform data only through authorized ride-hailing or fleet integrations.
Current trip check
The page below is still useful without JavaScript. When current checks are available, this panel points you to the Today, comparison, and route pages that matter before committing.
Showing static taxi planning links until the latest check is available.
Use this order when legality, fare, airport, stand, complaint, and ride-hailing sources disagree.
| Rank | Source layer |
|---|---|
| 1 | DLT and MOT/OTP for legal registry, official statistics, Taxi OK/VIP, complaint data, and aggregate taxi GPS analytics. |
| 2 | AOT airport pages for Suvarnabhumi and Don Mueang taxi counters, pickup points, surcharge, baggage, and airport ride-service rules. |
| 3 | DLT-linked public guidance for ride-hailing legality, driver/license requirements, complaint channels, and regulated app context. |
| 4 | OSM, Google Places, Longdo, NOSTRA, and airport/operator pages for taxi stands, pickup points, opening context, and geospatial enrichment. |
| 5 | Ride-hailing and private-fleet surfaces only where a user session, partner API, or explicit operator permission makes fare, ETA, dispatch, or booking data lawful to use. |
This keeps legal registry, GPS analytics, airport counters, motorcycle-taxi wins, app pickups, and private dispatch from collapsing into one misleading record.
| Rule | Meaning |
|---|---|
| 1 | DLT registration or regulated operator context is strongest for taxi legality and vehicle-category identity. |
| 2 | A taxi fare rule is not the same thing as a ride-hailing quote, airport surcharge, or negotiated long-distance fare. |
| 3 | OTP/MOT GPS analytics are aggregate demand signals, not live vehicle positions or raw trip records. |
| 4 | A taxi stand, airport queue counter, motorcycle-taxi win, and app pickup point need separate place types and confidence logic. |
| 5 | Ride-hailing app data shown to a passenger is not automatically an ingestible public API. |
| 6 | Motorcycle taxis, metered taxis, airport limousines, CABB-style premium taxis, tuk-tuks, and app hire-cars should never collapse into one service class. |
Each layer answers a different question. A legal taxi registry is not a live nearby-taxi feed; an airport taxi rule is not a ride-hailing quote; a stand map is not a complaint record; a GPS heatmap is not a driver assignment API.
DLT vehicle counts, driver-license statistics, operator-license data, Taxi OK/VIP records, and app-certification guidance explain what is legal and what is only an app-visible service.
public data is mostly aggregate demand heatmapsOTP/MOT taxi GPS analytics give monthly trip counts, average distance, speed, total time, and top pickup/dropoff zones without exposing live vehicles.
not realtime fare calculatorsBangkok fare rules, airport surcharges, baggage rules, toll policy, and airport-specific pickup points need their own source layer separate from ride-hailing pricing.
airport fare logic differs from street-hail app legality checksRide-hailing apps expose fare, ETA, vehicle, and driver context to the rider, but legality and app approval come from DLT while live dispatch data remains private or partner-only.
no broad public dispatch API nearby stand searchTaxi ranks, airport queues, motorcycle-taxi wins, and pickup points are best modeled from OSM, airport pages, Bangkok motorcycle datasets, and licensed POI enrichment.
stands are under-mapped safety trend analysisDLT 1584 complaint datasets, DLT GPS complaint channels, and airport/operator guidance provide service-quality and passenger-protection context.
public files are historical/aggregateThese pages turn the source model into usable taxi-fare, airport-taxi, ride-hailing, motorcycle-taxi, complaint, and taxi-stand guidance.
Bangkok metered-taxi fare logic, traffic-jam charging, airport surcharge separation, toll policy, baggage caveats, and why app quotes are not the same thing.
fare calculators / tourist expectation setting airport taxiSuvarnabhumi public taxi, queue-ticket area, 24-hour service, surcharge, toll responsibility, baggage rules, short-distance taxis, Grab pickup, CABB, EV taxi, and AOT limousine context.
airport arrivals / public taxi queue airport taxiDon Mueang taxi pickup points, 24-hour service, terminal-door rules, app-based pickup context, special taxi options, and onward transport caveats.
airport arrivals / terminal pickup guidance ride-hailing guideThailand ride-hailing legality, DLT-certified-app caveats, what the rider sees in-app, and why live ETA, fare, driver, and supply data are private unless a partner integration exists.
app comparisons / tourist ride choices motorcycle taxiBangkok motorcycle-taxi wins, driver counts, app-certification context, OSM stand mapping, and when a win is more realistic than a metered car.
last-mile travel / soi access complaint and safetyDLT 1584 complaint data, public complaint channels, taxi and motorcycle-taxi complaint context, and why complaint totals are better for trend analysis than realtime service monitoring.
consumer protection / trust scoring stand and pickup searchA taxi-stand and pickup-point model using OSM, airport pages, Google Places, Longdo, NOSTRA, and manual confidence scoring for ranks, wins, and app pickup zones.
nearby stand search / airport and mall pickup pointsUse DLT for legal vehicle, driver-license, operator-license, Taxi OK/VIP, GPS-linked oversight, complaints, and ride-hailing certification; OTP/MOT for aggregate taxi GPS trip analytics and pickup/dropoff zones; AOT for airport taxi counters, surcharge, baggage, Grab, CABB, EV taxi, and limousine rules; OSM and licensed POI APIs for stands and pickup points; and platform data only through authorized ride-hailing or fleet integrations.