16739 D St Las Vegas NV 89106
- Latitude
- 36.18581
- Longitude
- -115.14733
- ZCTA centroid
- 36.1821, -115.1625
- Time zone
- America/Los_Angeles
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.
Las Vegas 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
89101, 89102, 89104, 89106, 89108, 89109, +14 more
County
FIPS 32003
NV address format
USPS Publication 28 last line: Las Vegas, NV 89117
Telephone area code(s)
State-precision — not yet resolved to county/rate-centre.
Bounding box / centroid
bbox -115.652, 36.094 → -115.008, 36.477
Top real street names
- W Charleston Blvd128 segments
- N Jones Blvd100 segments
- N Torrey Pines Dr94 segments
- N Tenaya Way91 segments
- E Stewart Ave89 segments
- E Charleston Blvd88 segments
Street-suffix distribution
- Ave7097 streets
- St5943 streets
- Dr5218 streets
- Ct2796 streets
- Rd1740 streets
- Ln1679 streets
Population
official place boundary: Las Vegas city
Frequently Asked Questions
Is it legal to use a random address generator for Las Vegas 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 Las Vegas addresses pass address validation?
They pass format and parser validation, because every Las Vegas 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 Las Vegas address belong to a real person?
No. Every Las Vegas 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 code, county and city always agree for Las Vegas test data?
Yes. Clark County, the 702 area code, and the ZIP code shown are all derived from the same generated point inside a single ZIP Code Tabulation Area, checked on every build. See the validation harness for the exact method.
Can I generate Las Vegas 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 Las Vegas 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 Las Vegas test data with no real recipient and no deception intended — the full comparison is in this guide.
Nearby and Related
More Las Vegas 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.