Uzbekistan SMS Market

📦v1.0.0📅2026-04-28🔄Updated 2026-04-28👤Admin Team
use-casesmarket-and-positioningmessage-center

Uzbekistan SMS Market

Uzbekistan is a mobile-first market of 36+ million people with five national mobile network operators and a growing ecosystem of SMS aggregators serving banks, e-commerce platforms, government services, and content providers. A2P (Application-to-Person) SMS remains the dominant channel for authentication, transaction confirmations, and marketing in a market where smartphone adoption is high but messaging app fragmentation makes SMS the lowest-common-denominator delivery channel.


Mobile Network Operators

Uzbekistan has five active national MNOs as of 2026:

OperatorNotes
Beeline Uzbekistan (VEON)Market leader by subscribers (~8.2M); part of the VEON international group
UcellMajor operator; well-established A2P SMS routing
Mobiuz (UMS — Universal Mobile Systems)~7.8M subscribers; undergoing international privatization process (Rothschild & Co appointed as lead advisor, 2025)
Uzmobile (Uztelecom)State-owned brand of the national fixed-line and mobile operator
HumansSmaller operator; positioned as digital-first brand

Sources: Opensignal Uzbekistan Report, Sept 2025; Developing Telecoms, Mobiuz privatisation

All major operators support SMPP connectivity for bulk A2P SMS traffic. Competitive differentiation is shifting from price to network quality and 5G deployment in Tashkent and other major cities.


SMS Aggregators

The majority of enterprise A2P SMS in Uzbekistan flows through local aggregators rather than direct carrier connections. Aggregators handle the complexity of interconnecting with multiple operators, managing sender name registration, and providing a single integration point for businesses.

Eskiz.uz

One of the most widely-used local SMS aggregators. Offers:

  • Bulk SMS sending via REST API
  • OTP/authentication flows via API
  • Per-message pricing at approximately 50 UZS/SMS (as of 2026) with no monthly minimums
  • Sender name registration on behalf of customers for the major operators

Source: Eskiz.uz — SMS newsletter service

PlayMobile

Another established aggregator in the Uzbekistan market. Serves enterprise clients requiring high-volume A2P delivery across multiple operators.

Other Aggregators

The market includes additional local and regional providers (SMS.uz, and resellers of global aggregators such as D7 Networks and EasySendSMS). Global CPaaS providers (Twilio, Vonage) also publish Uzbekistan pricing but route through local intermediaries, typically at higher cost-per-message compared to direct local aggregator agreements.


Regulatory Context

SMS messaging in Uzbekistan is regulated under the framework of the Ministry of Digital Technologies (Минцифры — Mintsifry). Key regulatory elements affecting A2P SMS:

Sender name (Sender ID) registration: Marketing and service SMS traffic requires pre-registered sender names. Carriers enforce this at the SMPP level — unregistered sender names are filtered or blocked on delivery. The registration process involves submitting business documentation to the carrier (directly or via aggregator).

Content restrictions: Regulations restrict unsolicited commercial messages (spam). Operators maintain opt-out mechanisms.

Local routing preference: For high-volume enterprise traffic, regulators and operators favor direct aggregator agreements over purely international routing — which creates a demand for on-premise infrastructure that integrates with local SMPP endpoints.

Data localization: Uzbekistan's data protection framework (О персональных данных, Law No. ZRU-547) imposes requirements on personal data processing. SMS platforms handling subscriber phone numbers may need to ensure data stays within Uzbekistan's jurisdiction — a natural fit for self-hosted deployments.


Why Self-Hosted Matters in Uzbekistan

The Uzbekistan market has structural factors that favor on-premise SMS infrastructure over cloud SaaS:

  1. Direct carrier integration — telecoms and large enterprises often have direct SMPP agreements with operators. A self-hosted SMS gateway connects to these existing agreements without routing through international cloud services.

  2. Data sovereignty concerns — banks, government agencies, and telecoms operating in Uzbekistan cannot route subscriber data through foreign cloud infrastructure due to local data localization requirements.

  3. Local aggregator independence — a business that runs its own SMPP infrastructure (core + proxy) alongside Message Center is not locked into any single aggregator's pricing, availability, or API design.

  4. Custom adapter for local protocols — some Uzbekistan operators and aggregators have non-standard SMPP configurations or proprietary protocol extensions. Message Center's SKU 3 custom adapter option allows building an integration layer without modifying the standard SMS Core.


Target Segments in Uzbekistan

SegmentSMS Use CasesMessage Center Fit
Banks and NBFIsOTP, transaction alerts, balance notificationsTrigger mode; strict audit trail; sender registration workflow
E-commerce platformsOrder confirmations, delivery notifications, promotionsScheduled/spread mode; large lists
Government digital servicesCitizen notifications, UZIMEI interactionsAir-gapped deployment; data localization
Telecoms (MNOs)Subscriber notifications, network alertsSelf-hosted; direct SMPP; high volume
SMS aggregatorsManaged platform for enterprise clientsMulti-tenant workspaces (one per client)
Content providers / VASSubscription confirmations, content deliveryContent provider use case

Competitive Position in Uzbekistan

For Uzbekistan-based SMS aggregators building a managed platform for their enterprise clients, Message Center's SKU 3 (Custom Adapter) is the highest-value offering:

  • White-label the web interface under the aggregator's brand
  • Each enterprise client gets an isolated workspace with their own SMPP sender configuration
  • The custom adapter routes through the aggregator's own carrier connections — no change to the existing SMPP infrastructure
  • Enterprise clients get a full moderation/compliance workflow without the aggregator needing to build one

This positions the aggregator as a platform provider rather than a raw API vendor — significantly higher retention and margin than bare API access.


Next Steps