Standards-based SIM and eSIM reference

What Is an ICCID Number? SIM & eSIM Guide

Understand what an ICCID identifies, how its fields are organized, where to find it, and why it is different from IMSI, IMEI, EID, and your mobile phone number.

An ICCID is the serial-style identifier for a physical SIM card or an eSIM profile. It helps carriers, device platforms, and management systems distinguish the card or profile that holds a mobile subscription.

ICCID definition

ICCID stands for Integrated Circuit Card Identifier. The current ITU-T E.118 recommendation describes the number as a Primary Account Number; for SIM and eSIM use, it is also known as the ICCID or SIM serial number. It uniquely identifies a UICC or a profile in an eUICC.

Plain-language definition The ICCID identifies the SIM card or eSIM profile—not the phone, not the subscriber identity used on the network, and not the telephone number.
Full name
Integrated Circuit Card Identifier
Identifies
Physical UICC or eSIM profile
Common display
19 decimal digits beginning with 89
Primary standard
ITU-T E.118

How an ICCID number is structured

The exact boundary between issuer and account fields can vary, but the number follows a common hierarchy. The opening digits identify the telecommunications numbering context and issuer; the remaining body identifies the individual card or profile; the final digit is commonly a Luhn check digit.

89 1 01 1234567890123 8

Example only: 89 telecom MII · 1 country-code resource · 01 illustrative issuer field · account body · 8 Luhn digit

1. Major Industry Identifier: 89

The Major Industry Identifier 89 is assigned for telecommunication purposes. A digit string that does not begin with 89 may still satisfy a Luhn calculation, but it is not in the normal telecommunications ICCID numbering space.

2. Country code and issuer identification

The country-code portion uses E.164 numbering resources and can be one to three digits. It is followed by issuer identification. ITU guidance allows variation in issuer structures, so a country prefix alone is not a dependable carrier lookup.

3. Individual account identification

The issuer assigns the remaining body to distinguish a card or eSIM profile within its numbering allocation. Production systems should treat the complete value as a string so leading zeroes are preserved.

4. Luhn check digit

The final digit in the current 19-digit E.118 structure is calculated with the Luhn modulus-10 method. It detects many entry errors, but a checksum pass does not query a carrier or prove that the identifier was issued.

Why do ICCIDs appear as 18, 19, or 20 characters?

Current ITU-T E.118 specifies a 19-digit PAN for the ICCID. An 18-digit value may be the body awaiting its final parity digit or a truncated input; a 20-digit decimal value may come from an issuer-specific or legacy interface. Preserve those values for investigation, but do not label them conformant current E.118 ICCIDs on length alone.

Inside a UICC, ETSI TS 102 221 defines EF_ICCID as a 10-byte file. The decimal digits are stored as swapped-nibble BCD and unused space can be filled with hexadecimal F. That trailing F is storage padding, not an extra decimal ICCID digit.

Working with modem or smart-card hex?

Use the ICCID and EF_ICCID decoder to convert the 10-byte BCD representation without confusing filler nibbles with printed digits.

ICCID vs IMSI vs IMEI vs EID

These identifiers often appear together in device-management and carrier systems, but they identify different layers. Keeping them separate prevents provisioning and inventory mistakes.

Identifier What it identifies Typical format What changes it
ICCID Physical SIM/UICC or an eSIM profile Commonly 19 decimal digits, telecom prefix 89 Replacing the SIM or installing a different profile
IMSI Mobile network subscription identity Up to 15 digits under ITU-T E.212 Changing the subscription identity or operator profile
IMEI Mobile equipment such as a phone or modem Usually 15 decimal digits Changing the device or radio module
EID eUICC hardware that can store eSIM profiles 32 decimal digits in the current GSMA scheme Changing the eUICC hardware
MSISDN Dialable mobile telephone number E.164 phone number Carrier reassignment or an assigned number change
ICCID IIN is not IMSI MCC/MNC

ICCID follows ITU-T E.118: the 89 MII is followed by a one-to-three-digit E.164 country code and issuer identification. IMSI follows ITU-T E.212 and begins with an MCC and MNC. Those field systems are not interchangeable, and an ICCID country prefix alone is not a reliable current-carrier lookup.

Where to find an ICCID

The most reliable source depends on whether the SIM is physical or embedded and whether the device manufacturer exposes the value in settings.

Physical SIM

Card or packaging

Look for a long number printed on the SIM body, carrier card, activation slip, shipment label, or inventory record. It commonly begins with 89.

iPhone

Settings → General → About

