Estimate network bandwidth requirement from explicit engineering assumptions. The tool shows the primary planning value plus supporting figures so you can see how traffic, margin, geometry, or path components affect the result. Use measured inputs when available and treat the output as a design estimate rather than a service guarantee.
The result is provisioned link capacity, not expected average traffic. It combines peak concurrency, application demand, overhead, and an explicit operating headroom assumption.
Planning estimate only. Validate assumptions against equipment specifications, measurements, and local operating conditions.
150 concurrent users at 1.8 Mbps create 270.0 Mbps of payload. After 20% overhead and a 60% utilization target, required capacity is 540.0 Mbps.
Dividing by the utilization target sizes the link so modeled traffic occupies only that share, leaving capacity for variation.
Yes when traffic is asymmetric or the service has different directional limits. Use the relevant user demand for each direction.
It can cover protocol headers, retransmissions, tunneling, or other non-payload traffic. Use measurements when available.
Usually not. Enter the number active during the design peak, not every registered account, unless all can transmit at once.
No. Latency, packet loss, jitter, Wi-Fi or radio conditions, routing, and server capacity also affect performance.
| Variable | Role |
|---|---|
| Payload demand | Concurrent users × per-user Mbps |
| Overhead | Non-payload traffic allowance |
| Utilization target | Desired loaded share of provisioned capacity |