Knightscope K5
A wheeled patrol robot. Inspect route constraints, charging gaps and historical deployment evidence before sizing a security program.
DROID RESEARCH · SOURCES CHECKED
How much of a patrol schedule can one K5 cover between charges?
The reviewed brochure gives average patrol and charge intervals. These describe a repeating battery cycle, not guaranteed continuous coverage or a site-specific service level.
Knightscope ↗Documented system boundaries
Values are supplier documentation, not Droid measurements. Unknown fields remain unresolved.
| Field | Documented value | Conditions |
|---|---|---|
| Patrol interval | 2.5–3 hours on average | Between charges; route, load and weather test conditions are not stated. Knightscope ↗ |
| Charging interval | 20–30 minutes on average | Autonomous charging; does not include every cause of downtime. Knightscope ↗ |
| Route surface | ADA-compliant surfaces and ramps | Brochure also lists parking-garage grades up to 20%; this is percent grade, not degrees. Knightscope ↗ |
| Dock power | 120 V, 20 A outlet | Supply requirement; not measured energy consumption. Knightscope ↗ |
| Documented sensing | 4 HD cameras, 1 thermal camera, 6 lidar and 13 sonar sensors | Counts do not establish detection accuracy or disclose component suppliers. Knightscope ↗ |
| Configured price | Not established in reviewed sources | No current K5 quote established. The same brochure’s $545/month offer belongs to stationary K1 Hemisphere, not K5. Evidence status: unknown |
| Temperature unit | Not established in reviewed sources | The reviewed K5 line prints 0°–115° without an explicit scale. Do not silently normalize it to Celsius or Fahrenheit. Evidence status: unknown |
A charging-only scenario, not an uptime promise.
Droid calculation: 150 minutes patrolling / (150 + 30 minutes) = 83.3% patrol share. With 180 minutes patrolling and 20 charging, the share is 90%. These are two illustrative combinations of brochure endpoints, not measured bounds or a forecast.
The calculation excludes all other downtime and does not describe visibility at a particular checkpoint. Use actual full-cycle measurements before sizing the fleet.
Knightscope ↗Implications for a real patrol program
Droid’s analysis and proposed procurement checks:
- Charging is only one gap. Count travel to the dock, failed docking, blocked routes, maintenance and human recovery in the actual availability budget.
- A second robot is not automatically a continuous-coverage guarantee: overlapping charge windows, shared network outages and the route revisit interval can still leave blind periods.
- The Times Square record concerns an earlier K5 pilot whose exact hardware revision is unresolved. Do not attribute that pilot’s results to the brochure configuration.
Still to establish
- Delivered hardware / firmware and enabled analytics
- Site-specific patrol coverage, recovery time and alert precision
- Current configured subscription, monitoring and installation scope
- Exact authorization and certification documents for the quoted configuration
What the pilot must prove
- Measure the full patrol-to-charge-to-patrol cycle on the actual route.
- Record missed checkpoints and the longest gap at each location.
- Test escalation, network loss and safe recovery with the site team.
- Keep response staffing and charging coverage in the written operating plan.
Keep deployment evidence separate from specifications.
A historical installation may use different hardware, software and staffing. Open the records to inspect the site, period, mode and outcome limits before applying them to this system.
Source record
- K5 / K1 Hemisphere brochure — K5 pages 1–2 ↗Knightscope · Document title KSCP-KAP-brochure-26Q1-1-all; URL identifies K5V5 · Checked 2026-11-10
Bring us the task.
Let’s find the fit.
Share your environment, the job to be done, and the outcome you need to measure.