Zip Code 92376

ZIP code 92376 covers Rialto, California, in San Bernardino County — and it has a shape that makes people stop and look twice. Most of it is a compact block of city. Then there is a second piece, roughly 55 miles to the north, with nothing obvious connecting the two. We get asked about this one often enough that we made a video about it, below.

The short answer is that the shape is not a mistake. It is what happens when you draw a boundary around something that was never a boundary in the first place.

ZIP code 92376 at a glance

Those population and household figures are given as ranges on purpose. Different providers publish different numbers for the same ZIP — we found 84,548 and 85,727 for population, and 21,997 and 20,378 for households, depending on the source and the survey year. That is not sloppiness on anyone’s part, and it is the first clue to what is going on here.

Why the boundary looks wrong: ZIP codes are not areas

A ZIP code is not a shape. It is a collection of mail delivery routes, maintained by the USPS for the purpose of sorting mail efficiently. A route is a sequence of delivery points — addresses — not a region with an edge. The USPS has never published an official ZIP code boundary map, because from its point of view there is nothing to publish.

Everything you have ever seen described as a “ZIP code boundary” is therefore a reconstruction, and there are two main ways to build one:

• Census ZCTAs. The Census Bureau builds ZIP Code Tabulation Areas by taking census blocks and assigning each one to whichever ZIP most of its addresses use. The result is tidy, contiguous and good for demographics. This is where the 13.3 square miles comes from — a compact block of Rialto that plainly does not include anything 55 miles away.
• Delivery-point polygons. Commercial providers draw a shape around the actual addresses the USPS assigns to a ZIP. This is closer to operational reality, and it is where odd shapes appear — because a handful of remote delivery points really can sit a long way from the rest of the route.

Both are legitimate. They answer different questions, which is why they disagree, and why a ZIP that measures 13 square miles in one dataset can look like it spans half a county in another.

Why this matters if you are building sales territories

If you assign accounts to reps by ZIP code, an outlier like 92376 causes three specific problems.

Drive time stops matching the map. A rep who owns 92376 appears to own one neighbourhood. If the northern piece is in their dataset, they own something an hour and a half away that no route plan accounts for.

Area-based balancing misleads you. Splitting territories so each rep gets a similar amount of land is already a weak method. With a ZIP like this one it is actively wrong — the vast majority of the addresses sit in a fraction of the mapped area. Balance on accounts, revenue or population instead, never on square miles.

Your two systems will not agree. If your CRM uses one ZIP boundary file and your mapping tool uses another, the same account can land in two different territories, and the disagreement will be blamed on the software rather than on the data underneath it.

How to check any ZIP code yourself

When a ZIP looks wrong, resolve it against the addresses rather than the polygon. Look the ZIP up in the USPS ZIP Code Lookup Tool linked below to see which city names it actually accepts, and compare that against what your boundary file is drawing. If the two disagree, trust the addresses — they are the thing the USPS is actually maintaining.

In AlignMix, territories are built from the accounts themselves rather than from a boundary file, so a ZIP with a stray delivery point 55 miles north does not quietly reassign a customer to the wrong rep. If you are wrestling with ZIP-level assignments across thousands of accounts, our guide to updating ZIP code territory assignments in bulk covers the practical side, and what is a ZIP code boundary goes deeper into where these shapes come from.

Links:

• Google Zip Code 92376
• USPS Zip Code Lookup Tool