TL;DR: The table below lists area codes by state for all 50 states and Washington, DC, rebuilt line by line from the North American Numbering Plan Administrator NPA report dated November 18, 2026. That file carries 372 in-service geographic area codes across the 50 states and DC, and 262 of them are overlays, meaning the old one code one region model is now the exception rather than the rule. California holds 41 codes, Texas 29, New York 23, Florida 23 and Illinois 17, while 11 states still run on a single code: Alaska, Delaware, Hawaii, Maine, Montana, North Dakota, New Hampshire, Rhode Island, South Dakota, Vermont and Wyoming. Nine codes entered service between March 2024 and June 2026 and are missing from most lists still in circulation: 235 in Missouri, 924 in Minnesota, 357 in California, 748 in Colorado, 729 in Tennessee, 457 in Louisiana, 471 in Mississippi, 483 in Alabama and 465 in New York. Three more are already scheduled: 565 in Georgia on December 6, 2027, 451 in North Carolina on September 21, 2028, and 761 in Kentucky, currently in trigger status. For a rep working a list, the operating takeaway is narrower than the table suggests. An area code tells you which numbering plan area a number was issued in. It does not tell you where the person is sitting today, what time it is there, or whether you are allowed to call.
Most lists of area codes by state are copies of copies. Somebody scraped a table a few years back, somebody else reformatted it, and the version your rep is looking at has not been checked against the numbering authority since. That is how you end up with a prospect in a brand new overlay whose number your routing rules treat as invalid, or a territory map that silently misses a code serving half a metro.
So this one is rebuilt from the source. Every code in the table came out of the NPA report published by the North American Numbering Plan Administrator, the body that actually assigns these codes, in the file dated November 18, 2026. Nothing was carried over from an older list.
Area Codes by State Reference Table
Codes shown are geographic area codes in service in each state as of the November 18, 2026 file. Toll free codes (800, 833, 844, 855, 866, 877, 888) are not tied to a state and are left out, as are codes serving US territories rather than states.
| State | Abbr | Area codes in service | Count |
|---|---|---|---|
| Alabama | AL | 205, 251, 256, 334, 483, 659, 938 | 7 |
| Alaska | AK | 907 | 1 |
| Arizona | AZ | 480, 520, 602, 623, 928 | 5 |
| Arkansas | AR | 327, 479, 501, 870 | 4 |
| California | CA | 209, 213, 279, 310, 323, 341, 350, 357, 369, 408, 415, 424, 442, 510, 530, 559, 562, 619, 626, 628, 650, 657, 661, 669, 707, 714, 738, 747, 760, 805, 818, 820, 831, 837, 840, 858, 909, 916, 925, 949, 951 | 41 |
| Colorado | CO | 303, 719, 720, 748, 970, 983 | 6 |
| Connecticut | CT | 203, 475, 860, 959 | 4 |
| Delaware | DE | 302 | 1 |
| Florida | FL | 239, 305, 321, 324, 352, 386, 407, 448, 561, 645, 656, 689, 727, 728, 754, 772, 786, 813, 850, 863, 904, 941, 954 | 23 |
| Georgia | GA | 229, 404, 470, 478, 678, 706, 762, 770, 912, 943 | 10 |
| Hawaii | HI | 808 | 1 |
| Idaho | ID | 208, 986 | 2 |
| Illinois | IL | 217, 224, 309, 312, 331, 447, 464, 618, 630, 708, 730, 773, 779, 815, 847, 861, 872 | 17 |
| Indiana | IN | 219, 260, 317, 463, 574, 765, 812, 930 | 8 |
| Iowa | IA | 319, 515, 563, 641, 712 | 5 |
| Kansas | KS | 316, 620, 785, 913 | 4 |
| Kentucky | KY | 270, 364, 502, 606, 859 | 5 |
| Louisiana | LA | 225, 318, 337, 457, 504, 985 | 6 |
| Maine | ME | 207 | 1 |
| Maryland | MD | 227, 240, 301, 410, 443, 667 | 6 |
| Massachusetts | MA | 339, 351, 413, 508, 617, 774, 781, 857, 978 | 9 |
| Michigan | MI | 231, 248, 269, 313, 517, 586, 616, 679, 734, 810, 906, 947, 989 | 13 |
| Minnesota | MN | 218, 320, 507, 612, 651, 763, 924, 952 | 8 |
| Mississippi | MS | 228, 471, 601, 662, 769 | 5 |
| Missouri | MO | 235, 314, 417, 557, 573, 636, 660, 816, 975 | 9 |
| Montana | MT | 406 | 1 |
| Nebraska | NE | 308, 402, 531 | 3 |
| Nevada | NV | 702, 725, 775 | 3 |
| New Hampshire | NH | 603 | 1 |
| New Jersey | NJ | 201, 551, 609, 640, 732, 848, 856, 862, 908, 973 | 10 |
| New Mexico | NM | 505, 575 | 2 |
| New York | NY | 212, 315, 329, 332, 347, 363, 465, 516, 518, 585, 607, 624, 631, 646, 680, 716, 718, 838, 845, 914, 917, 929, 934 | 23 |
| North Carolina | NC | 252, 336, 472, 704, 743, 828, 910, 919, 980, 984 | 10 |
| North Dakota | ND | 701 | 1 |
| Ohio | OH | 216, 220, 234, 283, 326, 330, 380, 419, 436, 440, 513, 567, 614, 740, 937 | 15 |
| Oklahoma | OK | 405, 539, 572, 580, 918 | 5 |
| Oregon | OR | 458, 503, 541, 971 | 4 |
| Pennsylvania | PA | 215, 223, 267, 272, 412, 445, 484, 570, 582, 610, 717, 724, 814, 835, 878 | 15 |
| Rhode Island | RI | 401 | 1 |
| South Carolina | SC | 803, 821, 839, 843, 854, 864 | 6 |
| South Dakota | SD | 605 | 1 |
| Tennessee | TN | 423, 615, 629, 729, 731, 865, 901, 931 | 8 |
| Texas | TX | 210, 214, 254, 281, 325, 346, 361, 409, 430, 432, 469, 512, 621, 682, 713, 726, 737, 806, 817, 830, 832, 903, 915, 936, 940, 945, 956, 972, 979 | 29 |
| Utah | UT | 385, 435, 801 | 3 |
| Vermont | VT | 802 | 1 |
| Virginia | VA | 276, 434, 540, 571, 686, 703, 757, 804, 826, 948 | 10 |
| Washington | WA | 206, 253, 360, 425, 509, 564 | 6 |
| Washington, DC | DC | 202, 771 | 2 |
| West Virginia | WV | 304, 681 | 2 |
| Wisconsin | WI | 262, 274, 353, 414, 534, 608, 715, 920 | 8 |
| Wyoming | WY | 307 | 1 |
That is 372 codes across the 50 states and DC. Four states carry more codes than the entire bottom half of the list combined.
Why One Code No Longer Means One Place
Here is the part that breaks older mental models. Of the 372 codes in the table, 262 are overlays. An overlay is a new code laid on top of a region that already has one, covering the same territory rather than splitting it. Existing customers keep their numbers. New numbers get the new code. Two neighbors on the same street can have different area codes, and two contacts with different codes can be in the same building.

