Resources
Six Lost Hours a Day: The Depot Math Behind Waiting Inside the Zone
A depot run can take a robotaxi out of service for about two hours, up to three times a day, according to an infrastructure founder interviewed on The Road to Autonomy. The hours are lost on the drive to the edge of the city. The fix is a permitted lot inside the zone, and owners already have those.
By Greg Bessoni, Founder and CEO, XoomPark ·
A robotaxi driving to its depot is not earning. Count the hours.
An infrastructure founder told The Road to Autonomy that under today’s depot model a vehicle can be taken out of service for roughly two hours per servicing run, up to three times a day, as many as six lost hours.1 A good share of those hours fall in the middle of the day, when the vehicle could be carrying rides. That is lost utilization, in his words, and it is the number this post is about.
Where the hours go
Depots sit at the edge. The podcast’s field report from Dallas found two depots at opposite ends of the service area: a temporary hub in an industrial sector west of downtown, running on portable charging, and a permanent hub in East Dallas, several miles from downtown, with about 36 fast chargers.2 By October the permanent site was reported grid-tied and active with 40 fast-charging points.3 Land, power and neighbors push a depot to where those things are cheap and quiet, which is rarely where the riders are.
So each run is a drive out, a wait, a charge or a clean, and a drive back. The two hours is the founder’s figure for the whole loop, and it covers charging and reset, not only the driving. By our reading of the published service map, the busiest part of the Dallas zone sits six to nine miles from either depot. That is our estimate from a map, not a measurement.
Here is the arithmetic, with the assumptions in the open. Take an 18-hour operating day. If a vehicle averages one and a half paid trips an hour, six lost hours is nine trips, a third of the day. If it averages one trip an hour, it is six trips. Fleet sizes and trips per vehicle are not published, so treat this as a shape, not a figure. The shape is the point: the loss scales with distance to the depot and with how many times a day the vehicle has to make the trip.
The fix is where, not what
The founder’s answer is to put charging and reset capacity inside the operating zone, so the downtime becomes micro top-ups and micro cleans during natural lulls. He thinks that removes at least two of the three out-of-service pulls a day.1 Whether it is two or one, the direction is the same. A ten-minute top-up on a lot three blocks from the rides costs the fleet ten minutes. The same electricity at the edge of the city costs the drive there and back.
This is the oldest idea in fleet work. Taxis had stands. Airports built holding lots so drivers could wait near the terminal instead of circling. Buses have layover bays at the end of the line. The vehicle is new. The rule is not: wait near the people you serve. We wrote about the passenger side of that rule in The Robotaxi Should Be Waiting When the Train Arrives.
We use your unused stalls, never fill them so a retail customer can’t charge, and never make you go over your monthly peak.
The lot is already permitted
The part of the interview that matters most to a property owner is the permitting path. The founder says his company can deploy within eight to twelve weeks using a conditional-use authorization on land already permitted for automotive or electric vehicle charging use, and that a centralized depot can take a very long time to permit.1 His partners are charge point operators that already run fast charging in city centers, and owners of parking lots. The equipment is designed to fold up and move on a flatbed within days.1
Read that as an owner. Your lot’s existing use is the asset. A parking lot already parks cars. A charging site already charges them. The question a city asks about a fleet is whether the new activity changes that use: a service bay, 24-hour operations in a zone that limits hours, a charger installation that needs more power. When it does not, the path is a conditional use on a permitted lot, measured in weeks. When it does, it is a depot, measured in seasons. That gap is why a modest lot in the right place can be worth more to a fleet than a large one at the edge. We made the same argument from the owner’s side in What If Your Parking Could Earn Until You Needed It Back?.
What we do not know
- Fleet sizes, trips per vehicle per hour and real depot cycle times are not published. The six hours is one founder’s figure for today’s model, not a measurement across fleets.
- Depot layouts differ. One Dallas site was temporary with portable charging; the other was built for charging and security with no visible maintenance bays, which the field report reads as a sign a third site may follow.2
- Whether operators keep building edge depots or add in-zone stops is the thing to watch. The field reports are the only public record of either so far.
- Our six-to-nine-mile estimate comes from a published service map and two neighborhood-level depot descriptions. The reports do not give addresses.
The founder is building pods. We are building the network of lots, garages and charging sites the pods and the fleets both need, and the written record that says what each site allows. Different products, the same arithmetic. Reported depot locations now show on our search map with their sources, so you can see the edge for yourself.
Own a lot inside a robotaxi zone? List your property free. Tell us its hours, its access and whether charging is already on site.
Sources
- The Road to Autonomy, transcript: Building, Deploying and Scaling Autonomous Robotaxi Infrastructure (interview with Aseon Labs co-founder and CEO George Kalligeros)
- The Road to Autonomy, Dallas field report, Mar 30, 2026 (field verified)
- The Road to Autonomy, Dallas depot and active operations field report, Oct 12, 2026
Sources are public. XoomPark isn't affiliated with the companies referenced in this post.
About the author
Greg Bessoni is the founder and ceo, xoompark. He writes about fleet operations, curb logistics and AV infrastructure.