Kuwait phone numbers: format, mobile prefixes, validation and SMS rules

Kuwait phone numbers use the country code +965 and have 8 digits, with no area code and no trunk prefix. Mobile numbers start with 41, 5, 6 or 9, such as 500 XXXXX or 9XXX XXXX; from abroad you just put +965 in front: +965 500 XXXXX, stored in E.164 as +96550XXXXXX. Landlines start with 2. The prefix doesn't tell you the network: mobile numbers have been portable since 15 June 2013.

This guide is part of our phone numbers by country series. The tables are generated from libphonenumber's metadata, our MNP atlas and our public catalog. Example numbers are masked with X. The code samples use libphonenumber's own example numbers, which are for testing only; don't call or text them. On 2026-11-08 we read the numbering plan and decisions of the Communication and Information Technology Regulatory Authority (CITRA), its notices to the ITU and the operators' and press reports on portability. Several CITRA decisions are published in Arabic only. This is a summary, not legal advice.

What does a Kuwait phone number look like?

A Kuwaiti number is eight digits with no 0 in front and no area code. CITRA's National Number Plan, last updated on 10 August 2023, sets the whole scheme in one table (CITRA, 2023):

The plan adds one sentence that matters for validation: "All Kuwaiti eight-digit number ranges starting with the digits (41), (5), (6), and (9) are to be considered valid numbers in Kuwait's National Numbering Plan." CITRA allocates blocks inside those ranges to licensed operators on application, and it doesn't notify the ITU of each allocation. It first announced this layout to the ITU in August 2021 and repeated it in September 2022, asking networks abroad to open all the ranges (ITU, 2022).

Two lines need a word. The "Toll-free: 7 digits" row is how libphonenumber types the 18 corporate numbers, such as 180X XXX; CITRA calls them corporate numbers. They are not mobiles. And libphonenumber writes mobiles starting 5 as 500 XXXXX (three and five digits), while numbers starting 6 or 9 come out as 9XXX XXXX. The digits are the same either way, so don't validate the grouping.

Store only the E.164 form: +965 and the eight digits, with no spaces, dashes or brackets. Because there is no trunk prefix, nothing is dropped: 500 12345, +965 500 12345 and 00965 5001 2345 are the same number.

Which prefixes are mobile numbers?

CITRA's answer is simple: 41, 5, 6 and 9. libphonenumber's answer is not. The generator counted every 8-digit number that the library's mobile pattern for KW accepts:

Only nine two-digit blocks are fully mobile in the library: 41, 50, 55, 66, 90, 94, 96, 97 and 99. Others are partly covered, such as 51, 60, 65 and 98, and many have only a few four-digit sub-blocks, often with repeated digits. Blocks that appear in no row at all, 53, 54 and 59, are rejected entirely. The library lists the blocks its maintainers have seen in use, while CITRA opens the whole range in advance.

This is the most important fact in this guide for developers:

So a Kuwaiti number that libphonenumber calls invalid may still be a working mobile, if it is 8 digits in a CITRA mobile range. That is the reverse of the usual problem, where a library accepts numbers that don't exist. The code below keeps those numbers apart instead of throwing them away.

Who holds the blocks?

Kuwait has three mobile network operators: Zain (9), Ooredoo (6) and stc (5), which traded as VIVA until it rebranded in December 2019 (stc, 2019). The 41 range belongs to Virgin Mobile, which launched in May 2022 as Kuwait's first mobile virtual network operator, an operator that uses another company's network (Developing Telecoms, 2022).

libphonenumber's carrier data for +965 (965.txt) has one line per first digit and, as we read it on 2026-11-08, still names "VIVA" for 5, almost seven years after the rebrand. Even a current name shows only who received the range. A ported number keeps its digits, so look up the current network per number.

What are 18 numbers and short numbers?

None of these can receive an OTP, so reject them in a mobile field.

Why does a simple regex fail for Kuwaiti numbers?

Most tutorials give "8 digits starting with 5, 6 or 9", sometimes with 4. Each version is wrong in a different way:

• [569]\d{7} misses the 41 range.
• [4569]\d{7} accepts 40, 42… which are not in the plan.
• The CITRA-exact pattern 41\d{6}|[569]\d{7} matches the plan, but says nothing about which blocks are in service.

And the library is stricter than the plan, as shown above. Our post on why an E.164 regex is not enough shows the same problem elsewhere. For Kuwait, the honest answer combines both: the library for "known in use", CITRA's ranges for "possible", and a live lookup for "in service".

How do I validate a Kuwaiti number in code?