New York City is the clearest example in the file. The 212, 332, 646 and 917 codes form one overlay complex, and 347, 465, 718, 917 and 929 form another. The 917 code belongs to both. So a 917 number means New York City and nothing more precise than that, and no amount of territory logic will squeeze a borough out of it.
Overlays also changed how people dial. The numbering file flags 263 of those 372 codes as requiring all ten digits for a local call inside the same area code. The seven-digit habit only survives in 51 of them. If your team still trains reps to drop the area code on in-state numbers, that training is wrong in roughly seven cases out of ten.
Where new area codes come from
Codes do not appear at random. The numbering administrator collects utilization and forecast data from carriers, projects when each area code will run out of central office codes, and publishes a semi-annual exhaust analysis every April and October. When a code is heading for exhaust, the industry convenes, agrees on a relief plan, sends it to the state regulator for approval, and publishes a planning letter with the implementation schedule. If demand outruns the plan, the administrator can declare jeopardy and ration codes until relief lands.
Ten area codes are in relief planning as of the November 18, 2026 file: 502 in Kentucky, 509 in Washington, 580 in Oklahoma, 626, 657, 714 and 949 in California, 828 in North Carolina, 912 in Georgia and 956 in Texas. Each of those is a candidate to gain an overlay partner, which means any list you build today has a known expiration date in those regions.
The Nine Area Codes Older Lists Miss
Nine geographic codes entered service between March 2024 and June 2026. All nine are overlays, which means they sit inside regions your list already covers, so the gap is easy to miss until a number fails a validation rule.
| Code | State | Overlay complex | In service |
|---|---|---|---|
| 235 | Missouri | 235/573 | March 24, 2024 |
| 924 | Minnesota | 507/924 | August 30, 2024 |
| 357 | California | 357/559 | March 26, 2025 |
| 748 | Colorado | 748/970 | July 7, 2025 |
| 729 | Tennessee | 423/729 | September 5, 2025 |
| 457 | Louisiana | 318/457 | September 25, 2025 |
| 471 | Mississippi | 471/662 | January 30, 2026 |
| 483 | Alabama | 334/483 | February 23, 2026 |
| 465 | New York | 347/465/718/917/929 | June 18, 2026 |
Three more are already approved and dated. Georgia gets 565 on December 6, 2027, joining the 912 complex. North Carolina gets 451 on September 21, 2028, joining 828. Kentucky has 761 assigned against 502 and sitting in trigger status. Put those three on the calendar now rather than finding them when a rep cannot dial one.
What an Area Code Does Not Tell You
This is where a reference table starts doing damage if you ask too much of it. The table answers one question: which numbering plan area issued this number. Teams routinely ask it three more questions it cannot answer.
It does not tell you where the person is
People keep mobile numbers when they move. A rep in Denver can carry a 617 number for a decade. Businesses buy numbers in markets they want to sell into. So the area code records where a number was issued, not where the human answering it lives or works today. Treat it as a weak signal that loses to a verified address record every single time, and keep the inferred field separate from the confirmed one in your CRM so nobody downstream mistakes one for the other.
It does not tell you the local time
The numbering file carries a time zone field, and it disagrees with itself inside 11 states. Florida, Idaho, Indiana, Kansas, Kentucky, Michigan, Nebraska, Nevada, Oregon, Tennessee and Texas all have in-service codes carrying more than one zone value. Tennessee alone carries three. So a rep who derives a calling window from the first three digits will dial somebody an hour earlier than intended often enough to matter, and calling windows are exactly the thing you do not want to get wrong.
It does not tell you whether you may call
Permission is a record, not a prefix. Whether a number can be dialed depends on consent, suppression lists, the National Do Not Call registry and internal do-not-call status, plus whatever the applicable state rules require. None of that is encoded in an area code. A local-looking number is not a legal basis for anything.
Using Area Codes by State in Outbound Calling
There is one place where this table earns its keep operationally, and it is not the contact record. It is the number you dial from.

