Skip to content
IoT Crest

What is IMSI? The international mobile subscriber identity

Published , 6 min read

Short answer: The IMSI, international mobile subscriber identity, is the number a mobile network uses to recognize a subscription. It is up to 15 digits, stored on the SIM, and made of a country code, a network code and a subscriber number. It identifies the subscription, while the IMEI identifies the device and the ICCID identifies the SIM card, and networks avoid sending it over the air wherever they can.

What is IMSI: the subscriber identity on every SIM, its MCC, MNC and MSIN digits, how networks hide it with temporary IDs and SUCI, and IMSI vs IMEI vs ICCID.

This article covers what the IMSI is and where it lives, its MCC, MNC and MSIN fields, how the network uses it to authenticate a SIM, the temporary identities and 5G SUCI that keep it off the air, IMSI catchers, IMSI against IMEI, ICCID and phone number, how to read it, and multi-IMSI SIMs for IoT. It does not cover the authentication algorithms in detail, lawful interception, or any particular operator's numbering.

The IMSI, short for international mobile subscriber identity, is the number a mobile network uses to recognize a subscription. It is stored on the SIM, it is up to 15 digits long, and its first digits say which country and which network the subscription belongs to. When a phone or an IoT module connects, the network uses the IMSI to find the subscription’s records and to check that the SIM holds the matching secret key. This article explains how the number is built, how the network uses it, how modern networks keep it from being broadcast, how it differs from the IMEI, the ICCID and the phone number, how to read it from a device, and why IoT SIMs sometimes carry more than one. (IMSI is also the name of an IVF technique; this article is about the mobile identity only.)

What the IMSI is

The IMSI is defined by the ITU in Recommendation E.212 and by 3GPP in TS 23.003, the specification for numbering and identities in mobile networks. It is assigned by the operator that issues the subscription and written into the SIM, in a file the device reads when it starts.

Each subscription has its own IMSI. A plain SIM card carries one. An eSIM or eUICC carries one per operator profile, so downloading a new profile gives the device a new IMSI, while the chip’s own identity, the EID, stays the same; the IoT SIM card guide covers eSIM profiles. The IMSI is not the phone number and is not printed on the card.

On the network side, the IMSI is the key to the subscriber’s record in the home network’s database: the HLR in 2G and 3G, the HSS in 4G, and the UDM in 5G. That record holds what the subscription is allowed to do, which network it is currently using, and the secret key shared with the SIM.

The structure of an IMSI

An IMSI has three parts.

An IMSI split into its fields (test-network example) 001 01 0123456789 MCC country code 3 digits MNC network code 2 or 3 digits MSIN subscriber number within that network, up to 10 digits MCC + MNC = the home network, its PLMN ID 15 digits at most; MCC 001 with MNC 01 is reserved for test networks
Diagram: an IMSI divided into its three fields, using the reserved test-network code as the example. The mobile country code (MCC) is three digits, the mobile network code (MNC) two or three, and the mobile subscription identification number (MSIN) fills the rest, up to 15 digits in total. The MCC and MNC together name the home network.

The mobile country code (MCC) is three digits and identifies the country, or for some international and satellite networks a shared code. Larger countries have several; the United States uses codes from 310 to 316. The mobile network code (MNC) is two or three digits and identifies the operator within that country; Europe mostly uses two-digit MNCs and North America three. The mobile subscription identification number (MSIN) is the operator’s own number for the subscription, and makes up the remaining digits.

The MCC and MNC together are the PLMN ID, the identity of a public land mobile network, and they tell any network in the world which home network a visiting device belongs to. That is how roaming works: a network in another country reads the first five or six digits, finds the home operator, and asks it whether to let the device on. The MNO and MVNO article explains how operators and resellers get their own network codes.

How the network uses the IMSI

