Revenue Per Vehicle Per Day: The Number That Decides Everything

Every fleet decision you will ever make, buying more vehicles, changing your unlock fee, hiring a rebalancer, expanding to a new zone, comes down to one number: revenue per vehicle per day. Written RPVD, it is the daily earnings of the average vehicle in your fleet, compressing utilization, ride volume, and pricing into a single figure you hold against your daily cost per vehicle. If RPVD clears your cost stack, every vehicle you add prints margin. If it does not, every vehicle multiplies the loss. This lesson shows you how to calculate RPVD, what healthy ranges look like across markets and seasons, and the three levers that actually move it.

What RPVD is, and why it beats every other metric

RPVD is deceptively simple: it is total daily revenue divided by the number of vehicles you have deployed. A 40-vehicle fleet that pulls in $640 on a given day is running an RPVD of $16.

RPVD sits at the top of the stack because no other metric can hide behind it. Utilization can look healthy while margins bleed. Ride counts can climb while your average fare quietly collapses under promo codes. RPVD catches all of it, because it is revenue and it is per vehicle: the number you compare directly against your cost to keep one vehicle on the street for a day, which is the only comparison that tells you whether the business works.

How to calculate it

RPVD is the product of two things you already track: how often each vehicle rides, and how much each ride earns.

Two layers sit between that gross number and what reaches your bank account, and you should keep them separate rather than blending them into one adjusted figure:

• Your platform fee. On the Managed plan, Levy quotes its fee as 20% of GMV (gross rider payments before taxes, government fees, refunds, and tips), and at 100 to 249 active vehicles on an annual or approved term it drops to 15% of GMV. The nuance that matters for your payout: the partner share is not taken off gross. It is calculated on net revenue after Stripe processing (2.6% + $0.20 per transaction), with processing costs shared proportionally, and that share defaults to 80% of the net. So plan on keeping roughly 80% of net revenue after processing, not a straight 80% of your gross RPVD, and confirm the exact split in your agreement. On the Software-Only plan (100 to 249 vehicles, in-house operations, annual commitment), you pay a flat $14 per vehicle per month instead of a percentage.
• Payment processing. Levy's volume pricing is 2.6% + $0.20 per transaction, versus a standard 2.9% + $0.30. Operator and Levy share those processing costs proportionally.

There is no upfront software cost on any plan, and you pay when riders pay. The one floor to remember is the $250 per month platform minimum per operator, credited against your fees: if a month's fees come in under $250, Levy invoices the difference. At a small fleet, clearing that floor is your first RPVD milestone.

Healthy ranges by market and season

There is no universal "good" RPVD. The right benchmark is your own market and season, judged on the trend. The figures below are industry planning ranges that vary widely by market, season, and how hard the fleet is run, so treat them as starting assumptions to model against, not guarantees. Your numbers will differ, so model them in the Fleet Estimator.

A healthy urban scooter fleet often targets 3 to 5 rides per vehicle per day. Pair that with a typical short-hop fare and gross RPVD lands in the rough range of $10 to $22 in season. The spread is wide on purpose, because two inputs swing it hard:

• Market type. Dense urban cores and tourist waterfronts run at the high end. Campus fleets spike around class schedules and empty out on breaks. Suburban and low-density deployments run lower and lean on longer average trips to compensate.
• Season. In warm-weather micromobility markets, summer RPVD can run two to three times winter RPVD on identical hardware. A fleet that looks marginal in January can be your best performer in July. Always annualize before you judge a market, and never size your fleet to a peak-week number.

The three levers that move RPVD

RPVD only has three real inputs: how often a vehicle rides (placement), how much each ride earns (pricing), and how many hours the vehicle is available to ride at all (uptime). Every tactic worth doing pulls one of these three levers.

Placement: put vehicles where the rides are

Placement is the highest-leverage lever because it moves RVD, and RVD is the multiplier on everything. A vehicle earning zero rides in a dead zone drags your fleet-wide RPVD down no matter how good your pricing is.

• Define your service geography with zones. Levy's geofencing lets you configure service areas, parking zones, no-go areas, and speed-limit zones, plus out-of-zone parking rules and parking rewards. Tight, well-chosen zones concentrate vehicles where demand is instead of letting them drift into low-traffic edges.
• Forecast demand before you rebalance. Levy's AI Ops produces demand forecasts predicting rides per H3 hex over 1, 4, or 24 hour horizons, conditioned on weather and events, plus an ROI-ranked rebalance recommender that tells you to move N vehicles from one hex to another by a target time with a projected revenue lift. Use the heat-map view to see where tomorrow morning's demand will cluster and stage vehicles the night before.
• Read the recommendations, then act. AI Ops recommends and forecasts. It does not auto-dispatch or auto-execute moves, and its smallest time bucket is one hour, so treat it as a planning tool for your rebalancing crew, not an autopilot.

Pricing: raise revenue per ride without killing volume

Pricing moves the second input directly. The trap: aggressive discounting can lift ride counts while lowering RPVD, because a rise in RVD gets swamped by a falling average fare. Watch RPVD, not RVD, when you test a price.

Levy supports dynamic pricing, subscriptions, packages, and promotions, so you have room to test the whole fare structure:

