ICCID and IMSI: A Complete Practical Guide in Simple Terms

Introduction

If you're working with mobile proxies, modem farms, IoT devices, or simply want to understand how your SIM card is identified on the network, knowing ICCID and IMSI is essential. These two identifiers are the foundation of addressing and routing at the SIM and mobile network levels. In this article, we’ll break them down into simple terms: what ICCID and IMSI are, how they differ, how to read them correctly, where they are used in network scenarios, and why proper handling speeds up troubleshooting, reduces downtime risks, and gives you a strategic advantage. We'll start with definitions, then delve into their structures and standards, followed by practical methods, checklists, and real-world case studies. You’ll find a handy reference table for ICCID and IMSI structures, as well as internal links to sections on MCC and MNC for quick reference. It’s important to note: we focus on legal network and infrastructure practices, without discussing methods for bypassing restrictions or illegal scenarios.

What is ICCID?

ICCID (Integrated Circuit Card Identifier) is a global number of the card (for SIM, eSIM profile, or iSIM) defined by the ITU-T E.118 standard. Think of it as the "serial number of a payment card," just for SIMs. ICCID usually contains 19–20 digits, is printed on the SIM card plastic, and is stored in the card’s application (EF ICCID). Its purpose is to uniquely identify the carrier, which helps networks and operating systems understand what profile it is, which issuer it belongs to, and how to manage its inventory. Key properties of ICCID: it is not used for authenticating the subscriber in radio access; it can uniquely differentiate eSIM profiles (one chip can have multiple ICCIDs, each for a different profile); it is involved in lifecycle management processes of profiles (provisioning, transfer, deactivation).

What is IMSI?

IMSI (International Mobile Subscriber Identity) is an international subscriber identifier of up to 15 digits, defined by 3GPP and used for registering a device on the carrier's network. IMSI is stored in the SIM and is involved in authentication at the core network via algorithms (e.g., MILENAGE, COMP128 in older implementations) and keys Ki/OPc. IMSI acts as the “subscriber's passport” for the network: it helps HLR/HSS/UDM understand who your client is, which operator they belong to, and what services are available to them. Important note: IMSI is not printed on the plastic (usually), but is read programmatically and processed at the core network level. IMSI is used during the Attach/Registration procedure, PLMN selection, and roaming.

How ICCID Differs from IMSI

In short: ICCID is about the card; IMSI is about the subscriber. ICCID aids logistics, inventory management, and SIM/eSIM/iSIM profile management. IMSI assists the network in authenticating and servicing the subscriber. In the eSIM era, this distinction becomes even clearer: one chip can contain multiple profiles with different ICCIDs and IMSIs, where switching profiles changes the IMSI (and, consequently, the operator and plan), even though the physical device is the same.

How They Are Read and What They Encode

Both ICCID and IMSI are numerical strings with a clear internal structure.

MCC — Mobile Country Code

A three-digit code for the country/territory of the mobile network according to ITU-T standards. MCC determines the geographical affiliation of the operator and is the first part of the IMSI. For example, 250 is Russia, 262 is Germany. MCC does not always match the country dialing code.

MNC — Mobile Network Code

A two- or three-digit code for the network (operator) within the MCC. In the IMSI, it follows the MCC. The combination of MCC+MNC forms the PLMN ID — the identifier for the public mobile network, which the device uses to select the operator during registration.

IMSI Structure

• MCC (3 digits): country.
• MNC (2–3 digits): operator.
• MSIN (remaining 9–10 digits): subscriber number on the operator's network.

Totaling up to 15 digits. Example: 250 01 1234567890 — Russia, operator with MNC 01, subscriber 1234567890.

ICCID Structure

• MII (Major Industry Identifier, always 89 for telecom): 2 digits.
• Issuer Identification Number (IIN): includes the country code (E.164) and SIM issuer code. Length varies, usually up to 7 digits after 89.
• Individual Account Identifier: a unique card/profile number, length varies so the total length is 19–20 digits.
• Luhn Check Digit: 1 digit.

Example: 89 7 01 2345 678901234 5, where 89 is MII, “7 01 2345” is part of the IIN, “678901234” is the individual number, “5” is Luhn.

Why It Matters When Working with Mobile Proxies

In mobile proxies, ICCID and IMSI are the control points for managing the fleet of SIMs and modems. They allow you to: accurately match slots, profiles, and numbers; automate inventory and resource management; diagnose registration issues faster (using MCC/MNC and roaming); build matrices for "modem — profile — operator — service area"; manage eSIM profiles without physical access; document legally significant attributes of cards for audits. Services like mobileproxy.space utilize these identifiers to add understandable tags to telemetry, segment resources by operators/regions, and minimize downtime during profile switches.

Practice 1: SIM Inventory and Modem Fleet Management

