Sarathi ಸಾರಥಿ
How a clock is labelled

If it is not live, Sarathi will not call it live.

Every time in the product carries one of five labels. This page is the public meaning of those words. It matches the homepage legend and the usage guide.

Updated 3 September 2026

1. Why every time is labelled

Bengaluru does not yet publish a city-wide authorised realtime feed that Sarathi can connect. Until that exists, a clock from a GTFS snapshot is still useful — and it is still a timetable. The label tells you which of those two things you are looking at.

A label describes Sarathi’s information, not the operator’s promise on the road. Follow boards and staff while travelling.

2. Scheduled

Derived from a published timetable or GTFS schedule — BMTC static GTFS under transit-data/bmtc, or the provisional BMRCL snapshot under transit-data/bmrcl. It is not a GPS prediction and it is not called live.

On the Android planner, the Koramangala → Mayohall example shows a Scheduled pill next to the depart / arrive clocks. That is a timetable window, not a vehicle ping.

3. Typical

An estimate from known service patterns or historical assumptions, used when a clock-face timetable is missing or too thin. Treat it as a habit, not a promise.

4. Cached

Information Sarathi already fetched. It may be older than the current service state. Re-plan if the street has moved on.

5. Live

Shown only when a configured, authorised and sufficiently fresh realtime source is actually connected. Even then the feed can be delayed. Sarathi does not currently show Live city-wide for Bengaluru.

6. Unavailable

Sarathi does not have enough trustworthy information for that field, so the field stays blank rather than guessing.

7. What this page does not claim

  • No fare amounts. Confirm the fare with the operator.
  • No official BMTC or BMRCL partnership. See data sources.
  • No Play Store listing. See launch status.

Publisher: AUMLayer Cloud Labs LLP · [email protected] · +91 81510 39365 · aumlayer.com