Remove spaces and punctuation, parse with full metadata and the default region KW, and return one of four answers: a known mobile, a number in a CITRA mobile range the library doesn't know yet, a valid number that isn't a mobile, or invalid. You can try single numbers first in our free phone number validator.

Python (pip install phonenumbers):

import re

import phonenumbers
from phonenumbers import PhoneNumberType

# CITRA's plan: every 8-digit number starting 41, 5, 6 or 9 is a valid mobile number.
CITRA_MOBILE = re.compile(r"41\d{6}|[569]\d{7}")


def classify_kw(raw: str) -> tuple[str | None, str]:
    """(E.164 or None, "mobile" | "citra_range" | "not_mobile" | "invalid") for a Kuwaiti number."""
    s = re.sub(r"[\s().-]", "", raw)
    try:
        n = phonenumbers.parse(s, "KW")
    except phonenumbers.NumberParseException:
        return None, "invalid"
    if phonenumbers.region_code_for_country_code(n.country_code) != "KW":
        return None, "invalid"
    e164 = phonenumbers.format_number(n, phonenumbers.PhoneNumberFormat.E164)
    if phonenumbers.is_valid_number(n):
        if phonenumbers.number_type(n) == PhoneNumberType.MOBILE:
            return e164, "mobile"
        return None, "not_mobile"
    # libphonenumber knows only part of the 5, 6 and 9 ranges; CITRA opens all of them.
    if CITRA_MOBILE.fullmatch(str(n.national_number)):
        return e164, "citra_range"
    return None, "invalid"


# Inputs with X are masked; the demo fills X with 0 and masks the result again.
for raw in ["500 12345", "+965 500 12345", "00965 5001 2345", "52XX XXXX", "62XX XXXX",
            "40XX XXXX", "2234 5678", "1801 234", "500 1234"]:
    e164, kind = classify_kw(raw.replace("X", "0"))
    if e164 and "X" in raw:
        e164 = e164[:6] + "X" * (len(e164) - 6)
    print(f"{raw!r:18} -> {(e164, kind)}")

JavaScript (npm install libphonenumber-js):

import { parsePhoneNumberFromString } from "libphonenumber-js/max";

// CITRA's plan: every 8-digit number starting 41, 5, 6 or 9 is a valid mobile number.
const CITRA_MOBILE = /^(?:41\d{6}|[569]\d{7})$/;

/** [E.164 or null, "mobile" | "citra_range" | "not_mobile" | "invalid"] for a Kuwaiti number. */
export function classifyKw(raw) {
  const input = String(raw).replace(/[\s().-]/g, "");
  const phone = parsePhoneNumberFromString(input, "KW");
  if (!phone || phone.countryCallingCode !== "965") return [null, "invalid"];
  if (phone.isValid()) return phone.getType() === "MOBILE" ? [phone.number, "mobile"] : [null, "not_mobile"];
  // libphonenumber knows only part of the 5, 6 and 9 ranges; CITRA opens all of them.
  return CITRA_MOBILE.test(phone.nationalNumber) ? [phone.number, "citra_range"] : [null, "invalid"];
}

// Inputs with X are masked; the demo fills X with 0 and masks the result again.
for (const raw of ["500 12345", "+965 500 12345", "00965 5001 2345", "52XX XXXX", "62XX XXXX",
                   "40XX XXXX", "2234 5678", "1801 234", "500 1234"]) {
  let [e164, kind] = classifyKw(raw.replaceAll("X", "0"));
  if (e164 && raw.includes("X")) e164 = e164.slice(0, 6) + "X".repeat(e164.length - 6);
  console.log(JSON.stringify(raw).padEnd(18), "->", JSON.stringify([e164, kind]));
}

We ran both on 2026-11-08 (Python 3.12 with phonenumbers 9.0.40, Node.js 24 with libphonenumber-js 1.13.13). The unmasked inputs are libphonenumber's example numbers, plus a 7-digit version of the mobile example. Both returned the same answers; this is the Python output (JavaScript prints arrays with double quotes and null):

'500 12345'        -> ('+96550012345', 'mobile')
'+965 500 12345'   -> ('+96550012345', 'mobile')
'00965 5001 2345'  -> ('+96550012345', 'mobile')
'52XX XXXX'        -> ('+96552XXXXXX', 'citra_range')
'62XX XXXX'        -> ('+96562XXXXXX', 'citra_range')
'40XX XXXX'        -> (None, 'invalid')
'2234 5678'        -> (None, 'not_mobile')
'1801 234'         -> (None, 'not_mobile')
'500 1234'         -> (None, 'invalid')

