Throughput Calculator
Calculate network, TCP, RAID, LTE/5G, and Satisfactory train throughput with mode-specific formulas and transparent assumptions.
Calculate network transfer throughput, TCP window-limited throughput, ideal sequential RAID throughput, LTE/5G radio capacity, or Satisfactory train throughput from one multi-mode tool.
Throughput result
Throughput Calculator
A throughput calculator needs to know what system you are measuring. Network transfer throughput, TCP window-limited throughput, storage-array throughput, cellular-radio capacity, and Satisfactory train throughput use different models. This calculator separates those modes instead of forcing unrelated problems into one formula.
Network Throughput Calculator
The network-transfer mode uses the basic rate relationship: throughput = data transferred ÷ elapsed time. Data is normalized to bits and time to seconds, then the result is shown in Mbps, Gbps, MB/s, and GB/s. Decimal network units and binary MiB/GiB inputs are kept distinct.
This is measured application-data rate for the values you enter. Ethernet, IP, TCP/UDP, encryption, storage, retransmissions, and application overhead can make observed link utilization differ from this simple payload rate.
TCP Throughput Calculator
For a single TCP flow under ideal no-loss conditions, Microsoft documents the familiar receive-window limit as maximum bytes/s ≈ TCP receive window bytes ÷ RTT seconds. A larger round-trip time requires a larger receive window to keep a high-bandwidth path full.
The TCP mode therefore shows the window-limited rate and, when you enter a target Mbps value, the approximate receive window required by the bandwidth-delay product. Packet loss, congestion control, delayed acknowledgements, sender limits, receiver autotuning, middleboxes, CPU and application behavior can reduce real throughput.
RAID Throughput Calculator
The RAID throughput calculator estimates ideal sequential aggregate throughput from the number of drives and each drive’s sequential read/write rate. RAID 0 scales reads and writes across all drives. RAID 1 can service reads from mirrors but writes are limited by mirroring. RAID 5 and RAID 6 reserve one and two drive-equivalents respectively for parity in the ideal sequential logical-data model. RAID 10 uses half the drives for unique mirrored data on writes while reads can potentially use all members.
These are planning ceilings, not benchmark predictions. Linux kernel and IBM documentation both note that parity RAID behavior depends strongly on write pattern, full-stripe vs partial-stripe writes, controller/cache behavior, failures and rebuilds. Small random writes can be far slower than the sequential estimate shown here.
LTE Throughput Calculator and 5G Throughput Calculator
The LTE/5G mode uses a transparent capacity relationship: Mbps = bandwidth in MHz × spectral efficiency in bit/s/Hz/layer × MIMO layers × carriers. The optional usable-resource factor then reduces that theoretical number for scheduling, control channels, guard resources and other overhead that you want to account for.
This intentionally does not pretend to reproduce every LTE or 5G NR peak-data-rate parameter. Actual user throughput depends on modulation/coding, SINR, scheduler allocation, carrier aggregation, MIMO rank, TDD pattern, protocol overhead, device capability, cell load and network configuration. Use measured or vendor-appropriate spectral efficiency when you need a realistic scenario.
Satisfactory Train Throughput Calculator
The Satisfactory train throughput calculator follows the current Official Satisfactory Wiki train-throughput model for item Freight Cars. Each car has 32 inventory stacks. During a freight-platform loading animation, platform inputs are blocked for 27.08 seconds.
First, time to fill a car is calculated from stack size, 32 slots and the input rate, plus the loading lockout. If the platform cannot fill a car before the train returns, throughput is input/lockout limited. If the car fills before the train returns, throughput is limited by cargo capacity divided by round-trip time. Multiple cars are multiplied only under the assumption that each has an identical platform and input rate.
Frequently Asked Questions
Is bandwidth the same as throughput?
No. Bandwidth normally describes the available or nominal link capacity. Throughput is the rate actually carried or estimated for a specific flow/workload.
Why is TCP throughput lower on high-latency links?
A sender can have only a finite window of unacknowledged data in flight. As RTT rises, the same receive window is spread over more time, reducing the window-limited rate unless window scaling/autotuning provides a larger effective window.
Why can RAID 5 or RAID 6 benchmarks be lower than this calculator?
The calculator models ideal sequential aggregate bandwidth. Partial-stripe writes require parity-related reads/writes, while controllers, caches, filesystems, queue depth, rebuilds and workload shape affect observed results.
Is the LTE/5G result a guaranteed phone speed?
No. It is a capacity estimate based on the bandwidth, spectral efficiency, layers, carriers and usable-resource factor you enter. Real mobile speed can be much lower.
Does the Satisfactory mode include station lockout?
Yes. The item-train mode includes the current 27.08-second freight-platform loading lockout and 32-stack car capacity documented by the Official Satisfactory Wiki.
Methodology and Sources
The TCP relationship is cross-checked against current Microsoft networking documentation. RAID assumptions are framed as ideal sequential planning estimates and are limited using Linux kernel and IBM parity-RAID documentation. Satisfactory train logic is based on the Official Satisfactory Wiki’s current train-throughput tutorial. LTE/5G is intentionally a user-parameterized spectral-efficiency capacity model rather than a hard-coded claim about a specific 3GPP release, device or network.