ICCID Luhn check

Client

Telecom ICCIDs use the same Luhn doubling rule as many payment identifiers. This page focuses on mod-10 pass/fail and the corrected trailing digit when OCR misreads one number.

Privacy: digits are evaluated only inside your browser. There is no carrier, GSMA, or SM-DP+ query—format math only. Treat SIM identifiers like any sensitive operational paste.
?

The ITU‑T E.118 layout follows ISO/IEC 7812 for card identifiers: a Major Industry Identifier (telecom ICCIDs usually start with 89), an issuer/country/account block, then a trailing Luhn mod‑10 check digit using the same doubling rule as many payment PAN validators. Printed cards commonly show 1822 digits; issuers pin one length profile per range.

Result

Passes Luhn mod 10 on the full 19-digit string.

  • MII (first 2): 89
  • Issuer / account core (between MII and check): 3530012345678901
  • Check digit (last): 1

Common use cases

  • Debug a single transposed digit in warehouse scans.
  • Cross-check Luhn before retyping long ICCIDs into portals.

Common mistakes to avoid

  • Applying payment-card Luhn code to partial strings

    Run Luhn on the full ICCID including the check digit.

FAQ

Do ICCIDs use Luhn?

Yes—the full string includes a trailing Luhn mod-10 check digit in common E.118 prints.

Can I use the generic Luhn tool?

Yes—this page adds ICCID length guards and MII context.

Common search terms

Phrases people search for that match this tool. See the full long-tail keyword index.

  • iccid check
  • iccid checker online
  • iccid validator luhn online
  • sim card iccid checksum check browser
  • e118 iccid validate digits locally
  • telecom iccid mii 89 checker
  • integrate circuit card id luhn mod 10
  • iccid luhn check
  • validate iccid online
  • esim iccid check
  • iccid check digit
  • iccid vs imei
  • iccid format e118
  • iccid check online
  • bulk iccid check
  • sim iccid check
  • verify iccid number
  • iccid csv validator

Related utilities you can open in another tab—mostly client-side.