MCC (Mobile Country Code): Complete Guide and Its Connection to MNC and PLMN

Introduction: Why This Topic Matters and What You'll Learn

Mobile connectivity has become the default digital infrastructure for apps, payments, transport, and services, all depending on precise network identification. At the center of this identification is the MCC (Mobile Country Code), a three-digit country code within global mobile network identifiers. A solid understanding of MCC and its relation to MNC and PLMN is essential for network engineers, mobile proxy specialists, developers, and analysts.

Why is this important for you? Because MCC influences the determination of network countries, device registration logic with operators, billing and roaming accuracy, SIM toolkit functionality, and the real geolocation of mobile proxies and connections. Misinterpreting MCC can lead to access failures, targeting inaccuracies, and metric degradation—from advertising platform deviations to message delivery declines. By 2026, with the massive adoption of 5G SA/NSA, eSIM, and IoT profiles, precise handling of PLMN ID (MCC+MNC) becomes not just a technical detail but a factor of resilience.

In this guide, we'll cover everything from A to Z: you'll learn what MCC is and why it's needed; how the MCC–MNC–PLMN relationship functions; receive a comprehensive MCC directory by country with a focus on the CIS, Europe, and Asia; see how MCC affects mobile proxy geolocation; discover how to find your SIM's MCC on Android, iOS, and modems; and get step-by-step instructions, checklists, real cases, and answers to frequently asked questions. We strictly adhere to legal requirements and do not discuss practices that contravene legal norms.

Our promise: after reading, you'll confidently work with MCC at a professional level, avoid common pitfalls, and build reliable procedures for controlling the geography of mobile connections and proxies.

Basics: Fundamental Concepts (For Beginners)

MCC (Mobile Country Code) is a three-digit code that signifies a country as part of a mobile network identifier. Its partner in conjunction is the MNC (Mobile Network Code), a two- or three-digit code for operators within that country. Together, MCC and MNC form PLMN ID—a unique identifier for the public land mobile network. For instance, MCC=250 (Russia), MNC=02 (MTS), meaning PLMN ID = 250-02.

Where does MCC reside in the identification system? In several places:

• IMSI (International Mobile Subscriber Identity)—the identifier for subscribers on SIM/eSIM: the first three digits of IMSI represent MCC, the next 2-3 digits are MNC, followed by MSIN (the unique subscriber part).
• PLMN ID—pairing MCC+MNC transmitted by the network; this guides the device in selecting and registering with the required network.
• Signaling elements (LTE/NR): during scanning and registration, UE receives lists of allowed/forbidden PLMNs.

How does MCC differ from a country phone code (E.164)? Substantially. Phone codes are used for call numbering, while MCC is for identifying mobile networks at the radio access and core level. For example, Russia’s phone code is +7, while its MCC is 250.

Who assigns MCC? Distribution occurs through industry registries like GSMA in collaboration with national regulators. While the mapping of MCC to countries is stable, it is occasionally updated: new allocations may emerge, and statuses for territories and test bands may change.

Why is it essential to understand MCC in practice? The implications of MCC include:

• Network Registration and accurate roaming.
• Geolocation of Mobile Proxies and the alignment with expected country services.
• Compliance: filters, restrictions, tariff, and licensing conditions.
• Analytics: session tracing, traffic segmentation by markets.

A convenient analogy: MCC is like the "country" in a network passport number, MNC is the "issuing organization," and PLMN is the "country+operator" that you connect to upon entry.

Deep Dive: Advanced Aspects of the Topic

If the foundation is clear, let’s delve deeper. Key points include:

Structure of PLMN ID and Its Role

PLMN ID = MCC (3 digits) + MNC (2-3 digits). In 4G/5G cores, PLMN ID is used in network selection, in lists of "allowed PLMNs," during handovers between eNodeB/gNodeB. In 5G SA, a new NID (Network Identifier) appears for non-public networks (SNPN), but for public networks, it remains based on PLMN.

IMSI and Its Relationship with MCC