When a device attaches to a network for the first time, it identifies itself, and the network has to check that the claim is genuine. In outline:

  1. The device sends its identity: the IMSI, or in 5G a concealed form of it.
  2. The network it is attaching to, which may be a roaming partner, asks the home network for authentication data for that subscriber.
  3. The home network looks up the subscriber’s secret key and produces a random challenge and the answer it expects.
  4. The device’s SIM computes its answer from the challenge and the same key, which never leaves the SIM.
  5. If the answers match, the device is in, and both sides derive keys to encrypt the connection.
  6. The network gives the device a temporary identity to use from then on.
Attaching to a network: the IMSI is used once device + SIM visited network home network 1 IMSI, or SUCI in 5G 2 ask for auth data 3 challenge + expected answer 4 challenge 5 answer from the SIM's key 6 temporary ID (TMSI or GUTI)
Diagram: a device attaching to a network. The device sends its IMSI, or in 5G a concealed SUCI; the visited network asks the home network for authentication data; the home network returns a challenge and the expected answer; the SIM computes its answer with a key that never leaves it; if they match, the network issues a temporary identity that the device uses instead of the IMSI from then on.

Keeping the IMSI off the air

Because the IMSI is permanent and tied to one subscriber, anyone who can collect it can track that subscriber. Networks therefore send it over the radio as little as possible.

Temporary identities. After the first attach, the network issues a temporary identity, the TMSI in 2G and 3G and the GUTI in 4G and 5G, and the device uses that instead. The network changes it from time to time, so a listener sees short-lived numbers that are hard to link to one person or device.

IMSI catchers. Before 5G, a network could still ask a device for its permanent IMSI in plain text, for example when it did not recognize the temporary identity. A fake base station, called an IMSI catcher, exploits that: it imitates a real network, devices nearby connect to it, and it asks each one for its IMSI. Some also try to push devices down to 2G, where the older security has known weaknesses.

5G SUCI. 5G closes that gap. The permanent identity is called the SUPI, and for SIM-based subscriptions the SUPI is the IMSI. The device never sends it in clear: it sends a SUCI, a subscription concealed identifier, in which the MSIN is encrypted with the home network’s public key and only the routing part, the MCC and MNC, stays readable. Only the home network can decrypt it. The protection depends on the operator enabling it and on the device and SIM supporting it, and it does not help a device that falls back to an older network.

IMSI vs IMEI vs ICCID vs phone number

A connected device has several identities that are easy to mix up.

IdentifierWhat it identifiesWhere it livesChanges when
IMSIThe subscription, to the mobile networkOn the SIM, one per profileThe SIM or eSIM profile changes
ICCIDThe SIM card or eSIM profile itselfPrinted on the card and stored on the chipThe SIM or profile changes
IMEIThe phone or cellular moduleIn the device’s hardwareThe device changes
Phone number (MSISDN)The subscription, to people and billingIn the operator’s records, linked to the IMSIThe operator reassigns it; it can be kept when moving operator

The ICCID, its digit structure and where to find it are covered in the ICCID number article. Moving a phone number to a new operator keeps the number and brings a new SIM, so the IMSI and ICCID change while the number stays. Many IoT SIMs have no voice number at all, or a number that nobody dials, and are tracked by ICCID and IMSI alone.

How to read the IMSI

On a cellular module, the standard AT command AT+CIMI from 3GPP TS 27.007 returns the IMSI. Device firmware commonly reads it at start-up along with the IMEI and ICCID and reports all three, so the fleet platform can match a device to its subscription.

Phones rarely show the IMSI in their settings, and recent versions of Android stop ordinary apps from reading it. Network diagnostic tools and the operator can see it. For an IoT fleet, the connectivity provider’s management platform lists the IMSI for each SIM, usually alongside the ICCID.

Multi-IMSI SIMs and IoT

