Project data transferred through a 5G small cell over a selected planning period. The model uses endpoint count, average active throughput, active hours, and traffic utilization rather than assuming every device runs at peak speed continuously. It reports total, daily, and per-user volume so you can compare a forecast with counters, backhaul commitments, or data-processing capacity and keep overhead visible.
The main result is decimal terabytes transferred over the selected planning period. Daily and per-user figures make the assumptions easier to compare with measured counters or plan limits.
Traffic varies by application, day, and user. This is a volume estimate, not a peak-throughput or radio-capacity calculation.
For 250 users at 6 Mbps, 5 active hours per day, 30% utilization, and 30 days, payload traffic is 30.38 TB. Adding 10% overhead gives 33.41 TB.
No. Use average throughput while a user is active. Peak link speed would usually overstate transferred data.
A user rarely transfers at the entered throughput continuously. Utilization represents the active-time share actually carrying traffic.
The base result represents traffic at the entered rate. Add an overhead percentage if your metering or backhaul plan includes transport and protocol overhead.
Enter the users represented in the daily estimate. The active-hours and utilization inputs already describe how much each user transfers.
Use the displayed total for the selected number of days, then add a separate growth and contingency allowance suitable for your operation.
| Variable | Meaning | Unit |
|---|---|---|
| Users | Population included in the estimate | count |
| Active rate | Average payload throughput while active | Mbps |
| Active hours | Daily active window per user | hours/day |
| Utilization | Share of active window carrying traffic | % |
| Overhead | Additional non-payload traffic allowance | % |