Enter the installed device count
Use the devices represented by this traffic class or planning scenario.Estimate simultaneous activity
Set the percentage expected to be actively transferring data during the same peak window.Enter per-device demand
Use average Mbps for one active device in this class.Add peak and utilization allowances
Apply a burst multiplier, then choose how much of planned capacity the peak-adjusted traffic may consume.Review and combine scenarios
For mixed device classes, run separate scenarios and combine compatible peak requirements rather than forcing every device into one average.
Private 5G Bandwidth Requirements Estimator
The Private 5G Bandwidth Requirements Estimator calculates the aggregate capacity needed for an enterprise or industrial private 5G network from device population, active-device percentage, average throughput, a peak multiplier, and a target utilization ceiling. Unlike a simple per-device total, it lets you distinguish between the full installed device base and the subset expected to carry traffic simultaneously.
The estimator is useful for early sizing of campus networks, factories, warehouses, ports, utilities, and other private wireless environments. Different device classes can have very different traffic profiles, so a single run works best when the population is reasonably similar; mixed cameras, robots, sensors, tablets, and voice devices should be modeled in separate groups and their peak demands combined. The result is an application-capacity target that still needs to be checked against spectrum, radio design, uplink/downlink balance, and transport capacity.
Private 5G bandwidth inputs
%
Mbps
×
%
Result
—
required aggregate capacity
Active devices—
Peak-adjusted demand—
Capacity headroom—
Active devices = Total devices × (Active percentage ÷ 100)Base demand = Active devices × Average Mbps per active devicePeak demand = Base demand × Peak multiplierRequired capacity = Peak demand ÷ (Target utilization ÷ 100)
Where:
- Total devices — installed devices in the modeled class
- Active percentage — share transferring data simultaneously at peak
- Average Mbps per active device — mean application throughput during activity
- Peak multiplier — burst or uncertainty factor
- Target utilization — maximum planned share of aggregate capacity used by peak demand
Assumptions: The modeled devices share one average traffic profile. For heterogeneous workloads, calculate each class separately. The result is aggregate throughput demand, not a direct spectrum or cell-count calculation.
What the result means
The main result is the aggregate Mbps capacity required so peak-adjusted active-device traffic remains within the selected utilization ceiling.
Private 5G deployments should also check coverage, uplink-heavy workloads, redundancy, mobility, QoS, and spectrum-specific radio capacity.
Given:
- 800 total devices
- 35% simultaneously active
- 2.5 Mbps per active device
- Peak multiplier: 1.4×
- Target utilization: 70%
Calculation:
Active devices = 800 × 0.35 = 280
Base demand = 280 × 2.5 = 700 Mbps
Peak demand = 700 × 1.4 = 980 Mbps
Required capacity = 980 ÷ 0.70 = 1,400 Mbps
Result: 1,400 Mbps required capacity
Interpretation: The modeled device class requires about 1.4 Gbps of aggregate capacity to keep the 980 Mbps peak-adjusted demand at 70% utilization.
Why use active-device percentage instead of assuming every device transmits at once?
Many private-network devices are idle, periodic, or event-driven. Separating installed count from simultaneous activity can produce a more realistic demand estimate.
How should I handle cameras and low-rate sensors together?
Model them as separate traffic classes when their rates and activity patterns differ substantially. Add the resulting peak demands only when their peak periods are expected to overlap.
Does the calculator account for QoS classes or network slices?
No. It estimates aggregate application bandwidth. QoS guarantees, priority, slice reservation, and scheduler behavior require additional capacity-allocation analysis.
Can the result be used to choose spectrum bandwidth?
It is an input to that decision, not the final answer. Spectrum requirements depend on achievable spectral efficiency, duplexing, interference, MIMO, coverage, and uplink/downlink traffic mix.
Why is utilization lower than 100% useful in industrial networks?
Headroom can absorb bursts, retransmissions, growth, or temporary reductions in radio efficiency. The appropriate margin depends on the service criticality and engineering design.