A device fixed in a basement or on a remote pole cannot move to find a better network, and a single home operator’s roaming agreements may not cover every country a product ships to. Some IoT SIMs carry several IMSIs from different operators and switch between them, so the device appears to belong to whichever home network gives the best access where it is. The switching is done by an applet on the SIM, sometimes steered over the air by the provider, and the IoT SIM card guide compares it with roaming SIMs and eSIM.

That has one practical consequence for fleet records: the IMSI a device reports can change without any hardware being touched. Key the device’s records on the ICCID or on the device’s own ID, store the current IMSI as an attribute, and expect it to change.

Written by the IoT Crest editorial team. Facts in this article follow the editorial policy: only well-established behavior is stated and no figures are invented.

More from Connectivity

  1. What is LPWAN? Low-power wide-area networks

    What LPWAN is, what it gives up for range and battery life, how NB-IoT, LTE-M, LoRaWAN and Sigfox differ, who runs each network and how to choose.

  2. 5G RedCap: what it is and where it fits

    5G RedCap explained: what Reduced Capability 5G cuts from full 5G, how it compares with LTE-M, NB-IoT and Cat 1 bis, eRedCap, and which devices should use it.

  3. Wi-Fi HaLow (802.11ah): range, speed and uses

    Wi-Fi HaLow explained: how 802.11ah uses sub-1 GHz bands for long range, what speed and battery life to expect, how it compares with LoRaWAN, and where it fits.

  4. What is an IMEI number? Digits, checks and uses

    What is IMEI: the 15-digit ID of a phone or cellular module, how its TAC, serial and check digit work, how it differs from IMSI and ICCID, and where to find it.

  5. What is an MNO? Mobile network operators vs MVNOs

    MNO meaning in telecoms: what a mobile network operator owns, MVNOs, MVNEs and MVNAs, what a PLMN is, and how to compare an MNO and an MVNO for IoT SIMs.

  6. 2.4 GHz vs 5 GHz: which Wi-Fi band IoT devices need

    2.4 GHz vs 5 GHz Wi-Fi for IoT: range, speed, channels 1, 6 and 11, why smart devices need 2.4 GHz, and how to fix pairing on a dual-band router.

  7. ICCID number explained: the SIM serial, digit by digit

    The ICCID number explained: what the SIM serial is, how its digits break down, how it differs from IMSI and IMEI, and where to find it on phones and modules.

  8. What is an M2M SIM card? How M2M and IoT SIMs differ from phone SIMs

    What an M2M or IoT SIM card is, how it differs from a regular phone SIM, where it is used, activation, the 2FF to MFF2 form factors, M2M eSIM and iSIM.

  9. IoT protocols explained: the radio, network and messaging layers

    IoT protocols explained layer by layer: radio and link protocols, the network and transport layers above them, messaging on top, and how to combine them.

  10. MQTT vs CoAP: which IoT messaging protocol to use

    MQTT vs CoAP compared for IoT devices: publish-subscribe over TCP against a REST-like protocol over UDP, delivery guarantees, power and when each one fits.

  11. MQTT explained: topics, QoS levels and retained messages

    MQTT explained: how a broker, publishers and subscribers fit together, how to name topics and use wildcards, what QoS levels promise and retained messages.

  12. LoRaWAN explained: range, data rates and when to use it

    LoRaWAN explained: how LoRa radio and the LoRaWAN network layer differ, what range to expect, how spreading factors work, and when to pick it.

  13. NB-IoT vs LTE-M for cellular IoT devices

    NB-IoT vs LTE-M for cellular IoT devices: bandwidth and latency, mobility, power saving modes, coverage inside buildings, and which one to pick.

All connectivity articles

Sponsor an article in this topic

Sponsored articles and in-article link placements for IoT vendors, agencies and SEO buyers. Every sponsored piece is labeled, edited to the same standard as the rest of the site, and placed in the hub its readers already visit. Rates on request.

Ask a question

Ask a question

Spotted an error, or want a topic covered? It goes straight to the editors, who reply by email, WhatsApp or SMS.