IMSI in SIM/eSIM includes MCC as the first three digits. This means that even without registration in the radio network, we can extract the MCC by reading the IMSI. Example: IMSI 2500270xxxxxxx—MCC=250, MNC=02 (if MNC is two digits). A nuance: MNC can be two or three digits long; correct parsing requires knowing the MNC list for that MCC.

Roaming, ePLMN, and Local Behavior

In roaming, a device may be in country X but use PLMN with the MCC of country X and that operator. MCC clearly indicates the country of the network but not always the IP country. Why? Because IP may originate from CGNAT/PGW in another jurisdiction, especially with multinational operators. For core network ID storage, ePLMN lists (equivalent PLMNs) are also used, where a set of PLMNs are deemed interchangeable during registration procedures.

5G Trends in 2026

• Growth in eSIM profiles with multiple PLMNs (corporate, IoT). MCC remains the basis for selection.
• Increased complexity of IP geography due to cloud UPF (User Plane Function) and distributed cores: the network's MCC stays local, while the IP may terminate in a neighboring country.
• Widespread use of local breakout scenarios (LBO) to reduce the gap between MCC and IP geography for B2B cases.

The conclusion: MCC is a reliable indicator of the network country, but not always the IP country. A comprehensive verification is required for consistent geolocation.

Practice 1: How to Read the Network Identifier—MCC, MNC, and PLMN

Let’s break it down step by step.

Step 1. Extracting MCC

Source: IMSI on SIM/eSIM or the system status of the telephone module. The first three digits of the IMSI are the MCC. Example: IMSI 250991234567890—MCC=250.

Step 2. Determining MNC Length

MNC can be 2 or 3 digits. The country’s operator list defines the length. For MCC=250 (Russia), there are many operators with a two-digit MNC (for example, 01, 02, 20), but three-digit MNCs can also appear in some countries. Without the correct MNC table, parsing the IMSI can lead to errors.

Step 3. Assembling PLMN ID

PLMN ID consists of MCC+MNC. Example: MCC=250, MNC=02—PLMN 250-02. This code is transmitted by the network in the system information, allowing the device to select the PLMN according to priorities: Home PLMN (HPLMN), Equivalent PLMN (ePLMN), Allowed list.

Step 4. Cross-referencing with Network Parameters

For LTE/NR, linking PLMN with TAC (Tracking Area Code) and Cell ID is useful to understand borders within the operator but does not impact the geography of the country (MCC). For engineering diagnostics: LAC (in 3G), TAC (in 4G/5G), eNodeB/gNodeB ID.

Step 5. Parsing Practice

• Received IMSI 460011234567890. We know that for MCC=460 (China), China Mobile has MNC=00 (two-digit). Thus: MCC=460, MNC=01? No—it requires checking against the table: for China Mobile, typical MNCs are 00, 02, 07, etc. If the IMSI starts with 46001..., then MNC=01 (China Unicom). Without the table, it’s easy to mix things up—always use current MNC directories.
• IMSI 2341509xxxxxxx. MCC=234 (United Kingdom), MNC=15. PLMN=234-15—this is the network of one of the MVNO/operators in the UK.

If you want to delve deeper into MNC and PLMN, check out materials on what MNC is and how it works and how PLMN is formed and why it matters to the system.

Practice 2: MCC Directory by Country (Focus on CIS, EU, and Asia)

Below is a reference table with MCC. We highlight popular markets in the CIS, Europe, and Asia, adding key regions for completeness. Note: specific MNC codes may vary by operators; MCC remains stable but is periodically updated.

Tip: MCC "001" is often used for test or international/special allocations, and there are reserved ranges—their everyday use is not usual.

Practice 3: How MCC Influences Mobile Proxy Geolocation

In the mobile proxy ecosystem, two geographical layers are vital: "radio network" and "IP." MCC pinpoints the country of the network where the modem/phone is registered. However, the IP address through which traffic travels may terminate in a neighboring country (especially under centralized nodes or cloud UPF). If you're building or using mobile proxies, follow the principle of layer alignment:

Geography Alignment Framework (MCC ↔ IP)

