DRIVER GUIDE

How to calculate rideshare net income per hour

The fare shown on an offer is only the starting point. A useful estimate includes expenses and the real amount of time the trip will take from your shift.

For a rideshare driver, gross fare and net income are different numbers. A trip can look attractive on the offer screen but become less valuable once you include pickup distance, energy cost, traffic, and where the trip leaves you after drop-off.

A simple net income formula

Estimated net income = offer amount − trip-related operating cost

This is not a tax calculation. It is a quick operating estimate that can help you compare one opportunity with another. Your own method can include more or fewer costs, but it should stay consistent from trip to trip.

What to include in operating cost

  • Fuel or charging: estimate the energy used for the trip and, if relevant to your strategy, the pickup portion.
  • Vehicle wear and maintenance: many drivers reserve a per-kilometre or per-mile amount for tires, service, depreciation, and repairs.
  • Platform and payment effects: use the amount actually displayed to you, and do not assume a promotional fare repeats.
  • Other fixed costs: insurance, financing, and phone costs matter to shift profitability, even if you do not assign them to every individual trip.

Then compare time, not only money

Estimated net hourly pace = estimated net income ÷ estimated total trip time × 60

Total trip time is usually more useful than passenger time alone. It may include pickup, the ride itself, expected traffic, and the time you reasonably need to return to a preferred work area. A higher fare can still produce a weak hourly pace if it takes a long time or creates a long empty return.

Use a consistent pre-accept checklist

  1. What is the displayed offer amount?
  2. How long is pickup plus trip time likely to take?
  3. What is the estimated energy and vehicle cost?
  4. Where will the trip leave you?
  5. What is the resulting estimated net hourly pace?

The aim is not to predict the future perfectly. It is to make the comparison more consistent before you commit.

Put the framework in your pocket

Tomato Drive keeps cost assumptions, operating zones, and trip review in one driver-first workflow.

Get Tomato Drive ↗