Home › Learn

What does RTLS actually cost per bed?

By Thaddeus Stepanovich — Founder, Harbinge.rs · 14 years in EMS and healthcare IT

What do published figures say?

Start with the honest headline: no RTLS vendor and no independent analyst publishes a current, concrete "$X-$Y per bed" figure for a full deployed system. Every source we could find either avoids dollar figures entirely or buries them in gated whitepapers behind a demo request. That gap is itself worth stating plainly, because it's the reason so many buyers end up anchoring on the wrong number.

What does exist is hardware-level pricing, which is not the same thing as deployed cost. According to an academic survey on cost and complexity as barriers to RTLS adoption (Moeini & Coates), BLE RTLS infrastructure is reported to cost "several tens of dollars per piece," versus "several hundreds of dollars" for alternative RTLS hardware types — a difference the paper frames as up to roughly 90% lower hardware pricing for BLE. That's a real, sourced signal about relative architecture cost, but it describes tags and gateways sitting on a shelf, not a system installed in a 400-bed hospital.

One industry cost-comparison blog goes further, breaking out separate ranges for UWB tags, UWB anchor infrastructure, BLE beacon tags, and BLE infrastructure, deployed at a stated device density per square meter. We're deliberately not repeating those numbers here: it's a single vendor-adjacent industry blog, not an audited market report, we couldn't independently corroborate the exact figures, and neither UWB nor BLE vendors publish list pricing that would let us check them. What the same source is directionally consistent with — and with the sourced 90% hardware-cost gap above — is that BLE hardware runs roughly an order of magnitude cheaper per unit than UWB hardware across tags and infrastructure alike. That gap in relative cost is the useful signal; the absolute dollar figures attached to it are not something we're willing to publish as fact. Treat it as a directional comparison between architectures, not a quote you could take to a CFO.

A few adjacent figures are worth knowing even though they're not per-bed costs either. According to kontakt.io, many RTLS providers now charge a flat rate per licensed hospital bed covering the BLE beacons and tags needed to manage equipment like IV pumps, wheelchairs, and telemetry packs — which confirms the per-bed pricing model exists commercially, even though no dollar figure is published alongside it. The same source reports that a 400-bed facility can go live on core RTLS use cases in as little as two weeks when the deployment leverages existing Wi-Fi infrastructure instead of a purpose-built network, which is a real cost lever (see below) even without an attached price. And on the returns side rather than the cost side, kontakt.io reports one unnamed health system saved roughly $1 million annually after RTLS deployment by eliminating equipment over-purchasing, and cites Atrium Health Wake Forest Baptist Medical Center as saving approximately $3.5 million through RTLS implementation — vendor-published customer outcomes, not audited figures, but evidence that ROI claims circulate more freely than cost claims do.

Put together: the published record gives you hardware-tier cost ratios and anecdotal ROI, not a number you can multiply by your bed count. Anyone quoting you a specific per-bed dollar range is either working from a real vendor quote for your specific facility, or guessing.

What does the quoted price leave out?

Whatever number does show up in a vendor quote, it's worth walking through what typically isn't in it before you compare it to anything else. None of the following carries a published dollar figure — vendors describe these qualitatively and direct buyers to a sales conversation for pricing — but each is a real, recurring line item in a deployed system:

• Installation labor and ceiling or wall access in occupied clinical space — the line item that most often surprises buyers, since it means coordinating with infection control and unit staff room by room rather than working in an empty building.
• Low-voltage cabling, for any architecture that isn't fully wireless or battery-powered infrastructure.
• Integration with existing IT and Wi-Fi networks, or a dedicated clinical-grade network where facilities choose not to reuse what's already in place.
• A tag on every tracked asset, each with its own battery — CenTrak and AiRISTA publish different multi-year battery-life figures for their own hardware, but under different test conditions (update interval, duty cycle), so don't treat vendor battery-life numbers as directly comparable across brands.
• An ongoing battery-replacement and recalibration program at fleet scale — hospital RTLS deployments commonly involve thousands of asset tags, and environmental and location tags typically need annual recalibration to meet NIST requirements, according to reporting on managed-service offerings from RTLS vendors.
• A maintenance and support contract covering firmware updates, infrastructure repairs, and system recalibration after any renovation that changes room geometry.

