385 Area Code: Salt Lake City and the Wasatch Front

The 385 area code is Salt Lake City, Utah — an all-services overlay that has issued numbers across the entire Wasatch Front alongside 801 since March 2009, serving Ogden, Bountiful, Salt Lake City, Murray, Lehi, American Fork, Orem, Provo and Spanish Fork from one shared map. The two codes are interchangeable on coverage, cost and dialing; which one a new line receives depends only on where prefix stock happens to sit on ordering day.

See 385 on a missed call? The display reads Wasatch Front — Salt Lake City, Ogden, Provo — the neighborly look outbound businesses prize, but spoofing can hang those digits on traffic from anywhere, so the code alone proves nothing.

385 at a glance

Quick fact	Answer
In service since	March 2009 (first 385 prefixes activated March 29, 2009)
Overlay	Itself an all-services overlay of 801, covering the identical footprint
Territory anchors	Salt Lake City, Ogden, Provo, Orem, Lehi
Dialing	Ten-digit local, mandatory since March 1, 2009
Exhaust projection	Q3 2035 for the combined 385/801 pool (April 2026 NANPA analysis)

What the three digits don’t show is the near miss. For nine years, 385 existed only on paper — assigned in the spring of 2000 as the second half of a geographic split that would have renumbered Provo and Ogden while Salt Lake City kept its digits. That split was postponed three times, suspended outright, and finally torn up. The overlay dialing today is the do-over.

801 kept the metro, 435 took the rest

Into the late 1990s a single code — 801 — covered every telephone in Utah, a holdover from the numbering plan’s first generation of statewide assignments. The first cut came from the Bellcore era of numbering administration: Planning Letter PL-NANP-065 (May 30, 1997) recorded that US WEST had reported continued number growth statewide and that Utah’s Public Service Commission had approved a geographic split in response.

The Salt Lake City–Ogden–Provo metropolitan corridor — generally the counties of Salt Lake, Utah, Davis, Weber and Morgan — retained 801. Everything else in the state became 435 at 12:01 a.m. on Sunday, September 21, 1997. A test number, 435-792-0049, answered from September 7 so carriers could prove their routing, and the letter was explicit that local calling areas and seven-digit local dialing would not change. The metro kept its digits and its habits; only the far side of the state relabeled.

Renumber Provo and Ogden, keep Salt Lake: the 2000 plan

Growth along the Front kept coming, and on April 26, 2000 the commission approved a second split — the strangest map in this code’s file. Under PL-231 (May 31, 2000), the new 385 was to consist of two disconnected pieces: a southern lobe taking American Fork, Orem, Provo and Spanish Fork, and a northern lobe taking Ogden, Morgan, Kaysville and Bountiful. Salt Lake County, sitting between them, kept 801 — one new code, split across two territories that never touch.

The cutover was set for 2:00 a.m. on December 31, 2000, with either code accepted until 2:00 a.m. on June 30, 2001. US WEST published three test numbers — Orem, Farmington and Kaysville — to be dialable by New Year’s Eve, and Farmington drew the memorable one: 385-447-0385, a line wearing the new code at both ends.

The date that never held

Eight weeks before the cutover, PL-248 (November 6, 2000) delayed the split. A year later, PL-308 (October 29, 2001) delayed it again. PL-326 (October 22, 2002) recorded the commission’s October 10, 2002 order pushing implementation out to March 2005 — a date that also never arrived. PL-337 (June 23, 2004) reported the end of the line: on June 21, 2004, the commission vacated the dialing dates entirely in Dockets 99-999-04 and 99-999-05, and the split creating 385 was suspended until further notice.

A relief plan that can wait five years is a shortage that never arrived on schedule. The same era shelved projects elsewhere — Raleigh’s 984 overlay spent that decade in a similar drawer — but Utah’s dormant file was odder cargo: half of a split, its test numbers already reserved and its boundary maps already drawn.

The 2007 rewrite: same map, second code

On July 12, 2007, the commission closed the loop in Docket No. 07-999-01, rescinding and vacating its split order and approving an all-services distributed overlay in its place. PL-366 (August 16, 2007), which formally replaces every earlier 385 letter, laid out the calendar: new-code prefixes orderable from September 29, 2008, permissive ten-digit dialing from June 1, 2008, mandatory ten-digit dialing at 12:01 a.m. on March 1, 2009, and the first 385 prefixes cleared to activate on March 29, 2009.

The verification line this time was 385-600-1234, answering from December 1, 2008 through June 1, 2009. The decisive difference from the 2000 plan: nobody renumbered. Provo and Ogden kept every 801 number they had, and the young code simply began covering the same ground — the shape nearly every modern area code addition has taken since.

