IoT Sensor Network Calculator
Sensor count and gateway placement from coverage area.
About this calculator
This calculator sizes an IoT sensor deployment by working backward from coverage area to hardware count. Each sensor's effective coverage is modeled as a circle (π × range²) scaled by a 0.785 packing-efficiency factor, which accounts for the overlap unavoidable when tiling circular coverage zones across a rectangular area — dividing total area by that per-sensor coverage gives the base sensor count, which is then multiplied by your redundancy factor (1.2 = 20% extra sensors for reliability/overlap). Gateway count takes the larger of two independent constraints: how many gateways are needed just to handle the sensor capacity limit (sensors ÷ max-sensors-per-gateway), and how many are needed to physically cover the area given the gateway's own range, using the same circular-packing formula.
Network hop count depends on topology: star topology is always 1 hop (direct to gateway), tree topology estimates hops as the log₂ of sensor count (a rough proxy for hierarchical depth), and mesh topology estimates average hops as the square root of the area divided by twice the sensor range — modeling how far a message must relay across a multi-hop mesh. Mesh throughput factor (1/hops) reflects that a shared-channel mesh network's usable bandwidth degrades roughly in proportion to hop count, since each retransmission consumes airtime. This is a planning-level estimate, not a full RF propagation survey — it doesn't account for obstacles, terrain, or interference, so treat the sensor and gateway counts as a starting point for a real site survey.
Inputs
Results
Sensors needed
6
How to Use This Calculator
- Enter the total coverage area in square meters and effective sensor range in meters.
- Select a network topology: 0=star, 1=mesh, 2=tree.
- Set max sensors per gateway and gateway communication range in meters.
- Enter redundancy factor (1.2 = 20% extra sensors) and unit costs for sensors and gateways.
- Read Sensors needed, Gateways needed, and Total hardware cost to plan your deployment.
How the result changes with Sensor range (m)
| Sensor range (m) | Sensors needed |
|---|---|
| 15 | 23 |
| 23 | 10 |
| 45 | 4 |
| 75 | 2 |
What each input means
- Coverage area (m²)
- Total area to cover with sensors in square meters. 10,000 m² = 1 hectare.
- Sensor range (m)
- Effective sensing radius per sensor in meters.
- Topology (0=star,1=mesh,2=tree)
- Network topology: 0 = star (direct to gateway), 1 = mesh (multi-hop), 2 = tree (hierarchical).
- Max sensors/gateway
- Maximum devices a single gateway can support. LoRa: 500+, Zigbee: 65K, BLE: 7-20.
- Gateway range (m)
- Gateway communication range in meters. WiFi: 50-100 m, LoRa: 2-15 km.
- Redundancy factor
- Sensor over-provisioning for reliability. 1.0 = no redundancy, 1.2 = 20% extra.
- Sensor unit cost ($)
- Cost per sensor node including housing and installation.
- Gateway unit cost ($)
- Cost per gateway/concentrator including installation.
What each result means
- Sensors needed
- Total sensor nodes required to cover the area with redundancy.
- Gateways needed
- Minimum gateway count for capacity and coverage.
- Avg network hops
- Average hops from sensor to gateway (1 for star topology).
- Sensors per gateway
- Average sensor-to-gateway ratio in the deployment.
- Total hardware cost ($)
- Combined cost of all sensors and gateways.
- Throughput factor
- Effective per-node throughput as fraction of link rate (mesh overhead).
How this is calculated
Worked example, using the default values
- Identify Input Parameters4 parametersCoverage area (m²) = 10000, Sensor range (m) = 30, Topology (0=star,1=mesh,2=tree) = 0, Max sensors/gateway = 50 = 8 input(s) provided
- Calculate Sensors neededSensors needed6 = 6
- Calculate Gateways neededGateways needed1 = 1
- Calculate Avg network hopsAvg network hops1 = 1
Engine last updated . Checked against 2 independently-derived tests — how we verify calculators. Built by Paul Gunder, a software engineer, not a licensed financial, medical, or legal professional.
Frequently Asked Questions
Why is the 0.785 packing factor applied to the sensor coverage circle?
A sensor's theoretical coverage is a circle (π × range²), but you can't tile circles across a flat area with zero gaps or overlap. The 0.785 factor represents the realistic packing efficiency when circular coverage zones are arranged to cover a rectangular area without leaving gaps, so the effective per-sensor coverage used in the sensor-count formula is smaller than the raw circle area.
Why does the calculator take the larger of two gateway counts instead of just one formula?
Gateway count is constrained by two independent limits: how many gateways are needed to handle the total sensor capacity (sensors divided by max-sensors-per-gateway), and how many are needed to physically cover the area given the gateway's own range. Whichever constraint demands more gateways wins, since satisfying only the lower number would leave either capacity or coverage insufficient.
How does network topology change the estimated hop count?
Star topology is always 1 hop since every sensor talks directly to a gateway. Tree topology estimates hops as the log base 2 of total sensor count, a rough proxy for how deep a hierarchical tree gets as it fans out. Mesh topology estimates average hops as the square root of the coverage area divided by twice the sensor range, modeling how far a message must relay hop-by-hop across a multi-hop network.
Why does mesh topology reduce my effective throughput even though it doesn't need more gateways?
The mesh throughput factor is calculated as 1 divided by average hop count, reflecting that on a shared-channel mesh network, each additional hop consumes airtime for retransmission, reducing usable bandwidth per node roughly in proportion to how many hops a message must traverse. A mesh with an average of 4 hops effectively delivers only a quarter of the link's raw throughput to end nodes.
Related Calculators
The questions that sit next to this one — chosen by subject, including calculators filed under a different category.
LPWAN Coverage Calculator
LoRa/Sigfox range from gateway height and environment.
IotIoT Power Budget Calculator
Battery life from sensor duty cycle and transmission frequency.
Telecom InfrastructureNetwork Redundancy Cost Calculator
Additional cost for N+1 and ring redundancy.
IotIoT Data Volume Calculator
Data storage from sensor count, sample rate, and retention.
Military LogisticsDeployment Cost Calculator
Total deployment cost from personnel, duration, and equipment weight.
More in Technology & Computing.