Help and contact

Support

Email: [email protected]

Include your phone model, Android version, app version (Settings → About) and what you expected versus what happened. Screenshots help. Please do not send precise home addresses or personal travel history.

Closed testing

The app is in closed testing before a wider release. If you want to join, email the address above with the Google account you use on the Play Store. Testers install from the Play testing link; production is untouched.

Frequently asked

Why does the app need a data download?

The timetable is a 27 MB compressed SQLite file containing 60,891 stops, 6,784 KSRTC route patterns and 20,533 daily departures. Keeping it on the phone makes search, stop boards and timetables work without a signal. It is downloaded once and updated in the background.

Why is no live bus shown on my route?

Live coverage is partial: the public feed exposes roughly 2,000 of the 6,784 KSRTC patterns at any moment. The app shows the scheduled timetable in that case and never invents an ETA. A bus that stops reporting is shown as stale, then removed.

Why does a route code look unfamiliar?

Codes such as K6722 belong to the data source, not to KSRTC's official numbering. The app labels them as source codes and does not claim they are official.

How do I delete my data?

There is no account. Clear the app's storage in Android Settings or uninstall the app. See data deletion for details.

Updates

The app checks Google Play for updates. Flexible updates download in the background and install themselves when ready; a critical update uses Play's immediate flow.

Data corrections

The upstream data is maintained by busz/Chalo/reclaim.city. Send the stop, route and what looks wrong; we can pass it upstream, but we cannot guarantee a correction.

Privacy and terms

See the privacy policy and terms of service.