Skip to content
Axons Mobility

Operations

How to Increase Revenue per Vehicle in Scooter Sharing

By Axons Mobility Team · · 8 min read

The short answer

Revenue per vehicle in scooter sharing is trips per vehicle per day multiplied by the net revenue each trip keeps. To raise it, keep more vehicles rideable, place them where riders are, price for demand with surge, off-peak prices and daily caps, sell passes, aim promos at new and lapsed riders with budget caps, and stop revenue leaking through failed payments and refunds. Measure the result as contribution per vehicle per day, after costs, so you grow profit rather than just ride counts.

To increase revenue per vehicle in scooter sharing, raise the number of paid trips each vehicle makes per day and the net revenue each trip keeps. In practice that means keeping more vehicles rideable, putting them where riders are, pricing for demand, selling passes, aiming promos with care and stopping the money that leaks out through failed payments and refunds.

Revenue per vehicle is the heart of micromobility unit economics, but it only tells half the story. A change that adds trips while adding even more cost makes you poorer. This guide starts with how to measure it properly, then walks through eight levers, and ends with how to tell which of them is working.

How do you measure revenue per vehicle?

Everything below uses one building block: the vehicle-day. One vehicle on the street for one day is one vehicle-day. Fifty vehicles on the street for a week is 350 vehicle-days. Dividing by vehicle-days lets you compare weeks, zones and fleets of different sizes fairly.

MetricFormulaWhat it tells you
Rideable rateVehicle-days riders could rent ÷ (vehicles you own × days in the period)How much of the fleet you pay for is able to earn
UtilisationMinutes in paid rides ÷ minutes vehicles were available to ridersHow busy the rideable vehicles are
Trips per vehicle per dayPaid trips ÷ vehicle-daysWhether vehicles are in the right places at the right price
Net revenue per trip(Ride revenue − discounts − refunds) ÷ paid tripsHow much each trip really keeps
Revenue per vehicle per dayNet revenue ÷ vehicle-days (or trips per vehicle per day × net revenue per trip)The headline number
Cost per vehicle per day(Charging, repairs and parts, field staff, payment fees, software, insurance and fees) ÷ vehicle-daysWhat each vehicle needs to earn to break even
Contribution per vehicle per dayRevenue per vehicle per day − cost per vehicle per dayWhether a vehicle, zone or change is worth it

Three rules keep these numbers honest:

  • Fix your definitions. Decide once whether pass sales count when they are sold or spread across the trips they cover, and whether a vehicle in the workshop counts as a vehicle-day. Changing the rule later makes trends meaningless.
  • Do not borrow benchmarks. Results depend on the city, season, vehicle and fleet size. We do not quote industry averages here, because a number from someone else’s streets is a poor target. Compare your own weeks, zones and vehicle models instead.
  • Wait for enough data. A few days of trips from a handful of vehicles can swing wildly. The Unit Economics page in the Axons Mobility console shows what one vehicle earns and spends per day, and it shows nothing rather than a number built on too little data.

If you are still building your cost lines, our guide to the cost of starting a scooter sharing business lists every bucket.

1. Keep more vehicles rideable

A vehicle that is flat, broken or offline earns nothing, while its costs keep running. Raising the rideable rate is often the cheapest revenue you can find, because the demand already exists.

  • Fix the right vehicles first. Fleet Intelligence in the Axons Mobility console gives every vehicle a 100-point health score covering wear, electronics, usage and service history, so your team can see which vehicles need attention first and go from an alert to a work order in one press.
  • Never wait for parts. A repair that sits for days waiting for a brake cable is a vehicle off the road for days. Keep stock of the parts that fail most. In Axons Mobility work orders, parts come out of stock automatically, and an alert warns you when a part runs low.
  • Set a battery floor. Decide the battery level below which a vehicle goes on the swap list. A ride that dies halfway loses the trip and often causes a refund. Low-battery alerts give your swap team a clear list, and riders can filter the map by minimum battery.
  • Chase offline vehicles. A vehicle that stops reporting may be stolen, flat or broken. Offline alerts help your team reach it before the next day’s demand.

2. Put vehicles where the demand is

The same vehicle can earn very different amounts one street apart. Compare where rides start with where vehicles sit unused, then move the idle ones to where riders are, at the times they are there.

The live map in the Axons Mobility operator console has a heatmap layer, and Analytics shows utilisation and demand with a plain explanation of how each number was counted. Your team decides the moves; the data shows where to look. Zones help too:

  • Parking zones in busy places mean trips end where the next rider will be.
  • No-go and speed limit zones keep vehicles out of places that bring complaints or damage.
  • Charging zones bring vehicles back to where they can be charged.

Moving vehicles costs staff time, so check that the extra trips earn more than the move costs. That is exactly what contribution per vehicle per day shows.

3. Price for demand, not just for time

One price all day leaves money on the table at busy times and leaves vehicles idle at quiet ones. Axons Mobility lets you charge by time, distance, both, or a flat fare, with taxes and surcharges by region and a live fare preview. Four tools matter most for revenue per vehicle:

  • Surge pricing. A flat surge, or one that follows demand, earns more per trip when there are more riders than vehicles. Keep it modest and watch whether trips fall.
  • Off-peak prices. Pricing windows per fleet let you set a lower price for quiet hours, to turn idle minutes into rides. Check that cheaper rides are new rides, not full-price rides moved to a cheaper hour.
  • Daily caps. A cap on what a rider pays in a day makes long and repeated rides feel safe to take, which can fill hours a vehicle would otherwise sit still.
  • Reservation fees. When a rider holds a vehicle while walking to it, a small fee means the waiting time still earns something.

