5G PRB Calculator
Estimate standardized 5G NR Physical Resource Blocks by channel bandwidth and subcarrier spacing, then model utilized PRBs, remaining scheduling headroom, occupied spectrum, and an estimated downlink throughput figure using practical radio assumptions.
Interactive 5G NR PRB Calculation Tool
Choose your parameters and click Calculate 5G PRBs to see standardized NRB values, estimated utilized PRBs, and a quick capacity chart.
Expert Guide to Using a 5G PRB Calculator
A 5G PRB calculator helps radio engineers, planners, students, and operations teams convert channel bandwidth and subcarrier spacing into a standardized number of schedulable Physical Resource Blocks, often abbreviated as PRBs. In 5G NR, the PRB is one of the most practical units for understanding air interface capacity because scheduling, utilization, and throughput are all strongly tied to how many PRBs the network can assign in a slot. While users often look at bandwidth first, bandwidth by itself does not tell the whole story. Guard bands, numerology, reference signals, control overhead, and the selected duplexing profile all affect how much usable capacity remains.
This calculator is designed to make those relationships easier to understand. It starts from standard NRB values commonly used in 3GPP based deployments, then applies utilization, modulation, coding rate, and MIMO layering to produce an engineering estimate. That means the output is highly useful for planning and benchmarking, but it should still be validated against vendor specific scheduler behavior, TDD patterns, and field measurements.
What is a PRB in 5G NR?
A PRB is a block of radio resources that spans 12 subcarriers in frequency. Its width therefore depends on the subcarrier spacing. For example, with 15 kHz subcarrier spacing, one PRB occupies 180 kHz of spectrum. With 30 kHz subcarrier spacing, one PRB occupies 360 kHz. With 60 kHz, the PRB width is 720 kHz, and with 120 kHz it becomes 1.44 MHz. This is why the same nominal channel bandwidth does not always produce the same number of PRBs across different numerologies.
Key idea: More bandwidth usually means more PRBs, but larger subcarrier spacing generally reduces the PRB count for a given channel size because each PRB is wider in frequency.
Why a 20 MHz channel is not simply 20 MHz divided by PRB width
A common beginner mistake is to divide total bandwidth by 12 subcarriers times the chosen subcarrier spacing and assume the result is the NRB count. Real 5G NR channels require guard bands and operate within standardized raster and channelization rules. Because of this, the actual number of schedulable resource blocks is lower than the raw mathematical maximum. That is why standardized lookup values matter. For example, a 20 MHz FR1 channel at 30 kHz spacing uses 51 PRBs rather than the larger figure a naive calculation might suggest.
How this 5G PRB calculator works
This page follows a practical engineering workflow:
- Select the channel bandwidth in MHz.
- Select the subcarrier spacing in kHz.
- Look up the standardized NRB value for that valid combination.
- Apply utilization to estimate active PRBs used by the scheduler.
- Estimate effective throughput using modulation order, coding rate, MIMO layers, and overhead.
The throughput estimate is intentionally presented as an estimate, not a guaranteed user data rate. Real world performance also depends on signal quality, TDD DL to UL pattern, HARQ behavior, retransmissions, MAC scheduling policy, and UE category or capability set.
Standard NRB Examples for FR1 and FR2
The following table shows representative standardized NRB values used in 5G NR planning. These values are consistent with commonly referenced 3GPP channel bandwidth and numerology combinations.
| Channel bandwidth | 15 kHz SCS | 30 kHz SCS | 60 kHz SCS | 120 kHz SCS |
|---|---|---|---|---|
| 5 MHz | 25 | 11 | Not standard in FR1 | Not used |
| 10 MHz | 52 | 24 | 11 | Not used |
| 20 MHz | 106 | 51 | 24 | Not used |
| 50 MHz | 270 | 133 | 65 | Not used |
| 100 MHz | Not standard in FR1 | 273 | 135 | 66 |
| 200 MHz | Not used | Not used | 264 | 132 |
| 400 MHz | Not used | Not used | Not typical | 264 |
These figures immediately show why numerology matters so much in planning. At 100 MHz, 30 kHz spacing gives 273 PRBs, while 60 kHz gives 135 PRBs, roughly half as many. That does not mean 60 kHz is inferior in all cases. Larger subcarrier spacing can improve phase noise tolerance and reduce slot duration, which helps low latency services and higher frequency operation. The right choice depends on deployment goals, spectrum location, and service mix.
PRB Count Versus Usable Capacity
Operators often ask a more practical question: how much user traffic can those PRBs carry? The answer depends on multiple radio efficiency layers. A PRB can hold a fixed number of resource elements per slot, but not all of them carry user payload. Some are reserved for demodulation reference signals, CSI reporting, synchronization, or control signaling. Once overhead is accounted for, the remaining symbols can be mapped with a modulation order and code rate. MIMO then multiplies throughput further if channel conditions support additional layers.
To illustrate the effect, the next table gives approximate downlink capacity behavior for a 100 MHz channel at 30 kHz spacing with 273 PRBs. These are engineering style estimates rather than guaranteed field rates.
| Scenario | Modulation | Code rate | Layers | Utilization | Approximate throughput |
|---|---|---|---|---|---|
| Coverage oriented cell edge | QPSK | 0.50 | 1 | 60% | About 27 to 35 Mbps |
| Balanced macro deployment | 64QAM | 0.70 | 2 | 70% | About 190 to 230 Mbps |
| High quality urban mid band | 256QAM | 0.85 | 4 | 80% | About 700 to 850 Mbps |
These numbers align with what radio teams see in the field: PRB count provides the framework, but actual throughput depends on spectral efficiency and scheduling quality. A cell with abundant PRBs but poor SINR can underperform a smaller carrier operating under excellent radio conditions.
How to interpret utilization in a PRB calculator
PRB utilization represents the share of available PRBs that are actively assigned to traffic over the averaging interval. A value around 30% to 50% often suggests moderate loading, while sustained values above 70% can indicate a busy sector that may experience scheduling pressure during peak demand. High utilization is not always a problem. In fact, a well loaded site is often a healthy site. The warning sign appears when high utilization is combined with poor user experience, low edge rates, or large scheduling delays.
When you enter utilization in this tool, the output shows used PRBs and remaining PRBs. This helps answer practical questions such as:
- How much scheduler headroom remains during the busy hour?
- Would adding a second carrier or more spectrum likely reduce congestion?
- How much gain might be achieved by moving traffic to higher order MIMO or better modulation?
- Can a site absorb a forecast increase in traffic without immediate expansion?
Step by step: using the calculator correctly
- Start with the exact configured channel bandwidth, not the licensed block size unless they are the same.
- Select the actual numerology used by the cell, usually 15 kHz or 30 kHz in FR1 and 120 kHz in many FR2 cases.
- Enter a realistic PRB utilization figure from OSS counters or test assumptions.
- Choose a modulation order that reflects measured radio quality. 256QAM should not be assumed everywhere.
- Pick a coding rate that matches your planning model. Higher values represent better efficiency but less robustness.
- Set MIMO layers carefully. A 4 layer assumption can materially overstate throughput if the device mix or channel quality does not support it.
- Use overhead values around 10% to 20% unless you have vendor level measurements that justify something more precise.
Common mistakes when estimating 5G PRBs
- Ignoring standardized NRB tables: Raw frequency division is not enough because of guard bands and standardized channelization.
- Assuming 100% payload use: Real cells always spend some resources on control, reference signals, and system procedures.
- Overestimating MIMO: Many planning models assume 4 layers or more where the radio environment only supports 1 or 2.
- Confusing peak rate with average user experience: Theoretical throughput is not the same as busy hour sustained throughput.
- Using the wrong numerology: A wrong SCS selection changes the PRB count immediately and can distort the whole analysis.
Where PRB calculators are most valuable
A 5G PRB calculator is especially useful in four situations. First, it helps with early radio dimensioning when spectrum assets are known but detailed vendor simulations are not yet complete. Second, it supports troubleshooting by connecting OSS utilization counters to a normalized air interface unit. Third, it helps explain capacity tradeoffs to non RF stakeholders, because PRBs are easier to compare than low level OFDM details. Fourth, it is useful in training environments where students need to understand how bandwidth, numerology, and scheduling interact in NR.
PRBs and policy or spectrum context
For broader background on 5G spectrum use and network policy, the following public sources are helpful:
- FCC 5G overview and spectrum policy resources
- NIST 5G research and measurement resources
- NTIA spectrum management resources
Final takeaway
The best way to think about a 5G PRB calculator is as a bridge between radio theory and operational planning. Bandwidth tells you the size of the road, PRBs tell you how many traffic lanes are available to the scheduler, and utilization tells you how full those lanes already are. Once you add modulation, coding, and MIMO, you begin to see what user throughput is realistically achievable. Used properly, a PRB calculator gives engineers a fast, transparent, and standardized way to compare carriers, validate assumptions, and communicate 5G capacity with confidence.
Note: Exact NRB support can vary by frequency range, release, and vendor implementation details. Always confirm planning assumptions against your deployed radio software and current 3GPP documentation.