Do 385 and 801 dial any differently?

No. Since March 1, 2009, every local call across the two codes takes all ten digits and toll calls take 1 plus ten — the plan PL-366 published, and no NANPA planning letter has touched Utah since. The timing aged well: when the 988 crisis line pushed 82 seven-digit area codes onto ten-digit dialing in 2021, Planning Letter PL-556 (January 8, 2021, superseding PL-544) listed the affected codes state by state, and Utah appears nowhere in that table. The Front had done the work twelve years early.

A 2035 date that keeps sliding later

NANPA’s April 2026 NPA exhaust analysis — built on utilization data reported through March 1, 2026 — projects the combined 385/801 pool out of assignable prefixes in the third quarter of 2035. Watch the direction of travel, though: the late-2023 study said the first quarter of 2031, and every forecast since has pushed the date later — 3Q 2031, 2Q 2032, 1Q 2034, 3Q 2034, now 3Q 2035. Five straight cycles, each buying more runway.

The July 6, 2026 correction to that study revised four Texas entries and left Utah’s rows alone. For scale, 435 — the 1997 spin-off holding the rest of the state — posts the first quarter of 2076. And exhaust in an overlay complex triggers a relief proceeding, not a renumbering: whatever regulators eventually order, working 385 and 801 numbers stay exactly as they are.

Turning 385 digits into answered calls

For a business dialing into the corridor — a recruiter working the tech campuses around Lehi, a contractor bidding Davis County roofs, a supplier calling Ogden docks — a 385 or 801 display reads as a neighbor, and local presence does measurable work on answer rates. The two codes carry identical weight on a call screen; matching the rate center matters more than which of the pair shows up.

What no display can prove is who is calling, because caller ID spoofing can hang Wasatch Front digits on traffic from anywhere. The proof rides inside the call as a STIR/SHAKEN signature — and that is where SIPNEX works: an FCC-licensed carrier provisioning local DID numbers in both 385 and 801, matched to the rate center you need, delivering them over SIP trunking to any PBX or dialer, and signing outbound calls at A-level attestation under its own certificate. Toll-free, under SIPNEX’s RespOrg registration, joins the order whenever the campaign runs one.

Settling the common 385 questions

What cities does the 385 area code cover?

The 385 area code covers Utah’s Wasatch Front: Salt Lake City, Ogden, Provo, Orem, Bountiful, Kaysville, Farmington, Clearfield, Murray, Midvale, Lehi, American Fork, Pleasant Grove, Springville, Spanish Fork, Payson and Morgan. It shares every rate center with 801 — generally Salt Lake, Utah, Davis, Weber and Morgan counties — so the two codes cover identical ground on NANPA’s overlay map.

What separates a 385 number from an 801 number?

Only in age. 385 has been an all-services overlay on the exact 801 footprint since March 2009, so both codes issue numbers for the same Wasatch Front rate centers at the same cost, with the same ten-digit dialing. Nothing about a line’s location, price or reach follows from which of the two codes it wears.

Why did the 385 area code take nine years to launch?

Because it was created for a split that never happened. Utah approved a two-piece split of 801 in April 2000 and NANPA assigned 385 for it, but the cutover was postponed in 2000, 2001 and 2002, suspended in 2004, and rescinded in July 2007 in favor of an overlay. The first 385 prefixes were cleared to activate on March 29, 2009 — nearly nine years after assignment, with no number changes for anyone.

Do local calls in the 385 area code require ten digits?

Yes. Every local call across 385 and 801 has required all ten digits since March 1, 2009, when the overlay’s permissive dialing window closed; toll calls take 1 plus ten. That conversion ran more than a decade ahead of the 988 crisis-line changes of 2021, whose 82-code list in NANPA Planning Letter PL-556 contains no Utah entry at all.

When will the 385 and 801 area codes run out of numbers?

NANPA’s April 2026 exhaust analysis projects the third quarter of 2035 for the combined 385/801 pool. That date has moved later in five consecutive forecasts — from the first quarter of 2031 in the late-2023 study — and the July 2026 correction left Utah’s rows untouched. Local DID inventory across both codes remains orderable by rate center today.

---

Nine years on paper taught this code patience; your rollout shouldn’t need any. SIPNEX provisions 385 and 801 numbers under its own FCC carrier license, routes them anywhere over dialer-grade SIP trunking, and signs every outbound call at A-level attestation on a certificate issued to SIPNEX itself. See published pricing, reach the SIPNEX carrier team, or dial (833) 665-2220.