Network Throughput Calculator

Effective throughput from a nominal link rate and an efficiency factor.

This is a planning estimate, not a measurement or a guarantee. Real throughput can also depend on latency, packet loss, congestion, protocol behavior, CPU limits, encryption, server performance and application behavior. The efficiency percentage is an assumption you supply, not a measurement — nothing is probed or tested here.

What does this calculator do?

A link rate is what the interface is rated for; throughput is what your application actually gets. The gap between them comes from Ethernet framing, IP and TCP headers, acknowledgements, retransmissions, encryption, congestion and the endpoints themselves. This calculator makes that gap explicit: you supply the nominal rate and the share of it you expect to keep, and it returns the effective throughput in Mbps, MB/s and GB per hour, plus the capacity given up to overhead. The efficiency figure is your assumption — the tool cannot measure your path. Units follow the standards exactly: kB, MB, GB and TB are powers of ten (1 GB = 10⁹ bytes) while KiB, MiB, GiB and TiB are powers of two (1 GiB = 2³⁰ bytes). The two ladders are never mixed, so "1 GB = 1024 MB" is not treated as a universal rule.

Formula

Throughput is the nominal rate scaled by the efficiency you expect to achieve.

throughput = linkBandwidth × (efficiency ÷ 100)
MB/s = throughput ÷ 8 ÷ 10^6
overhead = linkBandwidth − throughput

How to use it

Enter the nominal rate of the bottleneck link with its unit, then the efficiency you expect as a percentage between 1 and 100. As rough starting points: a clean switched LAN path often sustains 90–95%; a tuned WAN link with encryption might reach 70–85%; a congested, lossy or high-latency path can fall much lower. If you have a measured result from a tool such as iperf3, derive the efficiency from it rather than guessing.

Worked example

A 1,000 Mbps link at 85% efficiency gives 850 Mbps of effective throughput — 106.25 MB/s, or 382.5 GB per hour if sustained. The remaining 150 Mbps is the capacity assumed lost to framing, headers and retransmissions.

Formula version1.0.0
Formulathroughput = linkBandwidth × (efficiency ÷ 100) MB/s = throughput ÷ 8 ÷ 10^6 overhead = linkBandwidth − throughput
Precision4 decimals

Frequently asked questions

What efficiency should I enter?

There is no single right answer, which is why the tool asks instead of assuming. Base it on a measurement of your own path if you have one; otherwise use a conservative figure and treat the output as a planning ceiling rather than a target.

Is this a speed test?

No. Nothing is measured or transmitted — the result is arithmetic on the two numbers you typed. There is no ping, no DNS lookup and no probe of any kind.

Why can throughput be far below the efficiency I set?

Because efficiency is only one of many limits. Latency combined with a small TCP window, packet loss, a slow disk, a busy server, single-threaded transfer software or an intermediate device can each cap throughput well below the framing-overhead figure.

Sources

Related calculators

Last updated: 2026-08-10 · v1.0.0 · Report an error