Fake Phone Number Generator

Why country format matters

Each country has its own numbering rules: how many digits a mobile has, which prefix separates mobile from landline, when the area-code zero is dropped. A serious library like libphonenumber (Google) understands these rules for every country and rejects numbers that don't comply.

If your generator emits malformed numbers, your tests pass in CI and fail in production when a real number arrives. Better start with correct synthetic data.

Formats by country

• United States: +1 [3-digit area] [7 digits]. Example: +1 415 555 1234.
• United Kingdom: +44 [10 digits]. Mobiles start with 7. Example: +44 7700 900123.
• Canada: Same plan as the US (+1). Example: +1 416 555 1234.
• Australia: +61 [9 digits]. Mobiles start with 4. Example: +61 412 345 678.
• Germany: +49 [variable length]. Mobiles 15x, 16x, 17x. Example: +49 151 12345678.

E.164 vs local vs international

1. E.164 (+14155551234): the technical format, digits-only with a leading +. The canonical format for storing in a database and sending over an API. It's what Twilio, Stripe and almost every service uses.
2. International (+1 415 555 1234): human-readable, with spaces and dashes. Useful for UI display.
3. Local ((415) 555-1234): the format an American recognizes at a glance. No country code.

Best practice: always store in E.164 and format for display. That avoids ambiguity when a number moves between countries.

Reserved ranges for fiction

Some countries reserve specific ranges for fiction, examples and testing. If you need a guaranteed "unassigned" number:

• United States: 555-0100 through 555-0199 (FCC-mandated for fiction).
• United Kingdom: 0113 4960000 to 4960999 (Ofcom).
• Australia: +61 7 7010 0000 through +61 7 7010 9999.
• Other countries: no official ranges. Use generated data carefully.

When NOT to use fake numbers

These numbers are good for populating tables, validating forms and showing UIs. They aren't good for:

• Real SMS testing. Twilio, MessageBird and others have testing modes with magic numbers that confirm delivery without actually sending.
• Code verification. If your flow texts a code, fake numbers don't receive.
• WhatsApp Business validation. You need a real number verified by Meta.
• Live demos where someone might actually call. You're sending traffic to a random person.

Combining with other synthetic data

A realistic fixture combines name + email + address + phone. Tips:

1. The phone country code should match the address. A "New York" user with a German phone is a sign of a sloppy fixture.
2. The area code should be plausible for the city: New York uses 212, 646, 718 — not 415 (San Francisco).
3. For mass tests, mix countries: it helps surface i18n bugs.