Task

To create a transparent accounting system: which modem, which SIM/eSIM profile, which operator, in what status. The goal is predictability, fast replacement, and less downtime.

ICCID-Centric Framework

1. Collect ICCID from all SIMs (via scanner, readings from the modem, from MDM/SM-DP+ for eSIM).
2. Link ICCID to the modem slot, MSISDN number (if available), device serial number (IMEI), and inventory object (rack, location).
3. Add IMSI and decode MCC/MNC for operator and country.
4. Assign statuses (active, testing, reserved, disposal) and SLA categories (critical/non-critical).
5. Sync with billing: rate, limits, next billing date.

Step-by-Step Guide

1. Export data from modems (AT commands: AT+CCID for ICCID, AT+CIMI for IMSI; commands vary by chipset).
2. Normalize formats (remove spaces, letters F from BCD, check Luhn on ICCID).
3. Build a registry in a table with columns: Date, Modem (IMEI), Slot, ICCID, IMSI, MCC, MNC, Operator, Location, Status, Rate.
4. Add alert rules: “SIM not registered for N minutes,” “MCC/MNC changed,” “reconnections over X/hour.”
5. Define the lifecycle: acceptance — commissioning — migration — decommissioning/disposal.

Quality Control Checklist

• Is ICCID unique? Duplicate checks.
• Is IMSI readable in each modem? Any exceptions for equipment?
• Is the MCC/MNC mapping to the operator correct? Verification against the directory.
• Does Luhn pass for ICCID?
• For eSIM: is there a link between ICCID and chip EID and SM-DP+ profile?

Practice 2: Network Diagnosis using MCC/MNC and IMSI

Task

Quickly understand why the modem is not registering, frequently disconnecting, or experiencing slow speeds.

PLMN Detective Method

1. Retrieve IMSI and identify MCC/MNC. Ensure the device is attempting to register in its "own" network or allowed roaming.
2. Compare the selected PLMN with the modem's preferred list (PRL/PLMN list).
3. Check RAT/capability ranges: does the SIM/plan and modem support the required LTE/NR bands.
4. Evaluate TAC/Cell ID and statistics on re-registrations; if increasing—look for interference or network overload.
5. Test an alternative eSIM profile (if available), compare KPIs.

Practical Tips

• Differences in MNC length (2 vs 3) are critical: errors on a zero can lead the device to "disappear" into a non-existent network.
• If IMSI indicates "roaming," but the plan is "home," check PRL and forbidden PLMN list.
• Regularly update the PLMN directory: in 2026, operators are actively changing MNCs due to consolidations and 5G SA deployments.

Practice 3: Automation, API, and Telemetry

Task

Minimize manual operations: everything through APIs, alerts, and monitoring dashboards.

Architectural Approach

• Data Collection: modem drivers or agents collect ICCID/IMSI, RSSI/RSRP/RSRQ, Cell ID, TAC, RAT type (LTE/NR), registration errors.
• Enrichment: directory services translate IMSI to MCC/MNC/operator.
• Storage: time-series for metrics and relational for inventory.
• Alerting: triggers based on SLA (registration, jitter, losses).
• Profile Management: for eSIM — through SM-DP+/LPA API, for physical SIM — orchestrator for replacements/rollovers.

API Pipeline Pseudocode

POST /telemetry { imei, iccid, imsi, rssi, rsrp, rsrq, rat, cell_id, tac, ts } -> Enrich (mcc, mnc, operator) -> Store SQL(iccid, imsi, mcc, mnc, operator, slot, status) + TSDB(metrics) -> Alerts (rules) -> Dashboard

Automation Checklist

• Normalization of ICCID/IMSI and Luhn validation on input.
• Does the PLMN directory auto-update (weekly)?
• Is the alert “IMSI changed without a planned operation” enabled?
• Are SM-DP+ operation logs for eSIM stored with links to ICCID/EID?
• Is there RBAC and data access auditing?

Note: platforms like mobileproxy.space integrate part of this stack "out of the box," alleviating routine tasks for teams, especially in scenarios involving large modem farms.

Practice 4: Security, Compliance, and Data Protection

Risks

• Identifier Confusion: profile replacement, erroneous billing operations.
• IMSI Leakage: increased risks of targeted attacks on subscribers (in certain scenarios).
• Opaque Operations with eSIM: unauthorized loading/deletion of profiles.

Policies and Measures

1. Access Minimization: IMSI and key fields are visible only to roles that need it. Access logs are mandatory.
2. Encryption at rest and in transit. Segmentation of monitoring networks from production traffic.
3. RBAC for SM-DP+ operations (loading/deleting profiles). Two-factor authentication.
4. Decommissioning Procedures: erasing eSIM profiles, disposing of SIMs with documented ICCID.
5. Legal Cleanliness: compliance with laws and operator agreements. No grey schemes.

