Loading
Preparing your generator page
We are loading content and tools so everything is ready to use.
We are loading content and tools so everything is ready to use.
Generate Luhn-valid 15-digit IMEI numbers for QA and development — not for real device activation. Pick TAC profiles (All, Apple-like, Samsung-like, Pixel-like, Xiaomi-like, Generic test), batch 1–100 values, unique by default, and copy a newline-separated list.
Also try the GUID Generator, UUID Generator, and more in Utility tools.
Last updated: May 19, 2026 · Published: 2026-03-27 · Updated: 2026-05-19
Uses valid 15-digit formatting with Luhn checksum. For testing and QA workflows only.
Set options and click generate
An IMEI generator creates synthetic 15-digit mobile equipment identifiers that match the expected shape: 8-digit TAC prefix, 6-digit serial segment, and a Luhn check digit. QA teams use them to test forms, APIs, and databases without pulling real handset IMEIs from production.
Muxgen runs generation in your browser — select a TAC profile, generate, copy. Values are not uploaded to Muxgen servers. Use for testing only.
Three steps to Luhn-valid test IMEIs.
Choose how many IMEIs per batch — default is 1; max adjusts with duplicates and profile pool size.
All profiles, Apple-like, Samsung-like, Pixel-like, Xiaomi-like, or Generic test — shapes the 8-digit prefix.
Click Generate IMEI(s), review Luhn-valid results, Copy to clipboard as a newline-separated list.
Every control in the live IMEI component panel.
Clamped to maxCount — up to 100 with duplicates on; unique mode caps at min(100, pool × 1M).
Six options — default All profiles merges every predefined 8-digit TAC pool in the component.
Default off — Set dedupes within the batch; on allows repeats for stress tests.
Builds values, validates with isValidImei, clears copied state on each run.
Monospace cards per 15-digit IMEI; scrollable when many values are generated.
Newline-separated export with Clipboard API and textarea fallback; 2s Copied! feedback.
Six profile options and their test prefix pools (not official GSMA TACs).
Random TAC from the combined pool (22 prefixes across Apple-like, Samsung-like, Pixel-like, Xiaomi-like, and Generic test).
Five 8-digit prefixes (e.g. 35693803, 35702209) — simulates iPhone-style TAC distribution in test data.
Five prefixes (e.g. 35503109, 35391805) for Android handset QA scenarios.
Four prefixes shared/overlapping test TACs for Google Pixel-style fixtures.
Four prefixes (e.g. 86753005) for generic Android OEM-style test batches.
Four simple prefixes (01020304, 11112222, etc.) for obvious non-production test IDs.
How TAC, serial, and Luhn combine in output.
Type Allocation Code prefix — picked randomly from the active profile pool, not assigned by a real GSMA registration.
Random decimal digits appended to TAC before checksum calculation.
15th digit from Luhn on the first 14 digits — must match for isValidImei to accept output.
Only digits 0–9 — regex ^\d{15}$ plus Luhn validation in the generator loop.
approxUnique = TAC count × 1,000,000 serial combinations per profile selection.
Helper text on the tool: valid formatting for testing — not for production activation.
Where newline-copied IMEI lists land in real projects.
Paste IMEIs into mobile onboarding fields that require exactly 15 digits.
POST device register endpoints with Luhn-valid bodies from newline copy.
INSERT test devices without using real subscriber equipment identifiers.
Generate up to 100 unique IMEIs per click for performance scenarios.
APIs that accept both device IDs and auth secrets can pair this tool with the API Key Generator and validate payloads via the JSON Formatter.
Need hex UUIDs instead of 15-digit IMEIs? Use the GUID Generator or UUID Generator.
Aligned with the live IMEI generator component.
Every listed IMEI passes post-generation isValidImei check.
Brand-style and generic prefix pools for varied test distributions.
One-click batches for QA matrices and automation data files.
Optional Allow duplicate IMEIs for collision and repeat testing.
Paste into spreadsheets, .env lists, or CI fixture files quickly.
No sign-up; identifiers generated locally in the browser.
When Luhn-valid test IMEIs save time.
Cypress, Playwright, and Appium tests that need valid-shaped device IDs.
Simulate handset records in staging without real inventory IMEIs.
Verify your Luhn implementation matches generator output.
Populate UI tables with realistic 15-digit values for screenshots.
Switch TAC profile per test case to exercise prefix-based routing logic.
Enable duplicates to simulate collision handling in registration APIs.
Profiles, formats, and related Muxgen utilities.
IMEIs are 15-digit numeric with Luhn; GUIDs are 128-bit hex UUID v4 strings.
IMEIs identify device-shaped records; API keys authenticate requests — different field validators.
Single-brand pools narrow prefix distribution; All mixes every pool for diverse fixtures.
Default unique per batch; duplicates on for repeat-ID stress tests only.
Luhn-valid structure does not mean the IMEI is registered on a carrier network.
Apple-like and Samsung-like are Muxgen test labels — not official manufacturer TAC assignments.
Terms developers search alongside test IMEI generators.
International Mobile Equipment Identity — 15-digit equipment identifier format.
Type Allocation Code — first 8 digits; identifies device model family in real standards.
Checksum formula used to compute the 15th IMEI digit from the prior 14.
Six digits in this generator — random decimal positions 9–14 of the IMEI.
Final digit — validated so the full 15-digit string passes Luhn.
Synthetic data for QA — keep separate from production device registries.
Ethical, reliable QA usage after you copy identifiers.
Never use generated IMEIs for fraud, unlocking, or carrier activation workflows.
Leave Allow duplicate IMEIs off when seeding large unique device tables.
Run one generated value through your server-side Luhn and length checks.
Use Generic test profile when you want obviously synthetic TAC prefixes in logs.
Separate connection strings and table namespaces for IMEI fixture imports.
Marketing and docs should state values are randomly generated for testing.
Habits that pair with TAC profiles and duplicate mode.
Draft ^\d{15}$ validators, then confirm samples pass your API middleware.
Apple-like for iOS app tests, Samsung-like for Android MDM mocks.
One IMEI per line maps cleanly to CSV single-column imports.
Services that accept either IMEI or UUID can be tested with both Muxgen generators.
Run generate again for more — keeps browser generation responsive.
On-tool note reminds you: Luhn-valid formatting for testing and QA workflows only.
Luhn checksum, TAC profiles, batch limits, uniqueness, QA-only use, and privacy.
Explore more tools in the directory.
UUID v4 strings when your API uses GUIDs instead of numeric device IDs.
Alternate Muxgen page for bulk unique identifiers with format presets.
Mock API keys for mobile backend auth alongside device ID fixtures.
Build \d{15} or Luhn-aware patterns to validate IMEI fields in forms.
Pretty-print API payloads that include imei properties after generation.
Secrets for test accounts paired with generated device identifiers.