To see how cab fares vary on your own route, log every ride on that route for two weeks: date, time slot, distance, fare and whether the fare looked raised. Ten rides is enough to find your average, your highest fare and the time slot that costs least. The sample log below is made up, but the method works on your real rides.
What should I record for each ride?
- Date and day of the week.
- Time slot: morning 8 to 10, midday 11 to 16, evening 18 to 20, or your own.
- Distance in km, as shown on the trip receipt.
- Fare paid, including any extra charge shown on the receipt.
- A surge flag: Yes if the app showed a higher price or a peak note, No if not.
Keep the same pickup and drop-off every time. If the route changes, the comparison stops being fair. A phone note works, and so does a spreadsheet.
What does a made-up 10-ride log look like?
| Ride | Day and time | Slot | Fare | Surge |
|---|---|---|---|---|
| 1 | Mon 09:00 | Morning | ₹310 | Yes |
| 2 | Mon 19:00 | Evening | ₹360 | Yes |
| 3 | Tue 08:00 | Morning | ₹250 | No |
| 4 | Tue 14:00 | Midday | ₹190 | No |
| 5 | Wed 09:00 | Morning | ₹290 | Yes |
| 6 | Wed 15:30 | Midday | ₹210 | No |
| 7 | Thu 19:00 | Evening | ₹340 | Yes |
| 8 | Fri 11:00 | Midday | ₹180 | No |
| 9 | Sat 09:30 | Morning | ₹270 | No |
| 10 | Sat 14:00 | Midday | ₹200 | No |
Imagine the distance was close to 12 km on every ride, so the difference is the price and not the route.
How do I work out the average, highest and cheapest slot?
Put fares in D2 to D11 and the slot in C2 to C11. Then:
- Average fare: =AVERAGE($D$2:$D$11) gives ₹260 here (₹2,600 over 10 rides).
- Highest: =MAX($D$2:$D$11) gives ₹360, the Monday evening ride.
- Cheapest: =MIN($D$2:$D$11) gives ₹180, the Friday late-morning ride.
- Average for one slot: =AVERAGEIFS($D$2:$D$11, $C$2:$C$11, "Evening") gives ₹350.
The same formula gives ₹280 for the morning (4 rides) and ₹195 for midday (4 rides). Rides flagged as surge averaged ₹325, against about ₹217 for the others. The top fare is exactly twice the lowest.
What do I do with the result?
If you can move a trip, you now know by how much it is worth moving. In this sample, leaving at midday instead of in the evening saves about ₹155 a ride on average (₹350 - ₹195). If you cannot move it, the log still tells you what to budget for that trip, which is better than guessing from the cheapest ride you remember.
A simple chart idea
Draw one bar for each slot, with the average fare as its height. Plot the surge rides as a different colour. In two minutes you can see whether evening really is your expensive slot. A sheet can draw this from the slot and fare columns.
You can also divide each fare by its distance to get the rupees per km, which is useful if your route changes slightly between rides. In a sheet, with fare in D2 and distance in F2, use =D2/F2 and fill down. Compare slots on that figure when the distances differ by more than a kilometre or so. If the per-km figure stays within a narrow band while the total varies, the difference is mostly the route; if it swings, the price itself is moving.
Can a tracker do the logging for me?
Card or UPI rides arrive in a bank statement as a fare and a date, but with no time slot or surge flag, so the interesting part of this log still comes from you. SpendixAI can import the statement for the fare and date, and you can keep the slot and surge columns in a sheet beside it. For a quick two-week experiment, a simple sheet is just as good.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