The first three are one number written three ways. The two citra_range rows are numbers that libphonenumber rejects but CITRA's plan allows; keep them, mark them unconfirmed and confirm them before you rely on them. 40… isn't in any mobile range. The landline and the corporate 18 number are valid but not mobile, and the last input is one digit short.

The generated test table runs the raw library call over masked inputs. The shape regex column tests the "4, 5, 6 or 9" tutorial pattern, after spaces, dashes and brackets are removed:

Rows 8 and 10 are the ones to remember:

1. Row 8: 40 passes the loose regex, but only 41 is a mobile range in CITRA's plan, and libphonenumber rejects it too.
2. Row 10: the 18 corporate number is valid, as TOLL_FREE in the library. It can't receive an SMS.

For a whole file, our free phone list cleaner normalises numbers to E.164 and removes duplicates in your browser. Our Python and JavaScript guides cover more languages. Kuwait's metadata changes often (see "What changed recently?"), so update the library regularly; each update moves numbers from citra_range to mobile.

Does number portability change the carrier?

Yes. Mobile number portability (MNP) started on Saturday 15 June 2013, as a Ministry of Communications initiative before CITRA existed. Zain said customers could switch at its branches, keep their number and pay nothing for the move (Zain, 2013). CITRA was set up by Law No. 37 of 2014 and now regulates porting.

In December 2025 CITRA announced a full regulatory framework for portability. As reported in the Kuwaiti press (The Times Kuwait, 2025):

• Who can port. Prepaid, postpaid and data lines, 50 days after first activation, and again 90 days after the previous port. A user can switch between prepaid and postpaid while porting.
• One stop. The receiving operator handles the whole port, and the old contract ends automatically when it is done.
• 12 hours. A port must be completed within 12 hours, and the user can choose a porting date up to 30 days after applying.
• Fees. The receiving operator may charge up to 5 Kuwaiti dinars per successful port; the donor operator may charge nothing. CITRA can change the cap.
• No win-back pressure. Operators may not contact users to influence their decision or offer incentives without CITRA's approval.
• A central database. Licensed intermediaries run a central portability database and report on technical performance weekly and monthly. Breaches are punished under Law No. 37 of 2014.

A separate decision signed by CITRA's chairman requires the mobile operators to report every month, within the first eight working days, all ports of the previous month: successful, rejected and cancelled, plus numbers returned to their range holders (Arab Times, 2025). We found no published porting totals.

Our MNP atlas has no verified row for Kuwait yet.

The facts above are what we would add to the atlas. Our MNP atlas compares portability across countries, and how to check if a phone number is ported shows the lookup. With thirteen years of porting and a 12-hour process, the first digit is only a hint. For routing, pricing or fraud rules, look up the current network per number.

What are the rules for SMS, caller ID and personal data?

These summarise the decisions and reports as we read them on 2026-11-08. Not legal advice; ask counsel how they apply to you.

Personal data: CITRA's regulation and the e-commerce law

Kuwait has no general personal data protection law. Two instruments do most of the work (DLA Piper, 2025):

• The Data Privacy Protection Regulation. CITRA issued it by Decision No. 26 of 2024 on 7 February 2024. It replaced Decision No. 42 of 2021 and its amendments, and applies from its publication in the official gazette (CITRA decision, Arabic). It covers CITRA's licensed service providers, under a definition broad enough to reach websites, apps and cloud services that process personal data. Providers must show their terms in Arabic and English, state the purpose and obtain consent before providing the service, delete the data when consent is withdrawn, record transfers abroad and the countries involved, and report a personal data breach to CITRA and the people affected within 24 hours.
• The E-Commerce Law, Law No. 20 of 2014. It forbids collecting or processing personal data without the person's consent, and forbids passing it on without consent or a court order.

DLA Piper lists "no specific provisions" for electronic marketing. So there is no Kuwaiti equivalent of an opt-in rule for SMS in a statute, but consent is still the basis for processing the number at all.

Sender names and bulk SMS

Business SMS in Kuwait goes out from registered alphanumeric sender names, not from ordinary mobile numbers. CITRA's Decision No. 165 of 2024 (10 June 2024) requires the mobile operators to interconnect their bulk SMS services and fixes the settlement rate between operators at 5 fils per message (CITRA decision, Arabic). That is a wholesale rule between networks, not the price a business pays.

The registration rules themselves are set by the operators. Messaging providers document them like this (AWS; Unifonic; Clickatell):

