Cash is hard to reconcile
A busy day can end with fare collection spread across conductors, vehicles and handwritten records.
For Punjab bus operators
Sell app tickets, check them on board, and see the day by route and vehicle.
Tresta Go brings the passenger ticket, conductor check and operator view into one controlled pilot—without pretending your operation changes overnight.
The operating problem
You should not have to wait until cash and paper come back to know what happened.
Sold does not mean checked
Without a recorded on-board check, it is difficult to compare issued tickets with passengers actually carried.
Route visibility arrives late
Owners need a practical view of ticket activity by route and vehicle, not another pile of paperwork.
One practical loop
From a passenger ticket to an operator record
- 01
Passenger buys
A passenger chooses and activates a ticket in Tresta Go.
- 02
Conductor checks
The conductor scans or enters the ticket on an Android phone.
- 03
Check is recorded
The result is recorded once the server confirms it.
- 04
Operator reviews
Ticket and checking activity is grouped by route, run and vehicle.
The actual product
Three screens, one accountable journey
These are presentation versions of the real Tresta Go passenger ticket, checker and operator insights screens—not stock phone images.
Passenger
Single ride
Valid ticket
Sirhind → Fatehgarh Sahib · TG-D3MO-2410
Remaining
00:42:18
Example screen. Not valid for travel.
Conductor
Ticket checker
VALID
Recorded just now · cannot be accepted again
TG-D3MO-2410 · Single ride
Operator
Operations / Insights
Punjab Roadways Partner
Ticket value
₹18,460
Verified
284
In service
3
Revenue by route
Vehicle feed
PB-23-AB-1842
Sirhind → Fatehgarh Sahib
7 min late · simulated
What you provide
- Your route list and stopping points
- Your active vehicle list and registrations
- One Android phone for each conductor using the checker
- One named contact who can make day-to-day pilot decisions
What Tresta Go handles
- Passenger app and ticket screens
- Payment setup agreed for the pilot
- Operator reporting and ticket-check records
- Team onboarding, training and pilot support
Controlled pilot
Agree the terms before anything launches.
Duration
Pilot duration agreed with the operator before launch.
Cost
Pilot pricing and payment terms agreed in writing before launch.
Success
Measures agreed together—such as ticket activity, completed checks and usable route reporting.
Exit
Exit terms, data handling and any close-down steps agreed before the pilot starts. No commitment is created by booking a demo.
Questions operators ask first
What if there is no mobile signal on the route?
The current checker needs a server response. If there is no signal, it shows UNABLE TO VERIFY, does not accept the ticket and does not mark it used. Offline checking is not currently offered.
What if a passenger has no smartphone?
Tresta Go does not replace every fare channel in a pilot. The operator can continue its agreed existing process for passengers who cannot use app ticketing.
What happens to cash fares?
Cash collection remains under the operator’s existing process unless different pilot terms are agreed. Tresta Go reporting covers transactions and checks recorded in Tresta Go; it does not claim to reconcile cash it never recorded.
Who owns the data?
Data access, handling and exit arrangements are agreed with the operator before launch. The app restricts operational views by role; final commercial and data terms belong in the pilot agreement.
How long does setup take?
It depends on the route and vehicle information supplied, staff availability, and agreed payment setup. We scope the work before committing to a launch date.
Start the conversation
Book a 20-minute operator demo
Tell us enough to prepare a useful conversation around your routes and vehicles. This is an enquiry, not a pilot commitment.
WhatsApp contact is being configured. Use the form and choose WhatsApp as your preferred contact method.