1. Extract the actual PLMN: MCC+MNC, logging it in proxy session logs.
2. Check ASN and IP geo: using built-in GeoIP databases (without external links—utilize a local MaxMind-like directory) and reverse hostname.
3. Compare the country MCC with the country IP: discrepancies are allowed in specific scenarios (roaming, multinational cores), but set a threshold: for instance, "no more than one country discrepancy under stable conditions."
4. Assess LBO/UPF topology: if your provider uses a local breakout, discrepancies will reduce. Clarify the architecture.
5. Implement an "MCC fidelity score": 0-100, where 100 signifies perfect alignment between the MCC and the country IP in 95% of sessions over a period.

Practical Effects of MCC on Proxies

• Regulatory Filters: some services check PLMN (via SDK/OS) and expect a specific country. A mismatch could result in refusal or a request for additional verification.
• Targeting and Local Content: media and marketing platforms increasingly "stitch" signals together: IP geo + PLMN country. When MCC and IP diverge, certain inventory may be unavailable.
• Billing and QoS: operators may have policy differentiation based on PLMN and RAT (LTE/NR) affecting session stability. Log PLMN along with the type of network (4G/5G).

What Mobile Proxy Providers Do

Providers like mobileproxy.space support filtering and fixing based on MCC/MNC, provide metrics for IP-geo alignment, cell rotation, and PLMN control. This mitigates the risk of geographical discrepancies and simplifies quality audits. It's crucial: request statistics on MCC↔IP alignment and SLA on "fidelity score".

Mini-Checklist for Geolocation Control

• Log MCC, MNC, TAC, Cell ID, RAT type, IP, ASN.
• Check the "country pair": MCC country vs GeoIP country.
• Record the share of discrepancies, time slot, and modem location.
• Use white lists for PLMN in your pool.
• Set alerts for abrupt shifts in IP geo when MCC remains unchanged.

Practice 4: How to Find Your SIM's MCC

Methods vary depending on the platform and hardware. Here are some tried-and-true methods:

Android (Non-root)

1. Settings → About Phone → SIM Status → Network. The "Network" section often displays the operator and PLMN. If the MCC/MNC isn't clearly visible, check "SIM Info" or "Phone Status"—many interfaces show "Network Code."
2. USSD/Engineer codes for certain brands (depends on manufacturer). Example: *#*#4636#*#* → Phone Info → Current Network. This may display the PLMN ID.
3. Diagnostic apps: system widgets/utilities read TelephonyManager and show MCC/MNC.

iOS

1. Settings → General → About → Carrier. The name doesn't always reveal MCC, but in Field Test mode, PLMN viewing may be possible.
2. Dial *3001#12345#* and call → Field Test opens. In the Serving/Registered PLMN sections, MCC and MNC usually appear. Availability depends on iOS version and modem model.

USB/LTE Modems and Routers

1. AT Commands: connect to the modem via the COM port.
   • AT+CIMI — returns IMSI. The first three digits are MCC, followed by MNC.
   • AT+COPS? — shows registered operator and sometimes PLMN code.
   • AT+CREG? / AT+CEREG? — registration status. Used with COPS provides insights into the network.
2. ModemManager (Linux): mmcli -m 0 | grep operator; mmcli -m 0 --command='AT+CIMI'.
3. Huawei HiLink/ZTE web UI: diagnostics display "Network Code" or can query an internal API (as per device documentation).

eSIM/MDM

In corporate scenarios, MDM panels and eSIM SM-DP+ logs provide IMSI/ICCID attributes. MCC is extracted from IMSI. If MNC is three digits, ensure parsing is accurate concerning the country.

Important

• IMSI ≠ ICCID: ICCID is the SIM card number; do not confuse it with IMSI. MCC is derived strictly from IMSI.
• For dual-SIM, check the active line: MCC may differ between slots.
• In roaming, MCC will reflect the network country you’re currently registered in, not the home operator's country.

Practice 5: Designing Mobile Proxy Pools with MCC/MNC Considerations

If you are building or managing a mobile proxy pool, factor in MCC as a key parameter in orchestration.

Architectural Approach