• Split the fare into unlock and per-minute, and test them independently. Unlock fees load revenue onto short trips; per-minute rates load it onto long ones. Your ideal split depends on your average ride length.
• Use subscriptions and packages to raise frequency from your best riders without permanently discounting the marginal one. A commuter pass lifts RVD among high-intent users while your walk-up fare protects your average.
• Audit your promos against RPVD. Pull average revenue per ride before and after a promo. If RVD rose 10% but RPVD fell, the promo is buying volume you are paying for. Promotions that pull off-peak demand into your fleet are usually worth it; blanket discounts that cannibalize full-fare rides usually are not.

Uptime: stop paying for vehicles that cannot earn

The third lever is the one operators forget, because it does not show up as a price or a placement decision: it shows up as absence. Every hour a vehicle spends dead on a charger, in a repair queue, or offline is revenue you can never recover. Because deployed RPVD only counts vehicles on the street, this downtime hides unless you track it separately, as availability loss or as an active-fleet RPVD run against your full connected fleet. A vehicle out of service 20% of the time earns 20% below its potential before pricing or placement even enters the picture.

• Monitor vehicle health in real time. GPS, remote lock and unlock, battery monitoring, speed tracking, geofencing, and real-time status are standard, so you can spot a low battery or a stranded vehicle before it costs you a day of rides.
• Cut charging downtime with battery swap. Levy's Battery Swap tooling covers pack state-of-health tracking, swap stations, and a Juicer and Charger marketplace with bounties, so a depleted pack becomes a swap instead of a vehicle parked for hours.
• Close repairs fast with Work Orders. Task management, technician dispatch, parts tracking, and vendor invoicing shorten the time a vehicle sits broken. Pair that with US spare-parts stock (tires and tubes, brake cables and pads, display panels, batteries, fenders, throttle assemblies ship in days, not weeks) and your mean time to repair drops, which lifts effective RPVD across the fleet.

Levy runs 99.8% platform uptime with active monitoring, so the platform is not your bottleneck. The uptime you have to manage is your own: batteries, repairs, and rebalancing labor.

RPVD versus daily cost: the only comparison that matters

Calculating RPVD is half the job. The number means nothing until you hold it against what a vehicle costs you to run for one day. Build your daily cost stack, then compare.

Those numbers are placeholders to show the shape of the stack; fill in your own. The discipline: when RPVD sits comfortably above your loaded daily cost, each vehicle contributes margin and scaling is the right move. When RPVD hovers at or below it, adding vehicles multiplies the loss, and the fix is placement, pricing, or uptime, not more hardware.

Because Levy is a revenue-share model with $0 upfront on the Managed plan, your platform cost mostly scales with revenue rather than sitting as a fixed sunk cost. A percentage-of-GMV fee reduces your fixed-cost risk, but it does not eliminate it, and you should not treat it as risk-free. The $250 per month platform minimum is a floor you pay regardless of volume, so at a small or thin-margin fleet the effective platform cost per vehicle can be higher than the headline percentage suggests. Model the fee after the $250 minimum and after your net payout (what actually lands once processing is taken out), not as a clean 20% haircut on gross. Your fixed daily costs are still mostly the hardware, connectivity, and labor lines, and those are what RPVD has to clear first.

A worked comparison

Take the earlier example: gross RPVD of $16.60, an illustrative daily cost floor of $8, and the Managed 20%-of-GMV fee. The fee is roughly $3.32, which leaves about $13.28 before the fixed cost stack and about $5.28 per vehicle after the $8 floor. Treat that $5.28 as a rough vehicle-level contribution estimate, not profit and not exact net. It is a conservative shorthand that still excludes payment processing, does not account for the $250 per month platform minimum at low volume, and sits before the business-level costs (insurance, permits, storage, marketing, taxes, theft reserve, and your own overhead) that a true profit figure has to carry. Before you trust it, stress it against a downside.

The percentage fee is what makes a soft month survivable: it scales down with your revenue, so a weak week costs you less in platform fees than a fixed per-vehicle license would. It still does not make every vehicle profitable on its own, though. In the off-season row the vehicle loses money before the fee even matters, and the $250 minimum plus your fixed hardware, connectivity, and labor lines have to be covered regardless. Multiply the realistic scenarios across the fleet and the season, weight for your shoulder-month RPVD, and you have your real annual unit economics. Do this before you buy a single additional vehicle. Your numbers will differ, so model them in the Fleet Estimator.

By vehicle type

RPVD ranges shift with the vehicle, because both average fare and daily cost move together. Higher-value vehicles earn more per ride but cost more to amortize and maintain, so a bigger gross RPVD does not automatically mean a bigger contribution. The rough ranges below vary by market and season, so treat them as directional and model your own mix in the Fleet Estimator.

Frequently asked questions

Put your own numbers in

RPVD is the number that decides everything, so model it before you spend on hardware. Plug your city, fleet size, and pricing into the Fleet Estimator to see projected utilization, revenue per vehicle per day, and breakeven, then read the full scooter rental profitability breakdown for the assumptions behind those projections. Get comfortable reading RPVD against your daily cost, and every later decision, from your unlock fee to your next zone, gets easier to make.