Key takeaways
- Rochester's 100,000 trips and 50,000 staff hours are the health system's own reported figures, not an audited result.
- A trip count shows how often a robot moved, not how long each move took or who waited.
- The staff hour figure is an estimate, so test it against your own logged handoffs and timed manual runs.
- Log origin, destination, elevator wait, delay and handoff time from the first day of a pilot.
- Start with one leased unit, review the logs for several weeks, then size a lease from your own site data.
What did Rochester Regional Health actually report?
In August 2026, Rochester Regional Health said its Moxi robots had completed more than 100,000 trips at Rochester General Hospital and Unity Hospital. The system estimates that this work returned more than 50,000 hours to its staff.
Both figures come from the health system's own reporting, not from an audit. The coverage we reviewed does not show how the hour estimate was built. Treat the headline numbers as a reason to ask questions, not as a benchmark to copy.
What does a trip count actually measure?
A trip count records completed movements. It says nothing about how long each movement took, how long a nurse waited for a delivery, or whether a door held the robot up. Two sites with identical counts can have very different delays behind them.
The Rochester coverage does not define a trip in the sources we checked. Before comparing any count with your own, confirm the start point, the end point and what counts as a completed handoff.
Keep this separate from a different metric. As of November 2026, a Robot Report item we checked cites Diligent Robotics, which makes Moxi, with more than 100,000 autonomous elevator rides and a fleet of 100 robots at 20 sites. That item is an older company announcement, is undated in our search, and counts elevator rides rather than Rochester trips.
Where does the 50,000 hour figure come from?
The health system calls 50,000 hours an estimate of staff time returned, not an audited result. The same reporting cites about 55,000 miles of walking, or roughly 120 million steps, saved for employees, again as the system's estimate.
Estimates like these rest on inputs such as how long a manual run takes, how often it happens and what the freed time is used for. The public sources do not list those inputs, so a careful reader has to ask for them.
Returned time is not the same as cut payroll. A staff member who no longer walks a supply run gets minutes back for other work, and whether that becomes a saving depends on how the hospital reassigns the time.

How did the Rochester fleet grow across two hospitals?
Rochester Regional began using the robots in 2023 with four units at Rochester General and four at Unity, according to WXXI's 2023 coverage. CBS News reports the system operates eight of the devices, though the article date was not confirmed in our search.
Reported totals since 2023 split into more than 75,000 deliveries at Rochester General and more than 25,000 at Unity, as Finger Lakes 1 reported. That exact split was not confirmed on the health system's own page, so cite it as reported rather than verified.
How can your site track trips, delays and handoffs?

Build your own count before you need one. The goal is to see every run with enough context to explain a slow day, not to produce a tidy total. A log you can reproduce beats a headline you cannot.
Record these fields for every run, at minimum:
- Request time and dispatch time, so queue wait shows separately from travel time
- Origin and destination, with the floor and elevator bank used
- Elevator and door wait, in seconds, from the robot log or the nurse station
- Pickup and drop off confirmation time, plus the name of the person who signed the handoff
- Every stop, reroute or human override, with a short reason code
Should robot runs be measured against manual runs?
Measure the same work on both sides. A manual run includes the walk, the wait and the handoff. A robot run includes queue time, elevator wait and any person who must meet the robot at the far end.
Review the log weekly for the first month. Look for repeated waits at one elevator bank, handoffs that stall because no one is at the drop point, and runs the robot could not finish. Those patterns often explain the gap between a demo and a daily routine.
Ask whether the receiving staff still stop their work to take the load. If they do, the saved time may be smaller than the distance suggests. The Rochester figures are estimates built on assumptions the coverage does not list, so your own timed sample carries more weight than any headline.
Where does a lease fit into a hospital delivery plan?
Service Robot Co. is a vendor neutral robot integrator for US businesses. We match the robot to the task across manufacturers, then lease it through financing, deploy and integrate it, train staff and service every unit through a nationwide US engineer network.
A hospital team usually starts with a site assessment and site mapping. We quote one fixed robot lease payment on a three year lease after that assessment, so the hospital sees the cost before any unit arrives.
A cautious robot pilot program can start with one leased unit, with the logging method above running from day one. Before you sign, ask any integrator about spare unit coverage, remote triage, on-site dispatch and go live support. Those answers decide how far a single fault can disrupt a route.

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
- Finger Lakes 1, Rochester Regional robots reach 100,000 hospital deliveries (August 2026)
- Finger Lakes Daily News, Rochester Regional robots complete 100,000 hospital deliveries
- CBS News, robots in hospitals and Moxi
- WXXI News, Rochester Regional trains new robot employees (2023)
- The Robot Report, Moxi reaches 100k autonomous hospital elevator rides milestone
Service Robot Co. is not affiliated with, sponsored by, or endorsed by the companies mentioned in this article.




