Number / HLR Format Utilities
E.164, E.212 and E.214 in one place: validate an MSISDN, split an IMSI into MCC/MNC/MSIN, convert an IMSI to a Mobile Global Title, and look up the operators behind a mobile country code.
All lookups are bundled and run offline in your browser
- Normalized
- +5511988887777
- Country code
- 55
- Country
- Brazil
- National number
- 11988887777
Brazil: 11-digit mobile with 9th digit present (mandatory for mobiles since 2016).
MCC/MNC dataset: sample set, 2026-06. Prefix→operator for an MSISDN is unreliable after porting — that's what MNP/HLR lookups are for.
Why you can't derive an MSISDN from an IMSI
The IMSI (E.212) identifies the SIM inside the network; the MSISDN (E.164) is the dialable number. The mapping between them lives in the HLR/HSS and is not algorithmic — which is exactly why MNP and HLR lookups exist. The E.214 converter here shows the method (MCC→E.164 country code, MNC→network code) with a clear caveat that the authoritative NC mapping lives in the operator's GT plan.
FAQ
What can it decode?
Four utilities on one page: E.164 MSISDN validation and normalisation, E.212 IMSI decoding (MCC/MNC/MSIN), E.214 mobile-global-title conversion, and a direct MCC/MNC operator lookup.
How does it resolve the 2-vs-3-digit MNC ambiguity?
Against a bundled MCC-MNC dataset. When both a 2- and 3-digit interpretation match, it shows both rather than guessing.
Can I get the operator from a phone number?
Only the country and format reliably. After number portability, prefix-to-operator is unreliable for an MSISDN — that is exactly what MNP/HLR lookups are for (and part of what we consult on).
Number normalization cheatsheet (PDF)
Get the practitioner guide plus occasional deep-dives on SMPP, SIP and USSD. No spam; unsubscribe any time.
Stuck on a real integration?
These tools come from day-job work: SMSC/STP/Sigtran, SMPP hookups, USSD gateways and WebRTC. If a paste here turned into a rabbit hole, that's exactly what we do.