Because these buckets compound differently over time — installation is a one-time cost, batteries and recalibration recur on their own schedules, and support contracts typically escalate — industry guidance is to request a five-year total-cost-of-ownership model from any vendor rather than a per-tag or per-bed quote. A quote answers "what does the hardware cost." A TCO model answers the question you're actually trying to answer, which is "what will this system cost me to keep running."

How does cost scale with coverage?

The detail that trips up the most budgets is that RTLS cost tracks the building, not the asset count. Room-level and sub-room-level architectures — CenTrak's Gen2IR infrared and Sonitor's ultrasound-based ULE among them — require a receiver or exciter installed in every room where certainty-based location matters, because both technologies work by containing a signal to a physical space rather than by triangulating it. Cover half the building and you have location certainty in half the building; the other half is a dead zone regardless of how many tags you buy.

That's the opposite of how attestation-based or handheld-audit approaches scale, where cost tracks the number of devices touched, not the square footage instrumented. It's also why partial RTLS rollouts are a common failure pattern: a facility instruments the ED and OR first (reasonably, since that's where the highest-value use cases sit), and then equipment that migrates to an uninstrumented unit simply disappears from the system — which undermines confidence in the whole platform even though the parts that are covered work exactly as designed.

There is a real lever for reducing this cost, though, and it shows up across multiple vendors' own architecture descriptions: reusing infrastructure you already have. CenTrak's BLE locating option and its broader device portfolio are built to let facilities reuse existing Wi-Fi or BLE-enabled access points instead of installing a dedicated network, and kontakt.io reports a 400-bed facility going live on core use cases in two weeks by leveraging existing Wi-Fi rather than building purpose-built infrastructure. The trade-off, consistent with published vendor positioning, is accuracy: CenTrak describes its BLE option as providing "near-room level certainty," a step down from the sub-room "Virtual Walls" precision its dedicated Gen2IR infrared network delivers. Reusing infrastructure lowers the install bill; it doesn't eliminate the fact that coverage, not fleet size, is what you're paying for.

How do lighter-weight approaches compare?

Given how thin the published per-bed numbers are, it's worth comparing RTLS against the lighter-weight approaches buyers actually evaluate on the same four axes: what you pay up front, what you pay on an ongoing basis, how location accuracy works, and how fresh the location data actually is.

Read the "varies" cells as an honest reflection of the sourcing problem, not a dodge: the published figures above are the most specific numbers we could verify, and none of them resolve to a clean per-bed price. For a deeper look at when continuous coverage is actually worth that cost versus when it isn't, see RTLS alternatives and the underlying architecture detail in RTLS explained.

Where Forager fits

Forager doesn't try to compete on RTLS's own terms — it isn't a room-level locating system, and it won't tell you where an asset is this second. What it does is turn the location confirmations that already happen during normal fieldwork — a barcode scan during a service call, a check during rounds — into a timestamped, provable location record, at $15/device/yr with no readers to install and no cabling to run.

That makes Forager's cost scale with the number of devices you're tracking, not the square footage you'd otherwise need to instrument to get room-level certainty everywhere. For the use cases that genuinely need continuous, real-time location — active wander management, second-by-second bed status — that's still a job for infrastructure-backed RTLS. For the much larger set of organizations solving an audit, PMI compliance, or CMDB-freshness problem, it's usually cheaper to confirm location as a side effect of work already happening than to buy and maintain a fleet of readers and tag batteries to answer the same question. See how Forager works, and RTLS alternatives for the fuller decision framework.