Private Network Intelligence · Radio Planning
Private Network Radio Sizing & Planning Estimator
Estimate radio count ranges and identify whether site coverage or traffic capacity is the binding planning constraint.
Your Progress
Network Planning · Cross-Vertical · Vendor-Neutral

Private Network Radio Sizing & Planning Estimator

Get a planning-grade estimate of how many radios your private network deployment will likely require — and whether coverage or capacity is the binding constraint. Site-type-aware inputs produce calibrated estimates for industrial, mining, port, airport, and utility environments — not just generic indoor/outdoor. Useful for budget sizing and vendor conversations before formal RF design.

2 phases · ~6 minutes Site-type-aware inputs Coverage + capacity dual estimate Planning risk score Recommended next step
Phase 1Site Geometry
Phase 2Network & Devices
OutputSizing Report
This estimator produces a planning-grade range for budget sizing and vendor conversations. It does not replace RF design, site survey, or vendor engineering. For mission-critical or complex deployments, a formal RF design is required before procurement.
Work email required. Personal email addresses are not accepted.

Loading your estimate…

Retrieving your saved radio sizing estimate. This will only take a moment.

Phase 1 · Site Geometry
Site type is the primary driver of the estimate — it determines which geometry inputs appear and which coverage assumptions apply. Select the type that best describes your operational site.
Input 1 — Site type
What kind of site is this?
Select the operational description, not the industry label. A pharmaceutical warehouse is a standard indoor facility; a pharmaceutical plant with cleanrooms is specialist.
Input 2 — Area & geometry
What is the floor area and ceiling height?
Ceiling height is the single most impactful variable after area. A 30ft ceiling in an open warehouse produces significantly more coverage per radio than a 10ft office ceiling — even with identical floor area.
Typical floor plate — not total building
Levels requiring coverage
Ceiling height
Construction & RF environment
Input 2 — Terminal geometry
Terminal area and levels
Airport terminals require separate coverage planning per level. The estimate covers the terminal building. If airside apron coverage is also required, add it as a separate site or select Mixed Indoor + Outdoor.
Average per level — not total
All levels needing coverage
Input 2 — Apron geometry
Apron area and GSE profile
For airport apron, seamless handover for GSE at vehicle speed is the binding constraint — not coverage area. The estimate accounts for handover overlap at 10–60 km/h.
Total area requiring coverage
Total stand count
Input 2 — Quayside geometry
Berth dimensions and crane profile
Quayside coverage is linear — sized by berth length and coverage depth, not area. Crane height affects whether antennas can be mounted above the crane rail (ideal) or must work around crane shadow zones.
Crane height relative to antenna placement
Input 2 — Container yard geometry
Yard area and stack profile
⚠ Container yards have severe RF obstruction from stacked containers. Each tier of containers reduces effective radio coverage by approximately 15–25%. The estimate widens significantly with higher stacks.
Input 2 — Pit geometry
Operational area and haul road profile
Open pit mines have unique RF geometry — pit walls reflect signal but also create shadow zones on lower benches. Coverage is typically sized per bench level for lower pit areas, with wider coverage on upper benches.
Pit footprint + haul roads + plant
Total haul road requiring coverage
Levels requiring separate coverage planning
⚠ Underground mine sizing uses leaky feeder (radiating cable) — not standard base stations. The output is estimated cable length (km) and amplifier count, not radio count. A professional design is mandatory before procurement for any underground deployment.
Input 2 — Underground geometry
Tunnel network dimensions
All drives requiring coverage combined
Separate horizons requiring coverage
Tunnel profile
⚠ High-voltage switchgear, transformers, and power lines generate significant electromagnetic interference (EMI) that reduces effective radio coverage. The estimate widens to account for this. A site survey to characterise EM noise floor is strongly recommended before design.
Input 2 — Substation / plant geometry
Site area and EM environment
EM interference level
Input 2 — Outdoor area and terrain
Coverage area and terrain profile
Terrain profile
Input 2 — Mixed site geometry
Indoor and outdoor areas
For mixed sites, the indoor coverage estimate is the binding constraint. Enter both indoor and outdoor areas — they are calculated separately and combined.
Indoor construction type
Input 3 — Spectrum band
What spectrum band is planned for this deployment?
Spectrum band is the second biggest driver of radio count. mmWave requires many more radios; low-band requires far fewer. Select Unknown if not yet decided — the estimate range will widen accordingly.
Phase 2 · Network & Devices
Device count and traffic profile drive the capacity estimate. Simple mode uses pre-built profiles — choose the one closest to your primary workload. Advanced mode lets you enter per-class device counts.
Input 4 — Total concurrent devices
All devices connecting to this network simultaneously at peak
Include every device type: cameras, handhelds, sensors, AGVs, gateways, laptops. Count peak concurrent, not total installed.
Input 5 — Traffic profile (Simple mode)
Select the profile that best describes your dominant workload
Uplink is typically the binding capacity constraint for industrial deployments — cameras, sensors, and AGV telemetry all generate uplink traffic.
Advanced mode — device breakdown
Enter counts by device class
~4 Mbps UL each
~2 Mbps UL+DL each
~50 Kbps each
~1 Mbps each
~5 Mbps DL each
~500 Kbps each
5–25 Mbps UL each — uplink-heavy
Input 6 — Criticality
What is the criticality level of the primary use cases?
Mission-critical deployments require coverage overlap and redundancy headroom — this increases the radio count upward and widens the range.
Input 7 — Primary device mobility
How do the primary devices move across the site?
Vehicle-mounted devices require handover overlap between cells — each radio must cover an area that overlaps with its neighbours at the boundary. This increases effective radio count by 10–25% depending on speed and site geometry.
📡
Your Sizing Estimate is Ready
Complete the form below to receive your full report by email.
Radio count range Coverage vs capacity breakdown Planning risk score Site-specific checklist
📧
Check your inbox
We've sent your sizing report link to
Click the link to view your full report. Check spam if you don't see it within 2 minutes.
TeckNexus · Private Network Radio Sizing & Planning Estimator

