763 Area Code: Coon Rapids, Blaine, Maple Grove

The 763 area code is the north and northwest suburban ring of Minneapolis, Minnesota — Coon Rapids, Blaine, Fridley, Brooklyn Center, Maple Grove, Plymouth, and Golden Valley close in, with Anoka, Elk River, Monticello, Buffalo, and Cambridge farther out — split from 612 on February 27, 2000, never overlaid, and still dialing seven digits for a local call.

North-metro routine — a Maple Grove clinic, a Coon Rapids contractor, a Blaine school office — accounts for most 763s you can’t place. A caller ID display was never built to vouch for the caller, and this one doesn’t.

763, tabulated

On file	763
Live from	12:01 a.m. Central, February 27, 2000
Carved out of	612 — the northern half of a three-way split
Second code on top	None; no relief docket open
Suburbs served	Coon Rapids, Blaine, Maple Grove, Plymouth, Elk River
A local call takes	Seven digits; 1 plus ten also permitted
Prefix supply	Fourth quarter of 2109 (NANPA, April 2026)

Two documents carry nearly the whole story. One is a fourteen-page order the Minnesota Public Utilities Commission issued on April 6, 1999, reversing its own plan and drawing this code’s territory for the first time. The other is NANPA’s Planning Letter PL-200, which turned that order into a calendar. Very little in the file has changed since.

How the 763 area code came out of a reversal

By late 1998 the old 612 — already stripped of St. Paul, which had moved to 651 that July — was still consuming prefixes fast enough that the Commission had been rationing them by lottery since January 1998. On December 15, 1998, it ordered Phase II of its relief plan in Docket P-999/M-97-506: Minneapolis and Richfield (by city limits) and Fort Snelling (by wire center) would be cut out of 612 and handed a brand-new code, 952, while the western suburbs kept the 1947 digits.

The order admits the timing was partly forced. A new FCC order barred state commissions from rationing prefixes without a relief decision on the books, so the Commission decided first and invited argument afterward. Public hearings in Richfield, Eden Prairie, and Minneapolis on February 17–19, 1999 drew about 65 people. Nearly 1,200 written comments arrived by March 5 — three-quarters favoring an overlay, most of them prompted by a US WEST letter asking its business customers to write in.

US WEST, AT&T, Sprint, and an industry group speaking through NANPA all pushed for an all-services overlay. The counter-proposal came from city hall: on March 3, 1999, Richfield filed City Resolution No. 8683 asking the Commission to leave 612 with Minneapolis, Richfield, and Fort Snelling and split the rest of the old territory into two new codes. The state Department of Public Service also backed keeping 612 downtown, though it wanted a single new code for the suburbs.

The Order After Reconsideration of April 6, 1999 adopted Richfield’s version. Minneapolis, Fort Snelling, Richfield, and St. Anthony — the last added so it would not become a one-town “peninsula” between two other codes — kept 612. The remainder was divided into a northern half and a southern half, each with its own new code.

The ordering paragraphs assigned no digits to either half. The only new code the order names is 952 — reserved by NANPA for the original one-code plan and, as a footnote records, not yet officially assigned — and 763 appears nowhere in it. NANPA’s NPA database records both 763 and 952 assigned to Minnesota on July 22, 1999.

The Commission’s stated reason for two codes instead of one was runway. NANPA had projected a single suburban code lasting 4.9 years and the Minneapolis core 6.6; the Department’s figures were 9.8 and 9.5. Splitting the suburbs in two, the order said, offered “a long-term, perhaps permanent, solution” — and it added that, with 612 assigned to Minneapolis, the city’s own exhaust “may prove shorter than the suburbs.”

Which suburbs are in the 763 area code?

The order defined the northern code as “the suburbs north and west of Minneapolis, down to approximately I-394,” listing Columbia Heights, Fridley, Mounds View, Blaine, Cambridge, Princeton, Becker, Monticello, Buffalo, Waverly, Montrose, Delano, Independence, Medina, Maple Grove, Plymouth, and Golden Valley. Below the interstate, the southern code took Bloomington, Burnsville, Minnetonka, Wayzata, and St. Louis Park. The line follows municipal boundaries for most of its length; only in the rural stretch west of the Medina–Long Lake/Orono border does it run along wire centers instead.

