June 25, 2026 · 5 min read · Technical Whitepapers
Thailand IoT SIM deployment requires NBTC-registered M2M SIMs on AIS/TrueMove/dtac. For a 10,000-device rollout, connectivity costs €0.30–€0.70/SIM/month plus €0.05 registration fee. eSIM and CMP API are required for remote provisioning.
Thailand IoT SIM deployment is the process of procuring and activating SIM cards for IoT devices that must comply with the NBTC's machine-to-machine (M2M) regulations and operate on Thai carriers AIS, TrueMove, or dtac. For a 10,000-device fleet, connectivity costs typically range from €0.30 to €0.70 per SIM per month (based on published carrier rate cards for 10–50 MB/month plans), plus a one-time NBTC registration fee of about €0.05 per SIM. Devices using 3G/4G/5G bands must support Band 1 (2100 MHz), Band 3 (1800 MHz), and Band 40 (2300 MHz TDD) for optimal carrier coverage.
The NBTC (National Broadcasting and Telecommunications Commission) mandates that all IoT SIMs used for M2M services in Thailand must be registered with the device's IMEI or device identifier. Previously, unregistered consumer SIMs could be used in IoT gateways, but as of 2023, carriers enforce strict M2M APN policies. This changes procurement in two ways: (1) you cannot use standard consumer data SIMs without risking service termination after 90 days; (2) each SIM must be tied to a fixed device identity, making eSIM remote provisioning mandatory for large-scale deployments. For a 10,000-unit rollout, manual SIM swapping would cost €0.10–€0.20 per unit in logistics, versus €0.02 per eSIM profile download via a CMP platform API.
A utility deploying 50,000 smart meters in Bangkok needs NBTC-registered M2M SIMs with static IP for backhaul to the head-end system. Global IoT SIM with eSIM allows switching between dtac and TrueMove based on signal strength. Use RESTful M2M API for automated SIM profile activation via the CMP platform. Catalog pricing applies if data usage is under 20 MB/month per meter; above that, a project quote is needed for custom APN security.
A logistics company with 2,000 GPS trackers across Thailand requires low-latency (<200 ms) communication on AIS's 4G network. Each tracker sends 500 bytes every 30 seconds (approx. 1.4 GB/month per device). This volume exceeds typical catalog pricing tiers (usually capped at 50 MB), so a project quote is required. eSIM enables remote carrier selection to avoid roaming surcharges. The CMP platform must support real-time API for usage alerts.
Factory automation using Siemens or Advantech gateways with LTE Cat 1 modules. These gateways require a fixed APN with private IP and firewall rules. Only project quotes from carriers or aggregators can deliver this static configuration. eSIM with SM-DP+ integration allows secure profile updates without physical access.
| Carrier | Supported Bands (Key) | M2M APN Required? | eSIM Support (Profile Download) | Monthly Data Tier (10,000 units) | NBTC Registration Fee per SIM | API Available for Activation | Typical Pricing per SIM/Month (€) |
|---|---|---|---|---|---|---|---|
| --------- | ------------------------ | ------------------- | --------------------------------- | ---------------------------------- | ------------------------------- | ------------------------------ | ----------------------------------- |
| AIS | B1, B3, B40, B5 (LTE) | Yes – static IP possible | Yes – via SM-DP+ | 10 MB / 50 MB / 500 MB | THB 2 (€0.05) | RESTful M2M | €0.30 (10 MB) – €2.10 (500 MB) |
| TrueMove | B1, B3, B40, B8 | Yes – dynamic IP only | Yes – via SM-DP+ | 10 MB / 50 MB / 300 MB | THB 2 (€0.05) | RESTful M2M | €0.25 (10 MB) – €1.50 (300 MB) |
| dtac | B1, B3, B40, B7 | Yes – static IP possible | Planned Q2 2025 | 10 MB / 30 MB / 200 MB | THB 2 (€0.05) | RESTful M2M (limited) | €0.20 (10 MB) – €1.20 (200 MB) |
| Global IoT SIM aggregator | Multi-band 4G/5G (Roaming) | No – uses dynamic IP | Yes (any carrier via GSMA eSIM) | 10 MB / 100 MB / 1 GB | N/A (registered via host country) | Full RESTful M2M + CMP | €0.50 (10 MB) – €3.50 (1 GB) |
Choose a local carrier SIM (AIS, TrueMove, dtac) when devices are permanently deployed inside Thailand and bandwidth is predictable (<50 MB/month per device). Catalog pricing is sufficient for these cases because the data usage falls within standard M2M data plans. Use a Global IoT SIM aggregator (e.g., with eSIM and roaming agreements) only if devices travel across borders or if you need a single CMP platform for multiple APAC countries. A project quote is required when any of the following conditions are true: static IP with firewall rules, custom APN with dedicated M2M gateway, data usage >200 MB/month per device, or integration of the CMP API with your existing ERP (SAP/Oracle). For fleets >5,000 units, always request a project quote even for catalog-eligible tiers because volume discounts (15–30%) are typically not published.
LTE Cat 1 module (Quectel EG91-EX): €12–€18 per unit. eSIM chip (optional): add €0.30 – €0.50. For 10,000 units, module BOM: €150,000 average.
Local carrier M2M SIM, 10 MB/month: €0.30/SIM/month × 36 months × 10,000 = €108,000. NBTC registration: €0.05 × 10,000 = €500. Total connectivity: €108,500.
CMP platform (e.g., EMnify, Aeris) typically charges €0.02–€0.05 per SIM per month for basic usage monitoring and API access. For 10,000 SIMs × 36 months × €0.03 = €10,800.
SIM insertion and device configuration: €0.20 per unit (one-time) = €2,000. Ongoing support: 5% annual hardware maintenance = €7,500/year. Total 3-year maintenance: €22,500.
If using a global roaming SIM (€1.50/SIM/month) instead of local M2M SIM (€0.30) for 10,000 devices over 3 years, the extra cost is (1.50-0.30)×12×3×10,000 = €432,000. The local SIM deployment pays for itself in 14 months, making the NBTC registration overhead negligible.
Catalog pricing (published rate card) suffices for deployments that meet ALL criteria: <200 MB/month per device, dynamic IP only, no custom APN, single carrier (not multi-carrier aggregation), and fleet size <5,000 units.
A project quote is mandatory when deploying >5,000 SIMs (volume negotiations), requiring static IP or custom APN, using eSIM with remote provisioning across multiple carriers, or needing integration of the CMP RESTful M2M API into your existing IoT platform. In these cases, expect a response with a 30–60 day lead time including NBTC registration paperwork.