1. Segmentation by PLMN: group modems by PLMN (MCC+MNC), not just "by country." This will enhance result repeatability.
2. Multi-PLMN Coverage: in larger countries, plan for 2-3 leading PLMNs for diversification.
3. Logging RAN Parameters: TAC, Cell ID, eNodeB/gNodeB ID—for detecting degradations in particular zones.
4. Rotation with Binding: synchronize IP rotations with PLMN retention to avoid MCC drift.
5. SLA and Monitoring: metrics for MCC fidelity, "IP country match," minimum compliance percentages weekly/monthly.

Step-by-Step Checklist for Pool Launch

• Compile a table of target countries → select priority MCCs.
• Choose SIMs with the required MNCs within MCC.
• At the modem level, ensure stable registration by PLMN (COPS, RSRP/RSRQ monitoring).
• Run tests for 24-72 hours: capture IP country distribution, average matching shares.
• Set alerts for PLMN drift: record any switching between operators.

Integration with mobileproxy.space

Services like mobileproxy.space typically implement filters by country/city and operator (MNC), as well as session logs. It is advisable to fix proxies by PLMN and include MCC↔IP reports. This speeds up verification and enhances geosignal predictability.

Practice 6: Testing and Auditing MCC/PLMN in Production

Even an ideal configuration requires ongoing audits.

The "Three Independent Sensors" Method

1. Sensor 1: Radio — MCC/MNC/TAC/Cell (from modem/phone).
2. Sensor 2: IP — GeoIP database + ASN → country and network IP.
3. Sensor 3: Application — what the target service sees (some SDKs have diagnostic screens or reverse telemetry for country).

Aggregate data daily. If two out of three sensors diverge—a diagnosis is needed: check the cell area, signal level (RSRP/RSRQ/SINR), re-register in the PLMN.

Procedures

• Basic Check: 10-20 registration cycles at 15-minute intervals, comparing MCC↔IP geos.
• Stress Test: intensive IP rotation with fixed PLMN; evaluate compliance stability.
• Degradation: if mismatches exceed the threshold, halt distribution from the pool, perform a re-attach in the network, and change APN if needed.

Practice 7: Diagnosing MCC Issues and "Healing" Strategies

Common symptoms and possible solutions:

• Symptom: the service flags traffic as "suspicious region." Actions: check PLMN, MCC, and IP country; possibly, the IP is routed through another region. Request your proxy provider to tie to a local breakout.
• Symptom: sudden switches between PLMN. Actions: check signal level, log the band (LTE-only/NR-only); if possible, force the network mode, and update the modem firmware.
• Symptom: incorrect IMSI parsing (MNC incorrectly identified). Actions: use a current MNC directory for that country; set a rule: "if MNC is not in the directory—flag for manual check."
• Symptom: app discrepancy, even when radio layer and IP match. Actions: the service may cache history. Clear the app cache, switch sessions, check SDK country detection options (locale, GPS, PLMN).

Common Mistakes: What NOT to Do

• Do not confuse MCC with country phone code: these are different standards and different registries.
• Do not rely solely on IP-geo: ignoring MCC/PLMN leads to false conclusions about the real network country.
• Do not overlook MNC length: 2 or 3 digits are key to accurate IMSI parsing.
• Do not use outdated tables: MNC databases and MVNO mappings are periodically updated.
• Do not mix pools without PLMN control: this diminishes the predictability of results.
• Do not violate legal provisions: all practices must comply with the laws in your jurisdiction and service terms.

Tools and Resources: What to Use

• OS Tools: Android TelephonyManager, iOS Field Test, modem web UI.
• CLI and AT: AT+CIMI, AT+COPS?, AT+CEREG?; mmcli, qmicli.
• Local GeoIP Databases: for matching IP and country data without transferring information externally.
• Internal MNC directories: regularly update.
• Mobile Proxy Platforms: mobileproxy.space—filtering by MCC/MNC, compliance reports, convenient rotations.

Mini-Templates

• Log Schema: timestamp, device_id, IMSI_hash, MCC, MNC, PLMN, RAT, TAC, CellID, IP, ASN, geo_country, match_flag.
• Alert Rule: if mismatch_rate > 10% in 24 hours or PLMN switched more than three times in six hours—notify the engineer.