Change one price at a time, and compare with the same weekdays before the change. Weather and holidays move demand too, so compare like with like.

4. Sell passes and memberships

Passes lower revenue per trip but can raise revenue per vehicle, because regular riders can ride more when each ride feels already paid for. You also get cash up front. Axons Mobility supports day passes, ride packs, minute bundles and memberships, which can be gifted, shared or renewed automatically. The pass applies itself at unlock, so riders have nothing to remember. Judge a pass by revenue per vehicle per day across the fleet, not by the price of a single trip.

5. Aim promos at lapsed riders and new sign-ups

A discount for a rider who would ride anyway simply lowers your revenue. Promos earn their cost when they produce trips that would not happen otherwise. The two groups most worth targeting are new sign-ups who have not taken a first ride and riders who have stopped riding.

Axons Mobility has 11 kinds of promos, such as cashback, fare caps, streak rewards and referrals. You can aim them at new, lapsed, birthday, behaviour-score or low-wallet riders, give each a budget cap, and share them with QR posters or bulk unique codes. Rider Intelligence shows churn risk and revenue at risk, so you can see who is slipping away before they are gone. Give every promo an end date, then compare the trips it produced with what it cost.

6. Make group rides and reservations easy

Friends often ride together. If only one of them has your app, a group ride turns one rider into several paid trips. In the Axons Mobility rider app, a rider can unlock several vehicles at once; each ride is billed separately and the receipts are stacked together.

Reservations win trips from riders who would otherwise give up when the nearest vehicle is taken on the way. You set the hold length and fee, the price stays locked, and a countdown shows walking directions. Keep holds short, so a reserved vehicle is not blocked for long.

7. Cut failed payments and negative balances

A ride that ends unpaid counts as revenue in a report but never reaches your bank. Close the gaps:

  • Bank approval inside the app. When the bank asks the rider to confirm a payment (3-D Secure), it should happen without leaving the app, or the payment is easily abandoned.
  • A second chance when a card fails. Offer another card, the wallet balance or a retry straight away, instead of a dead end.
  • Wallets with auto top-up. A balance that refills itself is ready for the next ride.
  • Deposits held, not charged. A hold protects you without taking the rider’s money.
  • Recover what is owed. Rider Intelligence in Axons Mobility includes negative wallet recovery, so balances that went below zero are followed up rather than forgotten.

8. Prevent the refunds that parking disputes cause

Every refund comes straight off revenue per vehicle, and parking fees are a common cause. Most disputes start with a surprise, so remove it: show riders their parking status, the nearest parking zone and any fee before they end the ride, ask for a parking photo, and send an itemised receipt. Ride Replay lets riders check their own route, and force-stopped rides are billed only until the vehicle stopped moving. When a complaint still arrives, the Axons Mobility support desk can settle it with one-click refund, credit or promo code. Our guide on reducing parking disputes covers this in detail.

How do you know which lever is working?

Judge every change by contribution per vehicle per day. A surge rule that adds revenue but empties a zone, or a rebalancing shift that adds trips but costs more in wages, can look good on one metric and bad on this one.

Revenue Insights in the Axons Mobility console finds suggestions overnight, each with an estimated weekly impact. One press creates the surge rule, pass, campaign or work order, and the result is tracked afterwards. Treat the weekly impact as what it is, an estimate, and compare it with what really happened. A simple weekly routine works well:

  1. Check the rideable rate and clear the oldest open work orders.
  2. Compare trips per vehicle per day by zone and move idle vehicles.
  3. Review net revenue per trip, discounts and refunds.
  4. Make one pricing, pass or promo change, and write down what you expect.
  5. A week later, compare the result with the same weekdays before.

These levers work for scooters, bikes and mopeds alike; our page on shared scooters, bikes and mopeds shows how Axons Mobility supports each. The best way to see your own numbers is on your own streets: Axons Mobility offers a free 15-day trial on your own vehicles, in a private fleet with real riders.

Frequently asked questions

How do you calculate revenue per vehicle per day in scooter sharing?

Divide net ride revenue for a period, after discounts and refunds, by vehicle-days: the number of vehicles on the street on each day, added up across the period. The result equals trips per vehicle per day multiplied by average net revenue per trip, so you can raise it by adding trips, keeping more revenue per trip, or both.

What is a good utilisation rate for shared scooters?

There is no single good number. Utilisation depends on the city, the season, the weather, the vehicle model and how many vehicles you deploy, so a figure from another market is a poor target. Track your own utilisation week by week, and compare areas, vehicle models and times of day within your own fleet.

Does surge pricing increase revenue per scooter?

It can, when more riders want vehicles than you have in an area. It can also lower revenue if riders stop riding. Test surge in one fleet or time window, then compare revenue per vehicle per day with the same weekdays before the change.

How can promo codes increase revenue without losing money?

Aim them at riders who would not ride otherwise, such as new sign-ups who never took a first ride and riders who have stopped riding. Give every promo a budget cap and an end date, then compare the extra trips it produced with what it cost.

Why can revenue per vehicle fall when total trips go up?

Common reasons are deploying more vehicles than demand needs, discounts and passes lowering revenue per trip, more refunds, and payments that fail after the ride. Check trips per vehicle per day and net revenue per trip separately to see which one moved.

Related on Axons Mobility