Private Network Radio Sizing Estimate

Coverage vs Capacity Breakdown
Planning Risk Score
Recommended Next Step
Site-Specific Planning Checklist
Assumptions & Methodology
What are the SLA requirements for your use cases?
The TeckNexus SLA Mapper translates your operational use cases into precise technical SLA requirements — latency, throughput, availability, QoS class, and technology implications — for vendor briefing and RFP specification.

How Many Radios Does Your Private Network Actually Need? A Planning-Grade Estimator for Budget Sizing Before RF Design

A site-type-aware estimator distinguishes coverage-driven from capacity-driven radio counts across industrial, mining, port, airport and utility environments — before a formal RF design is commissioned

Radio count is one of the first numbers a private network budget hinges on, and one of the most commonly mis-estimated — because generic indoor/outdoor coverage models don’t capture what actually drives radio density in industrial environments: ceiling height, container stack shadowing, crane geometry, electromagnetic interference near switchgear, or handover overlap for vehicles moving at speed. TeckNexus has launched a Private Network Radio Sizing & Planning Estimator, a vendor-neutral tool that produces a planning-grade radio count range calibrated to eleven distinct site types — not a single generic formula applied everywhere.

Site type, described operationally, is the primary driver

The estimator is explicit about a distinction that matters more than it first appears: select the operational description of a site, not its industry label. A pharmaceutical warehouse is a standard indoor facility for radio sizing purposes; a pharmaceutical plant with cleanrooms is a specialist case entirely. Once operational type is selected, the geometry inputs and coverage assumptions that follow are calibrated specifically to that environment — a large-span industrial facility, an airport terminal, airside apron, port quayside, container yard, open-pit mine, underground mine, utility substation, or wide-area outdoor site all produce meaningfully different radio-per-square-foot assumptions, even at identical floor area.

Ceiling height turns out to be the single most impactful variable after floor area for standard indoor sites — a 30ft ceiling in an open warehouse produces significantly more coverage per radio than a 10ft office ceiling at identical floor area, because radio propagation geometry, not floor space alone, determines the coverage a single radio can carry.

Why generic outdoor formulas fail in industrial environments

