16153 E 200 S Clearfield UT 84015
- Latitude
- 41.11103
- Longitude
- -112.01653
- ZCTA centroid
- 41.1204, -112.0608
- Time zone
- America/Denver
Coordinates fall inside the ZIP boundary. Street numbers are drawn from ranges with no delivery point. The city name shown is the official place boundary for this point — the USPS last-line city source is not yet live for every ZIP.
Utah Address Data
Every figure below is measured from the underlying dataset, not estimated — the same data the generator above draws from. Need more than a handful of records? Bulk export returns up to 10,000 rows in one request, with no account required.
ZIP codes in the published dataset
Counties represented
UT address format
USPS Publication 28 last line: West Valley City, UT 84120
Telephone area codes
Bounding box / centroid
Top real street names
- S Main St276 segments
- S 400 E248 segments
- N Main St239 segments
- S 900 E235 segments
- S 300 W232 segments
- N 400 E230 segments
Street-suffix distribution
- Dr15950 streets
- W15040 streets
- S14876 streets
- E9893 streets
- N9763 streets
- St7341 streets
Population (counties represented)
Sum of Census county population for every county represented in the published dataset.
Utah cities in the published dataset
Utah has 1 Utah cities with their own generator page and 0 more listed below with too few published data points yet for a page of their own.
| City | ZIP codes | Records | Own page |
|---|---|---|---|
| Salt Lake City | 12 | 16 | Yes |
Frequently Asked Questions
Is it legal to use a random address generator for Utah addresses?
Yes, for testing and development — using a random address generator becomes illegal only when the output is used to deceive a real system, such as a government form or a bank. See the full legal guide for the specific statute, 18 U.S.C. § 1342, and what it actually covers.
Will these Utah addresses pass address validation?
They pass format and parser validation, because every Utah record is postal-format-valid per USPS Publication 28. They deliberately fail Delivery Point Validation, because the street number is drawn from a range with no registered delivery point — both are intentional.
Could a generated Utah address belong to a real person?
No. Every Utah record is built for geographic coherence from one point on a real street, with a street number chosen outside any range assigned to a real delivery point, so the address does not describe a real resident. The full method is on the methodology page.
Do the ZIP codes, counties and area codes across Utah always agree with real geography?
Yes. Utah has 90 usable ZIP codes across 5 counties in the dataset, and every generated record's county and area code are derived from the same point as its ZIP code, checked on every build. See the validation harness for the exact method.
Can I generate Utah addresses in bulk?
Yes — up to 10,000 rows at once, in CSV, JSON, NDJSON, or SQL, with no account required. Add ?seed= to get the same Utah records back on every run, which is useful for a CI fixture.
What is the difference between a fake address and a random address generator?
A fake address is meant to deceive a real recipient. A random address generator like Fake Addresses produces postal-format-valid, non-deliverable Utah test data with no real recipient and no deception intended — the full comparison is in this guide.
More Utah test data
Prohibited uses of Fake Addresses test dataProhibited use
Do not use these addresses to deceive anyone. Do not use them on government forms, tax filings, financial or KYC applications, school-enrolment records, voter registration, insurance claims, shipping labels, or anywhere a truthful address is legally required. In the US, using a fictitious address to defraud through the mail is a federal crime under 18 U.S.C. § 1342.