Tools

IoT data usage calculator

Estimate the monthly data usage of your device and your whole fleet from three things you actually know: message size, how often it sends, and the protocol. Each protocol's overhead (headers, TLS, keepalives) is an orientative engineering estimate — meant for sizing a plan, not for billing.

Per device

0.47MB/month

Messages: 0.21 MB · Keepalives: 0.26 MB

Whole fleet

23.7MB/month

290 bytes on air per message (payload + headers)

Which plan fits?

At a few MB per month, pay-as-you-go is usually the most efficient: you pay exactly for the data that crosses the network, with no bundle quota you'd never use up.

Where the numbers come from

Every message your device sends travels with baggage: IP and transport headers, and on secure protocols the cost of encryption. With UDP the overhead is around 28 bytes per datagram; CoAP adds a few more. MQTT keeps its connection open, so each publish pays modest headers — but the periodic keepalive adds up too (we include one every 15 minutes). HTTPS is the extreme case: if the device opens a fresh connection per send, the TLS handshake can weigh several KB — orders of magnitude more than a typical telemetry payload. That's why two firmwares with the same sensor can differ 50× in usage, and why it's worth estimating before picking a plan. Figures are orientative: retransmissions, DNS resolution and OTA updates are not included.

Frequently asked questions

How much data does a typical IoT device use?
It depends almost entirely on the sending pattern and protocol. A sensor publishing 200 bytes hourly over MQTT uses on the order of 0.2–0.5 MB per month; a GPS tracker reporting every 30 seconds can exceed 25 MB; and a misconfigured firmware opening a new HTTPS connection per send can multiply expected usage by 20. This calculator gives you the order of magnitude with your own parameters.
Why does HTTPS use so much more than MQTT or CoAP?
Connection establishment: a full TLS handshake exchanges certificates and keys and can cost 3–6 KB, plus the TCP handshake. If the connection is reused (keep-alive or session resumption) that cost amortizes across many messages; if the device opens and closes it every time, it pays the full price per send. MQTT holds a persistent connection and CoAP runs over connectionless UDP, which is why their per-message overheads are far smaller.
Does the calculator include retransmissions and OTA updates?
No. The figures cover regular telemetry traffic (messages plus keepalives). Retransmissions due to poor coverage, DNS resolution, NTP sync and OTA firmware updates come on top; in real deployments it's prudent to add a 20–30% margin over the estimate, more if the radio link is weak.
How do I choose between pay-as-you-go and data bundles?
Quick rule: with low or irregular usage (sensors, alarms, sparse telemetry), pay-as-you-go avoids paying for a bundle you don't consume; with steady mid-to-high usage (video, frequently-reporting trackers, routers), a monthly bundle lowers the cost per MB. The calculator places you in a range and links to both plans so you can compare with your numbers.

Put the estimate to the test with real SIMs

Test kit for €15: measure your device's real usage in our portal before sizing the fleet.