toolbox
Home / AI, Data & Technology / Fiber Network Concurrent User Capacity Estimator

Fiber Network Concurrent User Capacity Estimator

The Fiber Network Concurrent User Capacity Estimator translates a shared fiber bandwidth pool into an approximate number of simultaneously active users. It is useful when testing oversubscription assumptions on an uplink, aggregation segment, private network, or access system where each active user is expected to consume a modeled average throughput.

Enter the available aggregate bandwidth, the average Mbps needed by one active user, and the percentage of link capacity you are willing to use during the design period. You can also reserve a bandwidth percentage for protocol overhead, control traffic, bursts, or operational headroom. The calculator first removes the reserve, then applies the target utilization and divides the usable throughput by per-user demand. It is a throughput capacity model; session limits, PON split ratios, hardware tables, QoS, and application-specific peaks may impose separate constraints.

Inputs

Gbps
Mbps
%
%
Result
—
Estimated concurrent user capacity
Raw aggregate bandwidth—
Bandwidth after reserve—
Bandwidth at target utilization—

1. Enter shared bandwidth
Use the aggregate capacity available at the point where concurrent users compete for throughput.

2. Set per-user demand
Estimate average throughput required by one user while active.

3. Choose target utilization
Use less than 100% when you want the design to retain operating headroom during busy periods.

4. Reserve bandwidth
Subtract a percentage for overhead, bursts, control traffic, or other capacity you do not want counted as user payload.

5. Review user capacity
The calculator rounds down because a partial additional user would exceed the modeled design bandwidth.

Raw bandwidth (Mbps) = Capacity (Gbps) × 1,000 Bandwidth after reserve = Raw bandwidth × (1 − Reserve % ÷ 100) Design payload bandwidth = Bandwidth after reserve × (Target utilization % ÷ 100) Concurrent users = floor(Design payload bandwidth ÷ Mbps per active user)

The target-utilization and reserve inputs serve different purposes: utilization limits planned loading, while reserve removes bandwidth from the user payload pool entirely.

What the result means

The result is the number of active users that fit within the modeled payload bandwidth without exceeding the selected design utilization.

Check device, service, PON split, and QoS limits separately; bandwidth may not be the first constraint reached.

Given: 10 Gbps aggregate capacity, 15 Mbps per active user, 70% target utilization, and a 10% reserve.

Calculation: Raw = 10,000 Mbps. After reserve = 10,000 × 0.90 = 9,000 Mbps. Design payload = 9,000 × 0.70 = 6,300 Mbps. Concurrent users = floor(6,300 ÷ 15) = 420.

Result: 420 concurrent users.

Interpretation: At the chosen demand and headroom assumptions, 420 active users fit within the 10 Gbps pool.

Why is capacity rounded down?

The calculated quotient can contain a fraction, but an additional whole user would push modeled demand above the available design payload bandwidth. Rounding down keeps the result within the selected limit.

What is the difference between reserve and target utilization?

Reserve removes a share of nominal capacity from user traffic. Target utilization then limits how much of the remaining capacity is intentionally loaded during the design period.

Can I use peak Mbps per user?

Yes, but it will produce a more conservative user count. Average active-user throughput is often used for aggregate planning, while peak values may be more appropriate for strict guarantees.

Does this calculate total subscribers?

No. It estimates simultaneous active users. Total subscribers can be much larger if only a fraction are active at the same time, subject to the network architecture and service policy.

What other limits should I check?

Examples include PON split ratios, optical budgets, interface rates, device session limits, queues, service-level targets, and redundancy requirements. Any of those can cap the practical user count below the bandwidth result.