Key takeaways
- Rochester's 100,000-trip milestone is a health-system report, so read it as a reported operating record, not an audited benchmark.
- A trip count shows volume. It does not show how cleanly each delivery was logged, handed off or recovered when something went wrong.
- The reported 50,000-plus staff hours is an estimate. Ask how it was built before you copy it into your own budget.
- Before a fleet grows, check trip logs, hand-off records and uptime data, in that order.
What did Rochester Regional Health report?
In August 2026, Rochester Regional Health said its Moxi robots had passed 100,000 trips at Rochester General and Unity hospitals. Fingerlakes1 reported the milestone on August 21, 2026, and the figure comes from the health system itself, not from an outside audit.
The same report gives the health system's estimate that the robots have saved staff more than 50,000 hours. That number is an estimate. It signals where staff effort went, but it is not a measured line item you can drop into your own budget without checking how it was built.
The short answer is that Rochester has shown sustained, high-volume use across two hospitals. Public reporting does not explain how each trip was logged, how each hand-off was confirmed, or how often the units were out of service.
How do the site figures add up?
The health system reports more than 75,000 deliveries at Rochester General and more than 25,000 at Unity since the robots began operating in 2023. Those two figures together are consistent with the headline total, but both are stated as minimums, so no exact sum is published.
Keep one distinction firm. Diligent Robotics, the company that makes Moxi, said in a November 2024 announcement that its robots had completed over 100,000 autonomous elevator rides across U.S. health systems. That is a vendor-reported company-wide count that measures a different unit. Counting rides and counting hospital trips are not the same exercise, so a fleet-wide vendor total cannot stand in for one hospital's trip log.
What should a trip mean in your logs?
A trip count is only as useful as the definition behind it. Before you read any milestone as a benchmark, find out if a trip is counted one way or as a round trip, whether a failed delivery that gets re-sent counts twice, and if a robot waiting several minutes at an elevator is still on trip.
For your own facility, log each trip with a request time, pickup time, drop-off time, destination, recipient confirmation, and any stop or intervention with its cause. Those fields turn a simple count into a record you can audit, compare across shifts, and show to a vendor when a route underperforms.
Where do staff hand-offs fit?
Much of the value in a hospital robot sits in the hand-off, not the drive. Someone has to load the robot, receive the item, or clear a door. If that step is slow or unrecorded, the trip count can look strong while the labor saving quietly erodes.
- Who confirms receipt, and whether the robot records a name, badge or sign-off
- How long a delivered item waits before someone collects it
- What staff do when a door, elevator or lid fails mid-route
- Does the staff-hour estimate count loading and rerouting time, or only walking time avoided
What uptime questions should you ask first?
Public reporting on the Rochester units does not break down uptime, downtime causes or repair times. That gap matters most before you expand, because a unit that sits idle in a busy window can erase the gain from every trip it completed.
Ask for uptime by unit and by shift, the time to restore service after a fault, if remote triage can clear some faults without a technician visit, and how on-site dispatch is scheduled. Ask what spare unit coverage looks like when a robot goes down during a peak hour. Put those answers in writing before a fleet grows, not after.
How should a fleet grow after a milestone?
Growth works better in steps. A phased deployment with no shutdown lets you add units only after the logs show the first route is stable. Starting with one leased unit gives you a real fault history to judge, rather than a forecast built on a vendor's sales deck.
Service Robot Co. is an OEM-neutral integrator. We select robots across manufacturers, then lease them on a three-year lease with one fixed robot lease payment quoted after a site assessment. We deploy, integrate, train staff and service every unit under our RoboCare service, with go-live support and on-site dispatch under one partner and one number, so the logs, hand-offs and uptime questions above have a single point of accountability.
What can a non-hospital facility manager take from this?
You may never run a hospital, but the same questions apply to a hotel, a senior living campus, a university lab or a warehouse that moves linen or meals. A milestone is a prompt to ask how the number was made.
Read any robot milestone in three steps. Check who reported it, check how the unit of work was defined, and check what the logs say about time spent around the robot, not only time spent moving. A meal tray transport route in a senior living building needs the same discipline as a medication transport robot in a hospital, even though the stakes differ.
Frequently asked questions
Want a robot working for you?
Tell us the job and the site. We will recommend the robot, quote the lease, and keep it serviced.
Sources
Service Robot Co. is not affiliated with, sponsored by, or endorsed by the companies mentioned in this article.