PL-200’s own roll call for 763 adds Brooklyn Center, Coon Rapids, Circle Pines, Lexington, St. Francis, Isanti, and Elk River. Its prefix tables, drawn from the November 1999 LERG, group the code into fourteen rate centers — the large Twin Cities rate center, Osseo (where Maple Grove’s prefixes sit), Becker, Big Lake, Cambridge, Enfield, Glendorado, Monticello, Montrose–Waverly, Princeton, Rogers, St. Michael, Zimmerman, and — for the Maple Plain and Delano prefixes — Mound. The footprint runs from the Minneapolis city line through Anoka County and out to the Sherburne, Wright, and Isanti County towns.

One caveat from the same order still shapes the map. Wireless carriers held roughly 165 prefixes in the old 612, and the Commission let them keep those prefixes — and request more in either new code — regardless of where their switches sat. PL-200’s tables show the trace: prefixes marked with an asterisk are “duplicated codes in either or both NPAs,” with Minneapolis-labelled blocks appearing in both the 612 and 763 lists and Wayzata blocks in both 763 and 952.

PL-200 sets the calendar

NANPA issued Planning Letter PL-200 on November 29, 1999, under the subject line “612 NPA Split, Creating 763 and 952 NPAs – Minnesota.” It recorded the Commission’s approval of a three-way geographic split and set the calendar: the split and the start of permissive dialing at 12:01 a.m. Central on February 27, 2000 — the date NANPA’s database carries as the in-service date for both new codes. The April order had set permissive dialing to begin December 1, 1999, pulled forward from January 2000 to keep it clear of Y2K; the schedule NANPA published that November ran to the later date.

Burglar- and fire-alarm customers got the longest grace: until November 1, 2001 to repoint dialers set to the old code, some nine months after permissive dialing — either code reaching a 763 number — had closed for everyone else at 12:01 a.m. Central on January 14, 2001, and calls carrying the wrong code had begun reaching an intercept recording.

The test number carriers verified routing against was 763-571-1599. The letter listed prefixes as of November 24, 1999 — tables it reissued on January 17, 2001 “for legibility,” the only revision it ever received — and the split map itself, drawn by the Minnesota Department of Public Service, was for copyright reasons never reproduced in it.

Seven digits north of the interstate

PL-200 said the new codes would inherit 612’s dialing plan unchanged: seven digits for a local call inside the home code, ten or 1 plus ten for a local call into a neighboring code, 1 plus ten for toll. NANPA’s database records the same plan for 763 today — seven-digit local calls within the code, with 1 plus ten permitted on them as well.

The plan survived the event that ended seven-digit dialing across much of the country. When 988 became the national crisis line, NANPA’s Planning Letter PL-556 (January 8, 2021) listed 82 area codes that both allowed seven-digit dialing and had a 988 prefix in use; those converted to mandatory ten-digit dialing on October 24, 2021, after permissive dialing from April 24. Minnesota’s two entries were 218 and 952 — the southern twin from the 2000 split. 763 was not on the list, so nothing changed for it.

One line of the April 1999 order wrote an asymmetry into a call at the code’s northern edge, and NANPA’s dialing columns for 320 still reflect it. Cambridge, bound for the new northern code, shared an extended-area-service route with Braham in 320. The Commission ruled that Braham subscribers could keep dialing seven digits into Cambridge while Cambridge subscribers would dial ten digits back — an asymmetry written, the order says, to preserve prefixes in the code facing exhaust rather than in 320, which faced none.

A forecast that shed 33 years and still reads 2109

For 763 the reading is the fourth quarter of 2109 — NANPA’s 2026-1 NPA Exhaust Analysis, April 2026, working from utilization reported as of March 1, 2026. The preceding 2025-2 edition had said the third quarter of 2142; NANPA footnotes the 131-quarter pullback as increased historical and projected demand. Earlier editions read 1Q2080, 3Q2085, 3Q2105, and 4Q2111 — a forecast that has wandered across six decades, every point of it beyond any horizon on which relief gets planned.

The 1999 order’s prediction held. Of the three codes carved from the old 612, the one that kept the original digits runs out first — Minneapolis’s 612 in the first quarter of 2048 — while 952 sits in NANPA’s over-100-years tier and 763 reads 2109. 651 is forecast to the fourth quarter of 2100, northern Minnesota’s 218 to the third quarter of 2036. The July 6, 2026 revision NANPA posted afterward amended four Texas forecasts; Minnesota’s were not among them.

