How much 4G data will this deployment use?
Estimate monthly cellular data for a Wiman gateway based on tag count, polling interval and payload size. Pick a SIM plan with confidence before you order hardware.
How this is calculated
The estimator combines two streams of traffic: the regular polling uploads and the occasional TLS handshake when the cellular link recycles.
cyclesPerDay = 86 400 / pollIntervalSec
payloadBytesPerCycle = tagCount * payloadBytesPerTag
totalBytesPerCycle = payloadBytesPerCycle * (1 + overheadPct / 100)
reconnectsPerDay = 86 400 / reconnectIntervalSec
reconnectBytesPerDay = reconnectsPerDay * tlsHandshakeBytes
totalBytesPerDay = (totalBytesPerCycle * cyclesPerDay) + reconnectBytesPerDay
MB per day = totalBytesPerDay / (1024 * 1024)- Payload bytes per tag already includes a JSON key, value and delimiter — a Wiman CSV v2.3 frame is closer to 14-24 B per tag, JSON v3.2 is 28-40 B.
- Overhead covers MQTT topic + headers + the TLS record layer. 15-22% is typical on a well-tuned link.
- Reconnect cost dominates on flaky cells. If you see real consumption above the estimate, the SIM is probably renegotiating TLS more often than this assumes.
- Numbers ignore OTA firmware downloads, remote-access tunnels and platform back-channels. Add a safety margin of ~15% for those.
Need a tighter number? Send us your tag list and we will model it against the exact firmware build you would deploy.
Pick a plan that won't throttle in month two
Indian IoT data plans are usually capped — once you cross the bundle, the connection drops to 64 kbps or worse. The math here gives you a defensible number to take to your operator before the deployment ships.
Need help sizing a deployment?
Our engineers will validate the numbers against your real device list and recommend the right gateway.