• Register the sender name first. Every sender name is pre-registered with the networks. A local company needs its Kuwaiti commercial registration or trade licence, the civil ID of an authorised signatory and a signed, stamped no-objection letter on company letterhead; providers ask for separate letters for Ooredoo and Zain, and also cover stc and Virgin.
• Promotional names are marked. Promotional sender names must begin with AD-, and promotional and transactional names are registered separately. A name registered as transactional may not carry promotional content.
• No numbers as senders. Short codes and long numbers aren't supported for business SMS; use an alphanumeric name.
• Opt-in and opt-out. Marketing messages must include opt-in and opt-out instructions.
• Content limits. Political, adult and gambling content is not allowed.

Providers differ in details, so check yours before a campaign.

Arabic text uses a different SMS encoding from Latin text, so a message splits into more parts sooner. Our SMS character counter shows how many parts a bilingual message will take.

Caller names and "My Numbers"

CITRA issued a bylaw on caller name identification in public telecom networks by Decision No. 28 of 2024 on 13 February 2024 (CITRA decision, Arabic). The decision is public; we couldn't extract the bylaw's text, so we don't describe its details.

On 16 August 2026 CITRA launched "My Numbers" in the government's Sahel app. Citizens and residents can see every mobile number and telecom service registered under their name with any operator, and CITRA asked everyone to review the list (CITRA, 2026). For a business, that confirms that a Kuwaiti line is registered to a named person. It doesn't tell you who uses a number today, and our checks never return a subscriber's name.

If you send customer numbers to a check service, decide with counsel which consent or contract covers it and how the transfer rules apply to a provider outside Kuwait. Our posts on whether a phone number is personal data and on consent for WhatsApp checks give the baseline we work to: your own customers, a stated purpose, minimal data and honoured objections.

Which messaging apps and channels reach people in Kuwait?

We found no official statistics on messaging-app use in Kuwait, so measure your own customers rather than trusting a market average. SMS reaches every active mobile and remains the fallback for OTP, but only from a registered sender name.

Customer lists in Kuwait often mix +965 numbers with residents' home-country numbers. Normalise every row with its own country, not a default of KW, and check foreign numbers with their own country's rules. Our Qatar guide covers the neighbouring market, which has a similar flat 8-digit plan.

The method is the same as in our channel-by-country guide: check which apps your opted-in customers are registered on, route each one to the channel they use, and keep SMS as the fallback. To open a chat without saving a contact, our WhatsApp link generator builds a wa.me link from the E.164 number.

How do I check WhatsApp registration for a Kuwaiti customer list?

Classify every row with classify_kw() first. A check tells you whether a number is registered at the time of the check. It can't tell you whether the person wants your messages:

See WhatsApp number check for the fields. It runs in real time and in bulk jobs.

What changed recently?

The rows for KW and +965 in our numbering-plan changes dataset, built from libphonenumber's release notes:

Latest numbering-plan updates for KW: 2025-07-02 (v9.0.9), 2024-02-07 (v8.13.30), 2023-03-09 (v8.13.8), 2022-09-08 (v8.12.55), 2022-02-09 (v8.12.43).

Thirteen metadata updates since 2019 is a lot for one flat plan. It fits the picture above: the library adds Kuwaiti blocks as they come into use, while CITRA's plan already allows them. The other changes were in the market and the rules:

• 2013: mobile portability started (15 June).
• 2014: Law No. 37 set up CITRA, and the E-Commerce Law (No. 20) required consent for personal data.
• 2019: VIVA rebranded as stc (December).
• 2021: CITRA's earlier data privacy regulation (Decision No. 42 of 2021), and the current numbering layout notified to the ITU (August).
• 2022: Virgin Mobile launched on the 41 range (May).
• 2024: the new Data Privacy Protection Regulation (7 February), the caller name identification bylaw (13 February) and the bulk SMS interconnection decision (10 June).
• 2025: the portability framework (December).
• 2026: "My Numbers" in the Sahel app (16 August).

What can MobileValidate check for Kuwaiti numbers?

Generated from our public catalog:

Catalog data as of 2026-11-07.

* bulk jobs only. The live list is at GET /v1/services.

A lookup returns network and registration facts. It never returns a subscriber's name or address, and we don't offer "number details" searches.

One limit to know: our API parses numbers with the same library, so as of 2026-11-08 a number in the citra_range group above comes back as invalid_number. That answer is never billed, but it means we can't check those numbers yet either. Numbers that libphonenumber knows, which is most numbers in use, run through every check in the table.