Nothing else in the file points toward relief. NANPA’s database carries 763 with no overlay, no jeopardy declaration, and no relief planning in progress; the August 2026 relief-planning status report runs to twelve codes, none of them Minnesota’s, and the exhausting-within-36-months report names three, none of them here. Minnesota’s only overlay to date, 924, sits over southern Minnesota’s 507. What an exhaust date actually counts is the subject of our NPA-NXX explainer; the overlay-versus-split trade-off the Commission weighed in 1999 is laid out in our area code guide.

One quadrant of the Twin Cities, on the display

Within the metro, 763 reads as a specific place — Anoka County and the northwest Hennepin suburbs, not downtown and not the south side — and because no second code has ever been laid over it, a 763 display still narrows a caller to one quadrant of the Twin Cities. For an outbound team courting Maple Grove retailers or Blaine homeowners, matching that expectation is the case local presence dialing makes; a 612 or out-of-state display does not earn the same pickup.

The digits cannot do the vetting. Caller-ID spoofing prints 763 on traffic from anywhere, which is why the durable trust signal is the STIR/SHAKEN signature a carrier applies to calls it originates for a customer it knows.

SIPNEX holds its FCC carrier authority directly and issues local DID numbers by rate center — Twin Cities, Osseo, Cambridge, or any other US market with inventory on the day — delivered over SIP trunking to the PBX, softphone, or dialer already in place. Outbound calls leave signed at A-level attestation on SIPNEX’s own STIR/SHAKEN certificate, and toll-free numbers run under SIPNEX’s RespOrg registration.

What callers ask about 763

Which cities are in the 763 area code?

Coon Rapids, Blaine, Fridley, Brooklyn Center, Maple Grove, Plymouth, Golden Valley, and Anoka close in; Elk River, Monticello, Buffalo, Delano, Princeton, and Cambridge farther out. The Minnesota PUC’s 1999 order defined the territory as the suburbs north and west of Minneapolis down to roughly I-394, drawn mostly along city limits; Minneapolis, Richfield, St. Anthony, and Fort Snelling stayed on 612, and the suburbs south of the interstate took 952.

When did 763 split from area code 612?

At 12:01 a.m. Central on February 27, 2000, the date NANPA’s Planning Letter PL-200 set for both the split and the start of permissive dialing. Either code reached a 763 number until January 14, 2001 — November 1, 2001 for alarm lines — after which misdials hit an intercept recording. NANPA’s database records the code assigned on July 22, 1999, three and a half months after the Minnesota PUC’s order after reconsideration approved two new codes for the suburbs.

Why did Minneapolis keep 612 while the suburbs got 763?

Because the Minnesota PUC reversed itself on April 6, 1999. Its December 15, 1998 order had assigned Minneapolis, Richfield, and Fort Snelling the new code and left 612 with the suburbs; after nearly 1,200 comments and a Richfield city resolution proposing the alternative, the Commission ruled that the hub of government, business, and entertainment should keep its identity, and split the suburbs into two codes so each side got a long runway. The order itself predicted 612 might run out sooner than either suburb — NANPA’s current forecast agrees.

Can 763 local calls still be dialed with seven digits?

Yes. NANPA’s database lists seven-digit dialing for local calls within 763, with 1 plus ten digits also permitted, and 1 plus ten for toll calls. The 2021 conversion to ten-digit dialing for the 988 crisis line, set out in NANPA’s Planning Letter PL-556, applied only to codes with a 988 prefix in use — Minnesota’s were 218 and 952. 763 was not listed, so the plan PL-200 inherited from 612 in 2000 remains in force.

Will a second code ever be laid over 763?

No — nothing is planned or pending. NANPA’s April 2026 exhaust analysis projects 763’s prefix supply lasting to the fourth quarter of 2109; its database records no overlay, no jeopardy entry, and no relief work in progress; and the code appears on neither the relief-planning status report nor the exhausting-within-36-months report. When relief is eventually needed, the standard remedy is an overlay that leaves existing numbers unchanged — and local DIDs in 763 rate centers remain orderable today.

---

Two suburban codes, a city that kept its number, and a forecast that reaches into the twenty-second century — 763 is the settled half of a fight Minneapolis nearly lost. SIPNEX provisions north-metro numbers under its own FCC carrier license, routes them anywhere over SIP trunking, and signs every outbound call at A-level attestation on its own certificate. Talk to the SIPNEX team, review pricing, or call (833) 665-2220.