GSMA TAC Database: How It Works, Access Methods & Use Cases
Everything about the GSMA TAC database: allocation process, data structure, API access methods, and professional use cases for operators and network engineers.
The GSMA TAC Database is the authoritative global registry that maps every Type Allocation Code to a specific device manufacturer, model, and set of technical capabilities. For telecom professionals, understanding how this database works β and how to access it β is fundamental to device identification, network planning, and regulatory compliance.
This article covers the TAC allocation process, the data structure behind each record, practical access methods, and the professional use cases that rely on TAC data every day.
What Is the GSMA TAC Database?
The GSMA (GSM Association) manages the global TAC database as part of its IMEI allocation framework. A TAC (Type Allocation Code) is the first 8 digits of any IMEI number, and it uniquely identifies the manufacturer and model of a mobile device.
The database contains hundreds of thousands of registered TACs, covering every commercially available device that connects to a cellular network β from flagship smartphones and tablets to IoT modules, wearables, and vehicle telematics units.
Each TAC record maps to a set of structured attributes:
- Manufacturer (brand name and reporting body)
- Model name (marketing name and internal model number)
- Device type (smartphone, tablet, dongle, IoT module, wearable, router)
- Radio capabilities (supported frequency bands, RATs)
The GSMA TAC Database serves as the single source of truth for any entity that needs to identify a device from its IMEI prefix. Mobile operators, regulators, law enforcement, and device management platforms all depend on the accuracy of this registry.
TAC Allocation Process
Before any mobile device can be sold commercially, its manufacturer must obtain a TAC from the GSMA through the IMEI Allocation and Management service. The process works as follows:
-
Manufacturer application. The device manufacturer (or a Reporting Body acting on its behalf) submits an allocation request to the GSMA. This request includes device specifications, intended markets, and certification documentation.
-
Certification requirements. The GSMA requires evidence that the device has passed relevant type approval or certification (e.g., GCF, PTCRB, or regional regulatory bodies). This ensures that only standards-compliant devices receive a TAC.
-
TAC block assignment. Upon approval, the GSMA assigns one or more TAC values to the device model. Each TAC corresponds to a block of one million possible serial numbers (the SNR portion of the IMEI).
-
Multiple TACs per model. A single device model can receive multiple TACs. This is common when regional variants exist (different LTE band configurations), when hardware revisions are introduced, or when production volumes exceed the serial number range of a single TAC block.
The allocation process typically takes a few business days once all documentation is in order. Manufacturers with existing accounts and established relationships with the GSMA can often streamline the process for new device variants.
TAC Data Structure
Each TAC record in the database follows a structured schema. The core fields are:
| Field | Description | Example |
|---|---|---|
| TAC | 8-digit Type Allocation Code | 35456712 |
| Brand | Manufacturer or brand name | Samsung |
| Marketing Name | Commercial device name | Galaxy S25 Ultra |
| Model Number | Internal model identifier | SM-S938B |
| Device Type | Category classification | Smartphone |
| Radio Interface | Supported RATs (GSM, UMTS, LTE, NR) | LTE, NR |
| Operating System | Device OS (when available) | Android |
Beyond these core fields, enriched TAC databases may include:
- LTE band support (e.g., B1, B3, B7, B20, B28)
- NR band support (e.g., n1, n28, n41, n77, n78)
- Chipset information (e.g., Qualcomm Snapdragon 8 Elite, MediaTek Dimensity 9400)
- Carrier Aggregation combinations supported by the device
- MIMO capabilities (2x2, 4x4)
The chipset field is particularly valuable for RF engineers and network diagnostics professionals, since it determines DIAG log compatibility, UE capability decoding behavior, and modem-level feature support.
How to Access TAC Data
There are several ways to query TAC information, each with different trade-offs in terms of coverage, cost, and data quality.
GSMA IMEI Database (Official)
The GSMA offers direct access to its TAC database through the IMEI Database service, available to GSMA member operators and approved organizations. This is the most authoritative source, but it requires a paid subscription and is primarily designed for operators, regulators, and large enterprise customers.
Third-Party TAC Databases
Various third-party providers maintain TAC lookup services with varying levels of coverage, accuracy, and freshness. Quality differs significantly between providers β some databases lag months behind new device launches, and many lack enriched fields like chipset or band support data.
HiCellTek TAC Lookup API
The HiCellTek TAC Lookup API provides a free REST endpoint for querying TAC data. Our database covers 250,000+ devices with chipset enrichment, band support details, and regular updates as new devices are allocated TACs.
You can also use our online TAC Lookup tool for instant browser-based queries β no API key required.
Key advantages of the HiCellTek TAC database:
- Chipset enrichment: Qualcomm, MediaTek, Samsung Exynos, and other chipset families are mapped to TACs
- Band-level detail: LTE and NR band support per device
- REST API: Simple JSON responses, easy to integrate into existing tools and workflows
- Free tier: No cost for standard lookup volumes
Professional Use Cases
TAC data serves a wide range of professional applications across the telecom industry.
Mobile Operators
Operators rely on TAC data for Equipment Identity Register (EIR) management, verifying that devices connecting to their network are type-approved and not blacklisted. TAC lookups also support network planning by profiling the device population on the network β identifying the mix of 4G-only vs. 5G-capable terminals, for example, informs capacity planning and frequency refarming decisions.
RF Engineers and Network Optimization
For RF engineers, TAC data reveals the UE capabilities associated with a given device model. Knowing the chipset and supported band combinations is essential for interpreting drive test data, diagnosing handover failures, and understanding why specific devices behave differently under the same network conditions. The TAC lookup is often the first step in qualifying a device for field diagnostic work.
MDM and Enterprise Mobility
Mobile Device Management (MDM) and Enterprise Mobility Management (EMM) platforms use TAC data for device compliance checks and fleet inventory management. IT administrators can verify that enrolled devices meet corporate security requirements (e.g., minimum OS version, approved manufacturer) by resolving the TAC against the database.
Second-Hand Device Market
Buyers and resellers in the pre-owned device market use TAC lookups to verify device authenticity before purchase. A TAC that resolves to a different model than what is advertised is a strong indicator of a counterfeit or re-labeled device.
Regulators and Law Enforcement
National regulators maintain Central Equipment Identity Registers (CEIRs) that rely on TAC data to detect counterfeit devices, enforce import regulations, and support stolen device blacklisting. The GSMA TAC database is the foundational data source for these systems.
Limitations and Future Developments
While the GSMA TAC Database is comprehensive, it has inherent limitations that professionals should understand.
TAC identifies the model, not the individual device. A TAC lookup reveals the manufacturer and model but cannot distinguish between two units of the same model. Individual device identification requires the full IMEI number, including the serial number portion.
Data freshness. There is an inherent lag between a device receiving its TAC allocation and that data propagating to third-party databases. Very recently launched devices may not appear in all TAC lookup services immediately.
eSIM does not change the TAC process. The shift toward eSIM does not affect TAC allocation β the TAC is tied to the device hardware, not the SIM form factor. Devices with eSIM-only configurations still receive TACs through the standard GSMA allocation process.
IMEI 2.0 discussions. The GSMA has ongoing discussions around evolving the IMEI framework to accommodate the growing volume of IoT devices and new device categories. While no breaking changes to the TAC structure have been finalized, professionals should monitor GSMA working group publications for updates to the allocation scheme.
Conclusion
The GSMA TAC Database is a critical piece of telecom infrastructure that underpins device identification across the entire mobile ecosystem. Whether you are an operator managing an EIR, an RF engineer diagnosing field issues, or an enterprise IT team managing a device fleet, understanding how TAC data is structured and accessed will improve your workflow.
Explore the HiCellTek TAC Lookup to query our enriched database of 250,000+ devices, or integrate the TAC API directly into your tools and platforms.
Founder of HiCellTek. 15+ years in telecom, operator side, vendor side, field side. Building the field tool RF engineers deserve.
Request a personalized demo of HiCellTek β 2G/3G/4G/5G network diagnostics on Android.