Local presence dialing matches the caller ID a prospect sees to the area code attached to the number being called. Kixie runs this through a pool of real phone numbers covering area codes across the US, and rotates through several of them so one number is not burned by repeated attempts to the same prospect. The mechanism depends entirely on the mapping in the table above being current. Feed it a stale list and a brand new overlay gets dialed from an out-of-market number, which is the exact thing the feature exists to avoid.
Two caveats worth saying plainly, because this tactic gets oversold. First, a matching area code is not a magic answer rate. Kixie has published its own comparison of local, toll free and out-of-state numbers and what actually gets answered, and the honest version is that number reputation and call volume per number matter alongside the match. If the number you rotate to is already flagged, a perfect area code match will not save the call. That is a caller ID reputation problem, not a numbering problem.
Second, the practice has rules. Displaying a number you control and can be reached at is different from displaying a misleading one, and the boundary matters. Kixie covers it in more depth in how local presence dialing works, and the mechanics live on the local presence feature page.
What to inspect this week
Pull your number list and diff it against the table above. Four things to check, in order:
- Do the nine codes added since March 2024 exist in your validation rules, or do numbers carrying them get rejected or misrouted?
- Does your dialing-from pool cover the overlay partners in the states you actually sell into, or only the older code in each pair?
- Are the inferred location and confirmed location stored in separate CRM fields, and does your calling-window logic read the confirmed one?
- Are the ten area codes in relief planning on a review date, so a new overlay does not surprise you?
Those four take an afternoon. The alternative is finding the gap one failed dial at a time.
Area Codes by State Questions
How many area codes does each state have?
It ranges from one to 41. California has the most at 41 in-service geographic codes, then Texas at 29, New York and Florida at 23 each, and Illinois at 17. At the other end, 11 states run the whole state on a single code.
Which states still have only one area code?
Alaska (907), Delaware (302), Hawaii (808), Maine (207), Montana (406), North Dakota (701), New Hampshire (603), Rhode Island (401), South Dakota (605), Vermont (802) and Wyoming (307). That is 11 states as of the November 18, 2026 numbering file.
Can one area code cover more than one state?
In the current US numbering file each geographic code is listed against a single state or jurisdiction. The practical complication is the reverse case: a single state can hold dozens of codes, and overlay complexes mean several codes share the same ground.
Why did my area code start requiring ten digits?
An overlay was added to the region. Once two codes serve the same territory, seven digits no longer identify a unique number, so local calls move to ten digits. This applies to 263 of the 372 codes in the table.
How often does this list change?
Several times a year. Nine codes entered service in the roughly two and a half years before this file date, three more are scheduled through 2028, and ten existing codes are in active relief planning. A yearly re-check is the minimum; quarterly is better if local presence dialing is part of your motion.
Where should I verify an area code?
Go to the numbering administrator itself. The NPA report linked in the Sources section below is the underlying data file, refreshed continuously, and it carries the in-service date, overlay complex, time zone and dialing plan for every code.
Sources
- North American Numbering Plan Administrator, NPA report data file. Every area code, state assignment, in-service date, overlay complex, time zone and dialing plan in this article comes from this file, dated November 18, 2026. Reviewed November 18, 2026.
- North American Numbering Plan Administrator, NPA Reports index. The published index for the NPA data file and the semi-annual NPA exhaust projections. Reviewed November 18, 2026.
- North American Numbering Plan Administrator, NPA Relief Planning. Describes the relief process, the April and October exhaust analysis schedule, planning letters and jeopardy declarations. Reviewed November 18, 2026.
- Kixie, Local Presence. Product documentation for the number pool and caller ID rotation described in the outbound calling section. Reviewed November 18, 2026.
Sources verified by the Kixie Research Team on November 18, 2026.
Ready to close more deals with Kixie?
See how Kixie's AI-powered tools can transform your sales and support operations.
Start Free Trial