5G Throughput Calculator
The formula
What the 5g throughput tells you
A first-principles 5G NR estimate from bandwidth, modulation and MIMO layers — the same arithmetic the vendor coverage maps hide.
Calculation: Peak ≈ BW × bits/sym × layers × 1.56 (TS 38.214 PRB mapping); × scheduling load. Enter your inputs and every substitution is shown below the result.
Reading the result
Real user numbers land at 50–70 % of the radio-level figure once the core network and contention bite; anything above 400 Mbps already beats most fixed broadband.
Rules of thumb: Typical mid-band deployments: 100 MHz, 4 layers → 600–900 Mbps peak cell, 150–300 Mbps user.
Limitations and best practice
Aggregation across bands multiplies these columns, but only where the device supports EN-DC — a phone-class limit, not a tower one.
This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Frequently asked questions
Why is my 5G slower than this calculator?
Does mmWave change the model?
Source & methodology
3GPP TS 38.214 NR numerology and peak-data-rate formulas.
5G Throughput explained: formula, worked example and honest limits
You are here because you need a specific number, and you want to see how it was produced before you rely on it. 5G Throughput is the kind of number people argue about from memory. This page ends that argument with arithmetic you can watch happen: enter your figures, get Realistic downlink in real time, and see every substitution printed below.
It helps to separate the mechanics from the interpretation. The mechanics are fixed: Peak ≈ BW × bits/sym × layers × 1.56 (TS 38.214 PRB mapping); × scheduling load. Anyone, anywhere, entering the same inputs will get the same 2,628.0 Mbps. The interpretation is where experience counts: whether 2,628.0 Mbps is good, normal or alarming depends on comparisons covered below, and that is the part most articles about 5G Throughput never explain.
That makes documentation a feature. The steps block above exists so that the next engineer to read this page can verify not just the result but the reasoning — the difference between a number that gets acted on and one that gets argued with.
Nothing below is stock text pasted around a number: the worked example computes realistic downlink = 2,628.0 Mbps from this tool’s own defaults, and the sensitivity section ranks the inputs that move the result — Scheduling load first, at ≈10.0 % of the headline for a ten-percent error either way in that input. Read the sections in order and you will be able to reproduce every figure by hand.
Every input in 5G Throughput, and what it does to the answer
One formula, published in full: Peak ≈ BW × bits/sym × layers × 1.56 (TS 38.214 PRB mapping); × scheduling load. Anything you can read, you can reproduce in a spreadsheet, and that reproducibility is the whole point of printing it rather than hiding it behind a button.
Channel bandwidth (MHz) (example value 96) is a numeric input whose unit is fixed by the label; a wrong unit is a wrong answer wearing a plausible disguise. The example value is there to demonstrate the mechanics, not to describe your situation — overwrite it.
Modulation (example value 64-QAM (6)) is a choice rather than a quantity — pick the option that matches your situation, because the calculation path branches here. Replace the example with the figure from your own records — the tool recomputes instantly and the printed steps follow your numbers.
MIMO layers (example value 4) is a quantity rather than a category — precision here is cheap and worth having. This input feeds the formula directly; a defensible figure here is worth more than false precision anywhere else.
Scheduling load (%) (example value 73) is a numeric input whose unit is fixed by the label; a wrong unit is a wrong answer wearing a plausible disguise. Check the convention first: if the source says “6.5 % per year”, type 6.5 and let the formula do the rest.
What each “Modulation” choice actually does: QPSK (2 bits/sym) → 876.0 Mbps · 16-QAM (4) → 1,752.0 Mbps · 64-QAM (6) → 2,628.0 Mbps · 256-QAM (8) → 3,504.0 Mbps That table is the honest answer to “does this option matter”, re-derived from the formula rather than hard-coded into page copy.
A fully worked 5G Throughput example
The tool prints its own working; this is the same arithmetic on the example values, reproduced so you can follow it by hand. Starting figures: Channel bandwidth (MHz), Modulation, MIMO layers, Scheduling load (%). The computed realistic downlink comes out at 2,628.0 Mbps, which the interpretation band labels “Millimeter-wave-grade numbers”.
- Resource blocks = 96 MHz mapped through the 38.214 comb
- Peak = 96 × 6 bits × 4 layers × 1.56 = 3,600 Mbps
- × 73 % real scheduling load = 2,628.0 Mbps
- Spectral efficiency = 37.5 bps/Hz vs LTE’s ~3–4
Theoretical peak — 3,600.0 Mbps. If your inputs change, this is usually the first companion figure to move.
Per-layer throughput — 657.0 Mbps. This is the number experienced users quote when the headline alone would mislead.
Time to 2 GB at this rate — 0.1 min. Read next to the headline, this is the figure that shows the shape of the trade-off.
Spectral efficiency — 37.5 bps/Hz. Read next to the headline, this is the figure that shows the shape of the trade-off.
Re-running with your own figures is instant; re-running by hand once is the best way to know the tool is telling you the truth.
Scenario table: 5G Throughput at ±10 % and ±20 % of the key input
Single-point answers invite false confidence, so the same engine was run across a band around the input that matters most here. Each row is a full recalculation of 5G Throughput, not an interpolation.
| Scheduling load setting | Realistic downlink |
|---|---|
| 80 % of the example value | 2,102.4 Mbps |
| 90 % of the example value | 2,365.2 Mbps |
| example inputs | 2,628.0 Mbps |
| 110 % of the example value | 2,890.8 Mbps |
| 120 % of the example value | 3,153.6 Mbps |
Across 5 settings of Scheduling load, the result spans 2,102.4 Mbps to 3,153.6 Mbps. A decision that only works at one row of this table is a decision waiting for an input to move. Reproduce it in the form above by editing Scheduling load alone; the substitution steps will follow your figures exactly.
The levers behind 5G Throughput, ranked by effect
Generic advice says “it depends on your inputs”; this section says exactly how much. Each field was perturbed by ±10 % in isolation and the realistic downlink recomputed, so the ranking below is measured rather than asserted. It is the fastest honest answer to “what matters most in 5G Throughput?” — and it is specific to these defaults, because sensitivity moves with the starting point.
- Scheduling load +10 % → 5G Throughput = 2,890.8 Mbps · −10 % → 2,365.2 Mbps (the realistic downlink shifts ≈10.0 %)
- Nudge Channel bandwidth by ±10 % and 5G Throughput lands between 2,365.2 Mbps and 2,890.8 Mbps (sensitivity ≈10.0 %)
- MIMO layers: ten percent up gives 2,890.8 Mbps, ten percent down gives 2,365.2 Mbps — ≈10.0 % of the realistic downlink either way
Scheduling load is the dominant lever here: ten percent either way moves the result by about 10.0 %, from 2,365.2 Mbps to 2,890.8 Mbps. That is where a careless figure does the most damage, so check it against a source, and Channel bandwidth is effectively tied with it (≈10.0 % for the same nudge), so verify the pair together. The remaining fields can sit at safe defaults without materially changing the answer — knowing which is which is what separates a careful calculation from an anxious one.
What a 5G Throughput of 2,628.0 Mbps means in practice
Nobody acts on a bare figure — they act on a figure with a comparison attached. The default case lands in the “Millimeter-wave-grade numbers” band, and bands are deliberately wide because real situations overlap. How much of that band is luck? On Scheduling load alone ten percent either way covers 2,365.2 Mbps to 2,890.8 Mbps. The practical reading rules: ask what would have to change to move you one band. If the answer is “a small, plausible input difference”, the band itself is not the finding — the uncertainty is.
The comparison worth making is not with somebody else’s 5G Throughput but with the version of your own situation measured last quarter — same formula, same conventions, different inputs.
Why 5G Throughput results go wrong — and how to prevent it
Aggregation across bands multiplies these columns, but only where the device supports EN-DC — a phone-class limit, not a tower one. This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Treating the example inputs as a recommendation. They are a demonstration of the mechanism — a decision-grade 5G Throughput begins the moment your own figures replace them.
Attention is also misallocated between fields. Having measured this engine, we can say where it belongs: Scheduling load first, everything else second.
Another is comparing across contexts: a 5G Throughput computed with one set of conventions should never be lined up against a figure computed with another. Check the inputs behind both before ranking them.
Six things to confirm before acting on 5G Throughput
- Check that every field the formula needs actually arrived from a document, not from recollection.
- Compare the result with one independent method or published benchmark.
- Re-verify Scheduling load against a source document — ten percent of error there moves the headline by ≈10.0 %.
- Validate inputs against a live measurement, not datasheet peak figures.
- Record the date and the inputs alongside the number so future-you knows what was assumed.
- Run the ±10 % stress on the top two levers and check that your conclusion survives both.
How to use the 5G Throughput tool properly
The tool does the arithmetic; the routine below is what makes the arithmetic trustworthy. Five steps, a minute total — and afterwards you will know not just what the number is, but which assumption produced it.
Step 1 — one document, one pass. Open the statement, label or record that holds channel bandwidth (mhz), modulation, mimo layers, scheduling load (%) and transcribe straight into the form. Transcription from a single source removes the mismatch errors that appear when figures are assembled from three different places. Write the assumptions in the same file as the result, and future arguments take minutes instead of meetings.
Step 2 — enter the conservative case first. Resist the flattering scenario. Type the inputs you would defend in front of a sceptical reader, read the Realistic downlink (2,628.0 Mbps for the example values), and note the verdict band. Repeating a calculation with the same numbers proves only that the arithmetic is reliable — which is worth knowing.
Step 3 — measure what deserves measuring. The ranked levers above tell you where a careful figure pays off. Everything else can stay approximate, which is a licence to stop hunting for data you do not need. One decimal place more than your data supports is one decimal place of fiction.
Step 4 — run the scenario trio. Expected, pessimistic, optimistic. The gap between pessimistic and expected is the number to plan against; the optimistic result is useful only as a ceiling. Compare the calculation to the rough guess you arrived with, and ask why they differ.
Step 5 — record the context, not just the number. Note today’s date and the inputs alongside the 2,628.0 Mbps output. Six months from now the context is what turns this figure into a trend. Suspiciously tidy answers deserve the same scrutiny as untidy ones.
The real-world conversations 5G Throughput settles
In Networks & Storage the figure computed here is usually the first one somebody asks to see. Having it — with the formula behind it — changes your position in the conversation from participant to reference. Write the figure down before moving on; memory flatters whichever number you saw last.
The companion outputs — Theoretical peak and Per-layer throughput — exist for the second stage of that screen: the headline sizes the prize, while the companions describe the trade-off you are accepting to get it. Most surprises in numbers are surprises about inputs, not about formulas.
Re-running this page costs nothing and catches the slow drifts that never announce themselves. In Technology & Computing the expensive mistakes are rarely sudden; they are small changes in Channel bandwidth (MHz) that nobody recalculated for a year. Write the figure down before moving on; memory flatters whichever number you saw last.
The questions that come up most about 5G Throughput
What affects 5G Throughput the most?
Measured on this engine, Scheduling load is the dominant lever: moving it ±10 % shifts the realistic downlink across 2,365.2 Mbps to 2,890.8 Mbps — about 10.0 % of the headline, with Channel bandwidth next at ≈10.0 %. The ranked list in the sensitivity section is computed live, not asserted from a template.
Do channel bandwidth and scheduling load matter equally?
Effectively. Measured on this engine they land at ≈10.0 % and ≈10.0 % for the same ten-percent nudge, so the honest advice is to get both right; chasing precision in only one of them buys almost nothing.
How much does the “Modulation” choice change the answer?
The spread is not cosmetic: this choice alone takes 5G Throughput from 876.0 Mbps to 3,504.0 Mbps with every other input frozen, which is more influence than most of the numeric fields on this page can claim.
What is a typical 5G Throughput?
On the worked example above 5G Throughput comes out at 2,628.0 Mbps. Treat that as one point on a distribution rather than a norm: the bands, the companion outputs and the sensitivity ranking tell you how wide the plausible range really is.
How do I calculate 5G Throughput by hand?
Use the stated model — Peak ≈ BW × bits/sym × layers × 1.56 (TS 38.214 PRB mapping); × scheduling load — and substitute in the order the tool prints (it starts from Resource blocks = 96 MHz mapped through the 38.214 comb). On the example inputs the hand route lands on 2,628.0 Mbps, exactly what the calculator shows. A spreadsheet reproduces it in two or three cells; doing it once by hand is what makes the automated answer trustworthy.
What happens to 5G Throughput if scheduling load changes by 10 %?
Try it in the form above and the printed substitution will follow you; the pre-computed answer for the defaults is 2,365.2 Mbps to 2,890.8 Mbps across the ten-percent probe, i.e. ≈10.0 % sensitivity on the realistic downlink.
Is the 5G Throughput result of 2,628.0 Mbps good or bad?
The tool answers “what”, not “whether”: 2,628.0 Mbps carries the verdict “Millimeter-wave-grade numbers” for the default case, which is a starting interpretation rather than a verdict on your situation. Re-run with your own figures and compare the bands.
Is 5G Throughput accurate?
The arithmetic is exact: Peak ≈ BW × bits/sym × layers × 1.56 (TS 38.214 PRB mapping); × scheduling load is evaluated with full floating-point precision and every substitution is printed in the worked example. What limits accuracy is input quality and the model’s assumptions, so treat the 2,628.0 Mbps result as the correct answer to the question you typed — and check the assumptions section before acting on it.
How do I calculate 5G Throughput manually?
Write down the inputs, then follow the printed steps in order — Peak ≈ BW × bits/sym × layers × 1.56 (TS 38.214 PRB mapping); × scheduling load. A spreadsheet replicates it with two or three cells. The manual route is worth doing once to build intuition; after that the calculator saves time and eliminates transcription slips.
Why is my 5G slower than this calculator?
Scheduling load, MIMO rank fallback in the pocket, and core-network backhaul all shave the radio number down toward the 30–50 % band.
Does mmWave change the model?
Same math with 400 MHz channels — the different physics is range and blockage, not spectrum math.
Does this 5G Throughput tool store my numbers?
No. The entire calculation runs in your browser session; nothing entered above is transmitted or saved, which is the correct behaviour for sensitive Technology & Computing figures and the reason you can re-run this page as often as you like.
The vocabulary of 5G Throughput
- Theoretical peak
- 3,600.0 Mbps in the default 5G Throughput calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- Per-layer throughput
- 657.0 Mbps in the default 5G Throughput calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- Time to 2 GB at this rate
- 0.1 min for the 5G Throughput worked case; it sits next to the main result because it carries context the headline leaves out.
- Realistic downlink
- The primary output of this tool: 2,628.0 Mbps for the default inputs, computed exactly from Peak ≈ BW × bits/sym × layers × 1.56 (TS 38.214 PRB mapping); × scheduling load.
- Worked example
- The calculation written out in full so that nothing on this page has to be taken on trust.
- Verdict band
- The plain-language label — here “Millimeter-wave-grade numbers” — mapping the computed figure onto experience-based ranges for Technology & Computing.
- Sensitivity (±10 %)
- How far the 5G Throughput moves when a single input is nudged ten percent either way; the ranked list on this page is computed live from this engine.
The provenance of this 5G Throughput calculation
Everything above runs on one stated formula, applied without hidden coefficients: Peak ≈ BW × bits/sym × layers × 1.56 (TS 38.214 PRB mapping); × scheduling load. Source of record: 3GPP TS 38.214 NR numerology and peak-data-rate formulas. Where a professional version of this calculation differs, it differs in inputs and jurisdiction-specific coefficients, not in the algebra — which is why re-checking your inputs beats hunting for a second calculator.
Nothing here replaces a qualified professional, and nothing here is approximate either — the arithmetic is exact, and the honesty is in the inputs you supply. The sensitivity table above is part of that promise rather than a bonus: it lets you see how much of the result depends on how carefully you measured.
What to do with your 5G Throughput next
Re-run the calculation with your own figures, stress the two most sensitive inputs by ±10 %, and only then act on the result.
Whoever you are (people who need one trustworthy number before their next decision), the next step is the same: replace the example inputs with your own, note the date, and re-run whenever a figure moves. In Technology & Computing, a dated figure is a trend, and an undated one is a rumour.