One exact string
The human-readable number and barcode carry the same 19 decimal digits. Keep ICCIDs as strings so JavaScript, spreadsheets, and database imports cannot round them.
Printable SIM and eSIM test labels
Paste existing ICCIDs, verify the current 19-digit E.118 structure and Luhn digit, then create plain Code 128 labels for QA, inventory, scanner, and print testing.
Symbology / 02
Code 128 can encode the complete decimal ICCID in a compact linear symbol. This page leaves code-set optimization to the renderer and does not pretend every odd-length 19-digit value is entirely Code 128C.
The human-readable number and barcode carry the same 19 decimal digits. Keep ICCIDs as strings so JavaScript, spreadsheets, and database imports cannot round them.
The ICCID's last digit is a Luhn check digit. Code 128 also contains an internal symbol check character. The renderer adds that symbol check automatically; it is not appended to the ICCID text.
An on-screen symbol is not proof that every printed label will scan. Printer DPI, scaling, quiet zones, media, contrast, scanner settings, and receiving software all affect the result.
Primary reference
ISO/IEC 15417 specifies Code 128 characteristics, encoding, dimensions, decoding, and application-defined parameters. ITU-T E.118 separately defines the ICCID numbering structure. Neither a barcode render nor a successful scan proves that a SIM exists or is active.
Data model / 03
GS1-128 is a specific use of Code 128 with FNC1 and GS1 Application Identifier data structures. This tool does not invent an AI for ICCID, insert FNC1, or describe its output as GS1 compliant.
Plain Code 128 containing exactly the validated ICCID string, plus human-readable text below the symbol.
A leading FNC1 symbol character and defined GS1 Application Identifiers that tell receiving systems how to interpret each data field.
GS1 AI (8002) describes a cellular mobile telephone identifier, not a general ICCID field. Length alone is not permission to reuse that AI for SIM serial numbers.
Implementation boundary: if a carrier, label specification, retailer, or inventory system requires GS1-128, follow that party's documented data contract rather than silently converting a plain ICCID string.
GS1 references
GS1 states that GS1-128 begins with an FNC1 after the Code 128 start character and carries Application Identifier plus data fields. Those requirements are intentionally absent from this plain Code 128 tool.
Representation / 04
Current ITU-T E.118 defines a 19-digit PAN. This label mode accepts those 19 decimal digits only; it does not add an F or encode swapped-nibble hexadecimal from file 2FE2.
| Representation | Example | Use in this label tool | Reason |
|---|---|---|---|
| Printed ICCID | 8910112345678901238 | Render | 19 decimal digits, 89 MII, correct Luhn digit. |
| ICCID body only | 891011234567890123 | Reject | Missing the final Luhn digit; complete it with the calculator. |
| EF_ICCID storage | 98 01 11 32 54 76 98 10 32 F8 | Reject | Swapped-nibble hexadecimal storage bytes are not the human-readable ICCID. |
| Interface form with F | 8910112345678901238F | Reject | F may be representation padding; it is not a twentieth decimal check digit. |
Need to inspect a modem response or file 2FE2? Use the ICCID and EF_ICCID decoder before creating a human-readable label.
Print QA / 05
The download is a deterministic symbol for your validated string, but production readiness depends on the complete physical and software path.
This page cannot certify a printer, scanner, label stock, carrier workflow, or regulatory requirement. Keep a verified production label specification alongside the generated test asset.
FAQ / 06
Clear answers about Code 128, GS1-128, checksums, trailing F, activation, and print testing.
No. ITU-T E.118 defines the ICCID numbering structure, not a mandatory barcode symbology for every SIM label. Plain Code 128 is a practical option because it can encode the complete decimal string, but the target printer, scanner, label layout, and business system must be tested together.
No. This tool generates plain Code 128. GS1-128 uses an FNC1 character and GS1 Application Identifier data structures. The tool does not add an invented GS1 identifier or claim GS1 compliance for an ICCID.
No. The ICCID Luhn digit is part of the 19-digit identifier. Code 128 also includes an internal symbol check character for barcode decoding. They are separate checks, and users should not append the Code 128 check character to the ICCID text.
Not in this current-standard ICCID label mode. E.118 defines a 19-digit PAN. Hexadecimal F may appear as an EF_ICCID storage filler or in a profile-interface representation, but it is not a twentieth decimal Luhn digit. Confirm any interface-specific label requirement with its issuer.
No. A barcode only represents the entered characters, and a format-valid ICCID only passes structural checks. Neither result proves issuance, ownership, carrier assignment, activation, or network access.
Printing can change bar width, quiet zones, contrast, scaling, and edge quality. Test the actual printer, media, DPI, scanner, scan distance, and receiving software before using a label workflow in production.