Apple lists ICCID under About for supported cellular configurations. Touch and hold the identifier to copy it when that option is available.

Android

About phone or SIM manager

Menu names vary by manufacturer. Check SIM status or SIM manager. If the ICCID is not shown, use carrier records or the SIM packaging.

eSIM / fleet

Carrier or device-management portal

For eSIM profiles and IoT fleets, the carrier, SM-DP+ workflow, or connectivity-management platform normally records each profile ICCID.

Why many Android apps cannot read the ICCID

Android restricts access because ICCID is globally unique and non-resettable. Current APIs return it only to privileged, carrier-authorized, or qualifying device-management apps; ordinary apps should not promise universal ICCID access.

What an ICCID is used for

ICCID is useful anywhere a system must track the card or profile separately from the device and subscription identity:

  • SIM and eSIM inventory, shipment, and lifecycle management
  • IoT fleet onboarding and connectivity-platform reconciliation
  • Provisioning workflows and customer-support case matching
  • Software validation, database fixtures, API testing, and QA
  • Mapping an eSIM profile to an eUICC without confusing ICCID and EID

What an ICCID lookup cannot tell you by itself

An ICCID alone does not reveal the current phone number, prove activation, confirm account ownership, show network coverage, or reliably identify a carrier from an unmaintained prefix list. Those answers require authorized carrier or platform data.

Treat real ICCIDs as sensitive operational identifiers

Mask them in public screenshots, support posts, analytics, and logs. Share a full production ICCID only with systems and support channels that genuinely need it.

How to store ICCIDs in production systems

Most ICCID data failures happen outside the checksum algorithm: numeric types lose precision, import jobs remove leading zeroes, logs expose complete identifiers, or systems confuse format validity with current service state. Use an explicit data contract.

  • Store the normalized current-standard ICCID as text, such as CHAR(19) or VARCHAR(19), never as an integer or floating-point number.
  • Preserve the original input for audit while keeping a separate normalized decimal value for matching.
  • Keep printed ICCID and EF_ICCID hex in separate fields; a trailing F is storage padding, not a printed decimal digit.
  • Normalize spaces and hyphens at the boundary, but never silently truncate an 18-, 19-, or 20-character source value; retain it separately and record why it is non-standard or incomplete.
  • Mask production ICCIDs in URLs, analytics events, screenshots, support posts, and general application logs.
  • Model checksum, issuer assignment, activation, ownership, and current carrier separately; a Luhn pass answers only the checksum question.
  • Apply the current 19-digit E.118 rule for ICCID conformance, and model any issuer-specific import compatibility rule separately rather than silently weakening the ICCID validator.
JavaScript precision warning

A 19-digit ICCID exceeds JavaScript's safe integer range. Keep it quoted in JSON and CSV import schemas so the browser, spreadsheet, or database driver cannot round the final digits.

How to validate an ICCID safely

A useful structural check has three separate questions: does the value contain the expected number of decimal digits, does it use the telecommunications prefix 89, and does the final digit pass the applicable Luhn rule? Keep those checks separate from real-world existence and activation.

Frequently asked ICCID questions

Is an ICCID the same as a SIM card number?

Usually, yes. In consumer and carrier workflows, “SIM card number” commonly means the ICCID printed on a physical SIM or assigned to an eSIM profile.

Is ICC ID the same as ICCID?

Yes. “ICC ID” is a spaced form of ICCID, the Integrated Circuit Card Identifier used for a physical SIM card or an eSIM profile.

Is ICCID the same as IMEI?

No. ICCID identifies a SIM card or eSIM profile, while IMEI identifies mobile equipment such as a phone or modem. Replacing a SIM changes the ICCID but normally not the device IMEI.

Does an eSIM have an ICCID?

Yes. An installed eSIM profile has an ICCID. The EID is a separate identifier for the eUICC hardware that stores and manages profiles.

Can an ICCID reveal a phone number?

Not reliably. An ICCID and an MSISDN phone number serve different purposes, and only the carrier can resolve their current account relationship.

Does a valid ICCID checksum mean the SIM is active?

No. A valid Luhn checksum confirms mathematical structure only. It cannot prove that the SIM or profile exists, is active, or belongs to a particular account.

Official sources and further reading

This guide prioritizes standards bodies and platform documentation over static carrier-prefix claims.

Published as ICCID Generator technical documentation for developers, QA engineers, telecom operations teams, and people trying to identify the correct SIM or eSIM number. Factual claims and implementation guidance were last technically reviewed against the official sources listed above on August 12, 2026. Examples are illustrative and do not represent real carrier accounts.