Cases and Outcomes: Real Application Examples

Case 1: Reducing Deviations by Aligning MCC↔IP

Task: advertising accounts in the EU declined campaigns due to "non-standard geography." Diagnosis: MCC=214 (Spain), IP country=PT (Portugal) in 22% of sessions. Actions: switch the pool to an operator with a local breakout, lock PLMN 214-07, monitor ASN. Result: mismatch share dropped to 3%, approval percentage increased by 18 percentage points, CTR +9%.

Case 2: Unstable MNC Profile in the CIS

Task: unstable registration in a megacity, PLMN drifted between 250-02 and 250-20. Actions: RSRQ tuning of antennas, LTE-only mode, modem firmware update, white-listing PLMN. Result: PLMN retention 99% of the time, timeout drop by 27%, savings on unsuccessful sessions — 14% cost reduction.

Case 3: Correct IMSI Parsing for eSIM Pool in Asia

Task: incorrectly parsing MNC in MCC=460 and MCC=525, disrupting analytics. Actions: implemented an MNC registry with length checks, "auto-detect" via PLMN from the network for validation. Result: PLMN recognition accuracy 99.97%, incident reduction by 92%.

FAQ: 7-10 In-Depth Questions

1. Is it true that MCC unequivocally determines the IP country?

No. MCC specifies the mobile network country you are registered in. IP termination can occur in another country (centralized PGW/UPF, transit, provider specifics). Compare MCC and IP-geo concurrently.

2. How to distinguish between two- and three-digit MNC when parsing IMSI?

Utilize a current MNC table for that MCC. There is no universal rule of "always two digits"; in some countries, it can be three. Without a directory, mistakes can happen.

3. What is ePLMN, and why is it necessary?

ePLMN is a list of equivalent PLMNs. The network informs the device which PLMNs to consider equal to the home PLMN, simplifying registration, handover, and roaming processes.

4. Can an MVNO have its MNC?

Yes. Many full MVNOs receive their MNCs and PLMN IDs. However, "hosted" models where MVNOs use the MNC of the underlying operator are also common.

5. Why does the service see "another country" when I have the correct MCC?

Probable that the IP geo was determined by a different country (IP source, CGNAT, routing). Check ASN, regional breakout, and GeoIP databases. Often, tying the pool to a PLMN with local exit helps.

6. How does MCC work in 5G SA?

The same as in 4G: PLMN ID remains MCC+MNC. For non-public networks, an NID appears, but MCC remains. Registration procedures use PLMN.

7. Does MNP (Mobile Number Portability) affect MCC/MNC?

MNP relates to the number (MSISDN), not IMSI/PLMN. Number portability does not change MCC, while the subscriber's MNC is defined by the SIM profile and network, not the phone number.

8. How to check MCC on an iPhone if Field Test is limited?

Check for iOS updates: Field Test sections may change. An alternative is to use operator information from the eSIM profile or request diagnostic data from MDM/operator.

9. Can you "fix MCC"?

MCC is the country of the network. It is determined by the registered PLMN. You do not "fix MCC" directly; you fix the choice of network/operator. In practice, you maintain registration in the needed PLMN with sufficient signal level.

10. Is it legal to use mobile proxies?

Usage must comply with the laws in your country and service terms. We do not discuss or recommend practices that may violate legal norms.

Conclusion: Summary and Next Steps

MCC is a keystone in mobile network identification: without it, reading PLMN accurately, managing connections robustly, and objectively assessing mobile proxy geolocation is impossible. You learned how MCC, MNC, and PLMN are structured, received a comprehensive MCC directory by country, and practical methods for inspection and auditing. The next step is a matter of systematic discipline: keep logs of MCC/PLMN, automate checks against IP-geos, implement "MCC fidelity score," and establish regulations for discrepancies. When working with providers like mobileproxy.space, request compliance reports and fix proxies by PLMN—this speeds up achieving stable results. Most importantly, act within the framework of the law and industry norms. Then, MCC will cease to be a "code mystery" and become a reliable tool in your network strategy.