For Kuwaiti numbers, a live network status (HLR) check shows whether a number is reachable right now, whether it has been ported and which network serves it. An MNP lookup answers porting alone, and the carrier lookup gives the line type. Our free MCC-MNC lookup turns the network code in an answer into an operator name. For channels, WhatsApp and Telegram run in real time and in bulk; the starred checks run in bulk jobs only.

How do I start for free?

• 20 free real checks. Every live account can run 20 phone numbers and 10 e-mail addresses through the real checks for free on the dashboard's Try it page. Use them on your own number first.
• A free carrier lookup. The carrier lookup page has a public form for 3 lookups a day, no sign-up needed.
• Free tools. The phone number validator and phone list cleaner check format in your browser; all of them are on the tools page.
• A free test key. Get a test key for the sandbox. It gives fixed test answers so you can build every branch of your code; see test mode.
• A free estimate. POST /v1/jobs/estimate takes the same body as a job, checks nothing and shows the maximum cost before you start.
• Then add credit. Create your account; approval is automatic. Top-ups of larger amounts get 5% to 10% bonus credit; see pricing. Unknown, invalid and duplicate results are never charged.

A bulk flow for a Kuwaiti customer list

1. Export the numbers you hold with consent or another lawful basis, one per row.
2. Classify them with classify_kw(), or upload them as they are with default_country=KW, so 500 XXXXX is read as Kuwaiti. Keep the citra_range rows aside for now.
3. Run POST /v1/jobs/estimate with your checks, for example hlr and whatsapp, and read the cost breakdown.
4. Start the job, then download the results as CSV or NDJSON.

curl https://api.mobilevalidate.com/v1/jobs \
  -H "Authorization: Bearer $MOBILEVALIDATE_API_KEY" \
  -F file=@customers.csv -F checks=hlr,whatsapp -F default_country=KW

For single numbers, here is a small reachability check against the real-time endpoint. It uses the public sandbox key mv_test_publicSandboxn9ZgneuhR1B9CRfKG3fulym and our test values. The sandbox accepts only those UK drama numbers, so the example uses them; with a live key, pass the E.164 numbers that classify_kw() marked mobile.

import os

import requests  # pip install requests

API = "https://api.mobilevalidate.com/v1/lookup"
KEY = os.environ["MOBILEVALIDATE_API_KEY"]


def reachability(numbers: list[str]) -> dict[str, tuple]:
    """Per E.164 number: (reachable or unreachable, ported?, current network MCC-MNC). None means we don't know."""
    r = requests.post(API, headers={"Authorization": f"Bearer {KEY}"}, timeout=15,
                      json={"numbers": numbers, "checks": ["hlr"], "wait": 5})
    r.raise_for_status()
    out = {}
    for row in r.json()["results"]:
        hlr = row["checks"]["number.hlr"]
        a = (hlr["attributes"] or {}) if hlr["status"] == "completed" else {}
        out[row["e164"]] = (a.get("status"), a.get("ported"), a.get("mcc_mnc"))
    return out


for number, info in reachability(["+447700900001", "+447700900002", "+447700900003"]).items():
    print(number, info)

We ran it against the sandbox on 2026-11-08. It printed:

+447700900001 ('reachable', False, '23415')
+447700900002 ('unreachable', False, '23415')
+447700900003 (None, None, None)

The first test value is reachable and not ported, the second exists but is unreachable (switched off or out of coverage), and the third stands for a timeout: all three fields are None and it isn't billed. Keep None apart from False: None means we don't know. Requests with 20 or more consecutive numbers are refused (403 suspected_enumeration), and our acceptable use policy forbids finding recipients for unsolicited messages. People can object through our opt-out form.

What are the key takeaways?

• Kuwaiti numbers have 8 digits with no area code and no trunk prefix. Mobiles start with 41, 5, 6 or 9, landlines with 2, and 18 corporate numbers have 7 digits. In E.164, put +965 in front and change nothing else.
• CITRA's plan opens the whole 41, 5, 6 and 9 ranges; libphonenumber knows only the blocks seen in use. A number it rejects may still be real: mark it unconfirmed instead of deleting it.
• The first digit shows the original operator at most. Porting has existed since 15 June 2013, and the 2025 framework makes a port a 12-hour, one-stop process.
• Kuwait has no general data protection law. CITRA's 2024 Data Privacy Protection Regulation and the 2014 E-Commerce Law make consent the basis for processing a number.
• Business SMS needs a sender name registered with the networks; promotional names begin with AD-, and marketing messages need opt-in and opt-out instructions.
• Check WhatsApp or network status only for customers you hold lawfully, and never treat registration as consent.

Platform, regulator and company names are used descriptively. MobileValidate is not affiliated with any of them.