Book a DemoSyed Fazle RahmanSandeep
Back to tools

IMEI Generator

Bulk-generate Luhn-valid IMEIs for QA. 15 digits, valid check digit, ready for form validation tests, device registry seeding, and database fixtures. Runs in your browser.

1–100

0 items

How It Works

  1. 1

    Pick quantity

    1 to 100 IMEIs per batch.

  2. 2

    Choose a format

    Plain text, CSV, JSON, JS array, or Playwright.

  3. 3

    Generate

    Each IMEI is 15 digits with a valid Luhn check digit.

  4. 4

    Copy or download

    Drop into your test fixtures, mock device registry, or form tests.

Use Cases

  • Device registry tests

    Seed a mock MDM or device inventory with valid IMEIs for QA.

  • Form validation

    Verify your IMEI input field accepts Luhn-valid inputs and rejects invalid ones.

  • Database fixtures

    Populate a `device.imei` column for end-to-end test data.

  • API contract tests

    Test endpoints that accept IMEI parameters with always-valid inputs.

Frequently Asked Questions

Pick a quantity (1 to 100) and click Generate. Each random IMEI is 15 digits, starts with the reporting body prefix 35, and ends in a valid Luhn check digit. Every IMEI you generate is independent — no duplicates within a batch unless you generate hundreds at once.
IMEI stands for International Mobile Equipment Identity. A 15-digit number that uniquely identifies a mobile phone on a cellular network. Every GSM, UMTS, and LTE device has one. It is checksum-validated using the Luhn algorithm, the same checksum used for credit card numbers.
No. They are synthetically generated and pass Luhn validation, but are not registered with any device or carrier. Use them as test data for forms, validators, and database fixtures. They will fail any real GSMA / TAC database lookup.
We start with a generic reporting body prefix (35), append 12 random digits to reach 14, then compute the Luhn check digit and append it for a total of 15 digits. The result passes any Luhn-based IMEI validator.
Yes for standard Luhn validators. For validators that check the TAC (Type Allocation Code, first 8 digits) against the GSMA database, no, these are synthetic and not in any registry.
Not in the current build. Real per-model IMEIs require the manufacturer's TAC, which is registered with the GSMA. For QA, the generic format here is usually sufficient.
Yes. Pick the Playwright format to get a ready-to-paste test loop.
No. Generation runs entirely in your browser.

Similar tools

All tools

Done generating test data? Now automate the tests.

Bug0's expert AI agents write end-to-end tests from plain English, auto-heal them when your UI changes, and run them on every deploy. A forward-deployed engineer verifies every result.

Book a DemoSyed Fazle RahmanSandeep

From $2,500/mo. Results in 7 days.

Go on vacation. Bug0 never sleeps. The AI tests every commit, every deploy, every schedule. Your forward-deployed engineer reviews every failure and files the bugs. Coverage holds while you're off the grid.

Go on vacation.
Bug0 never sleeps.

The AI tests every commit, every deploy, every schedule. Your forward-deployed engineer reviews every failure and files the bugs. Coverage holds while you're off the grid.

Book a Demo