Compliance Checklist

• Is there a data processing registry (IMSI/ICCID) with purposes and retention periods?
• Are exports/exports of identifiers limited to necessary systems?
• Is regular access auditing and key rotation conducted?
• Are incident playbooks described for registration failures and compromises?

Tools, Reference Table, and Resources

Key Tools

• Modem Commands: AT+CCID (ICCID), AT+CIMI (IMSI), AT+CREG/AT+CEREG (statuses), AT+QENG (detailed telemetry, depending on chipset).
• MDM/EMM for device fleets: centralized reading of ICCID/IMSI and radio network KPIs.
• eSIM Stack: SM-DP+, LPA, EID registry, profile orchestration.
• PLMN Directories: regular auto-updating of MCC/MNC.
• Mobile Proxy Platforms: aggregate telemetry, management, reporting. Pay attention to the functionality of mobileproxy.space, where working with identifiers is integrated into daily operations.

Reference Table for Identifier Structures

Current Trends 2026

• eSIM and iSIM: increasing share of embedded profiles in IoT and proxy infrastructure, widespread adoption of RSP and remote profile switching.
• 5G SA: operators are acquiring more MNCs/PLMNs for network segmentation; the accuracy of directories is becoming more significant.
• Automation: expanding API management for profiles and telemetry; norm—auto alerts and self-healing scenarios in registration failures.

Cases, Results, and FAQ, Conclusion

Case 1: Reducing Downtime through ICCID-Centric Inventory

Task: 600 modems, 3 operators, frequent downtimes during SIM rotation. Actions: built an ICCID-IMEI-slot registry, implemented auto-enrichment of IMSI into MCC/MNC, alert “IMSIs changed outside the maintenance window.” Result: incident localization time reduced from 45 to 8 minutes; "lost" SIM count down from 12 to 0 per quarter; unplanned replacements decreased by 37%.

Case 2: Finding an Implicit Roaming Loop

Task: at one location, some modems suddenly went into roaming with deteriorating KPIs. Actions: matched IMSI with PLMN, noticed varying MNC lengths in profiles; updated the PRL and directory. Result: return to home PLMN, average speed increased by 28%, re-registration decreased by 3.2 times.

Case 3: Transitioning to eSIM Profiles Without Physical Travel

Task: replace 200 physical SIMs with eSIM. Actions: accounting ICCID/EID, orchestrating SM-DP+, staged profile loading, checking Luhn and statuses. Result: saved 120 man-hours of logistics, zero downtime, ability for "hot" operator switching based on MCC/MNC matrix.

FAQ

1. Can an operator be identified by ICCID alone?

Partially. By IIN and country code, one can infer the issuer, but it’s more reliable to use IMSI (MCC/MNC) or official PLMN directories.

2. What does the letter F mean in ICCID/IMSI output?

These are fillers in BCD representation. They need to be discarded in human-readable format.

3. How does an eSIM profile differ from a physical SIM concerning ICCID?

Each eSIM profile has its ICCID and is managed remotely via SM-DP+; one chip can have multiple ICCIDs.

4. Why does one operator have multiple MNCs?

For network segmentation, different brands, technological domains (e.g., 5G SA), and roaming agreements.

5. Is it mandatory for ICCID to have 20 digits?

No. 19 or 20 is acceptable, depending on the length of IIN and the individual part. The last digit is Luhn.

6. Can IMSI be changed without changing the SIM?

On eSIM — yes, when switching profiles. On physical SIM — usually no, IMSI is "burned" during personalization.

7. How to identify if the problem lies with the profile and not the radio part?

Compare radio signal metrics (RSRP/RSRQ/SINR) with the registration status based on IMSI/PLMN. A good signal and repeated Attach failures indicate profile/authentication issues.

8. Is it safe to log IMSI?

Yes, when following principles of minimization, encryption, and RBAC. Only store what is operationally necessary.

9. Why check Luhn on ICCID?

To filter out input errors and data corruption during exchanges with systems.

10. How often should the MCC/MNC directory be updated?

No less than once a month; in dynamic environments—weekly with differential checks.

Conclusion

ICCID and IMSI are not “dry” telecom theory, but practical levers for managing mobile infrastructure. Understanding their structure, role, and relationships with MCC/MNC transforms a chaotic fleet of SIMs and modems into a transparent system with predictable behavior. Implement ICCID-centric inventory, automate IMSI enrichment into PLMN, set up telemetry and alerts—and you’ll see downtimes decrease, troubleshooting simplify, and control grow. As scale increases, utilize specialized services like mobileproxy.space, which already consider best practices for working with SIM identifiers in the context of mobile proxies.