The site-type branches expose constraints a generic coverage calculator would miss entirely. Container yards suffer severe RF obstruction from stacked containers — each tier reduces effective radio coverage by roughly 15–25%, meaning the estimate for a four-high stack looks nothing like a two-high stack even across identical yard area. Port quayside coverage is linear rather than area-based, sized by berth length and coverage depth, with crane height relative to antenna placement determining whether coverage is straightforward or requires additional radios to work around crane shadow zones.

Open-pit mines carry their own geometry problem: pit walls both reflect signal and create shadow zones on lower benches, meaning coverage is typically sized per bench level for the lower pit, with wider coverage achievable on upper benches. Underground mines are treated as an entirely separate output category — leaky feeder (radiating cable), not standard base stations, is the technology, and the estimator’s output for underground sites is cable length and amplifier count rather than radio count at all. A professional design remains mandatory before procurement for any underground deployment regardless of what the estimator returns.

Utility substations and generation plants carry a distinct warning: high-voltage switchgear, transformers and power lines generate electromagnetic interference that measurably reduces effective radio coverage, and the estimator widens its range accordingly — while flagging that a site survey to characterise the EM noise floor is strongly recommended before formal design.

Spectrum band is the second-biggest lever on radio count

After site geometry, spectrum band choice is treated as the next most consequential input. mmWave (26/28GHz) requires substantially more radios for the same coverage footprint due to its short range, while licensed low-band spectrum under 1GHz needs far fewer radios, at the cost of lower per-radio capacity. CBRS/shared 3.5GHz remains the most common starting point in the US given its lack of licence fee, while licensed mid-band (3.7–4.2GHz) covers the primary enterprise allocation across Germany, the UK, Japan and much of APAC. Organisations that haven’t yet settled on a band are explicitly supported — selecting “unknown” simply widens the estimate range to reflect that genuine uncertainty, rather than forcing a premature commitment.

Where CBRS is selected, the estimator distinguishes GAA (General Authorised Access) from PAL (Priority Access Licence): GAA carries no licence cost but introduces interference risk in dense deployments, potentially requiring 20% capacity headroom, while PAL provides licensed priority access and interference protection — the estimator recommends PAL specifically for OT and mission-critical use cases, where interference risk isn’t an acceptable trade-off for the cost saving.

Capacity: where coverage-driven and capacity-driven estimates diverge

Device count and traffic profile drive the second half of the estimate — and the estimator is direct that uplink is typically the binding capacity constraint in industrial deployments, since cameras, sensors and AGV telemetry all generate uplink-heavy traffic that many enterprise network assumptions don’t account for. Traffic profiles are calibrated by workload type rather than generic device count: video-surveillance-heavy deployments are uplink-constrained in a way light IoT telemetry never is, while mission-critical OT — SCADA, safety systems, emergency communications — is modelled at near-100% concurrency with no tolerance for congestion, a materially different capacity posture than connected-workforce mobile broadband, where not all users are active simultaneously.

Mobility compounds capacity planning in a way that’s easy to underestimate: vehicle-mounted devices require handover overlap between cells, since each radio must cover an area that overlaps its neighbours at the cell boundary to maintain connection during handover — a requirement that increases effective radio count by 10–25% depending on speed and site geometry, purely to maintain seamless handover rather than to extend raw coverage.

From planning-grade estimate to procurement-ready design

The estimator is explicit about its own limits: it produces a planning-grade range for budget sizing and vendor conversations, not a substitute for formal RF design, site survey, or vendor engineering — and for mission-critical or complex deployments, that formal RF design step remains mandatory before procurement. What the estimator changes is the starting point of that process: entering budget conversations and vendor RFPs with a defensible, site-type-calibrated range rather than either a generic industry rule of thumb or a number supplied by the first vendor consulted.

Network planning teams, OT/IT architects and procurement teams sizing a private network deployment can take the free, vendor-neutral estimator directly and receive a full sizing report — including coverage versus capacity binding constraint, a planning risk score, and a recommended next step — in around six minutes.


Related Tool: Private Network Use Case-to-SLA Mapper
Once radio count is sized, confirm the SLA parameters — latency, availability, redundancy — driving that estimate are matched to your actual use cases, so the design and the specification stay aligned through procurement.

Partner Hubs

Download content, access intelligence tools, and hear from executives.

Partner Events

  • M360 ASEAN
  • FutureNet Asia 2026
Scroll to Top