A Valid UK Address Example
A valid United Kingdom address example has a delivery-address line (house number or name plus street), an optional locality line for a village or district inside a larger town, and a last line carrying the post town and the postcode on its own line beneath it — for instance "14 Example Road" on the first line and "BRISTOL" then "BS1 4ND" on the two lines that follow. A UK postcode always splits into an outward code (one or two letters plus one or two digits, occasionally followed by a letter) and an inward code (always one digit followed by two letters), separated by a single space, the way UPU S42 documents national postal-code templates varying in both shape and position from one country to the next.
Every United Kingdom record Fake Addresses generates carries a real postcode and resolves it to a real county or unitary authority by testing the postcode's own point against a real administrative-area boundary. What the record does not carry is a real post town or a real street name: no free UK source reaches street level today, so the delivery-address line on a generated record is clearly synthesised rather than presented as if it were a real delivery point, and the line shown in place of a post town is the resolved administrative-area name, not a genuine Royal Mail post town.
That distinction matters for a QA engineer specifically because a postcode that looks right but sits next to the wrong administrative area is exactly the kind of bug a validation-focused test suite should catch. Fake Addresses keeps the postcode and the resolved area genuinely tied to one real point rather than composing the two independently, so a United Kingdom test record stays internally consistent even though its street line is a synthetic placeholder rather than a claim about a real address.
UK Postcode Format and Examples
A UK postcode never exceeds seven characters excluding the space, and the space between the outward and inward code is always present in the standardised, printed form:
| Outward code | Inward code | Full postcode | Pattern |
|---|---|---|---|
| SW1A | 1AA | SW1A 1AA | 2 letters, 1 digit, 1 letter — 1 digit, 2 letters |
| M1 | 1AE | M1 1AE | 1 letter, 1 digit — 1 digit, 2 letters |
| CR2 | 6XH | CR2 6XH | 1 letter, 1 digit, 1 digit — 1 digit, 2 letters |
| DN55 | 1PT | DN55 1PT | 2 letters, 2 digits — 1 digit, 2 letters |
How UK Address Format Compares to the United States and Canada
United Kingdom addresses put the postal code on its own final line rather than folding it into the same line as the city, which is the single biggest structural difference a QA engineer moving between these three markets will hit first:
| Country | Last-line order | Postal-code position |
|---|---|---|
| United Kingdom | Post town, then postcode on its own line beneath it | Final line, on its own |
| United States | City, State, ZIP+4 | End of the last line, per USPS Publication 28 |
| Canada | City, two-letter province, postal code | End of the last line, two spaces before the code |
Synthetic Test Data Generation for UK Test Addresses
Synthetic test data generation for the United Kingdom depends on the postcode structure above holding exactly, because a validation integration built against real UK address-lookup services checks that structure before it checks anything else. A generated record whose postcode fails the outward/inward pattern would not exercise the code path a QA engineer actually needs tested — it would just be rejected before the interesting logic ever runs, which defeats the purpose of using generated data at all.
Fake Addresses states its United Kingdom coherence level plainly on the random UK address generator rather than implying a precision the underlying data cannot support: a real postcode resolved to a real administrative area by point-in-polygon, with a synthetic street line, because no free UK source reaches street level. A QA engineer who needs to know exactly what is real and what is synthesised in a given field can read that distinction on the generator page itself rather than guessing from the output alone.
Every United Kingdom record this site produces is also non-deliverable by construction. No free UK street-level address data is ingested at all, so the synthesised delivery-address line cannot coincide with a real delivery point, which is what keeps a UK test fixture safe to commit to a public repository or run through a live validation integration without any risk of resolving to somebody's actual address.
Frequently asked questions
Does a UK postcode always have the same number of characters?
No. A UK postcode ranges from five to seven characters excluding the space, because the outward code can carry one or two letters and one or two digits before the fixed one-digit-plus-two-letter inward code. Fake Addresses generates only real, structurally valid postcodes, never an invented pattern.
Why does the postcode sit on its own line in a UK address?
UK address format puts the post town and the postcode last, with the postcode conventionally set apart from the town name, which is the opposite convention from a US ZIP+4 folded into the same line as the city and state. Fake Addresses follows this UK-specific structure on every generated record.
Is a Fake Addresses UK street address real?
No, and it is not meant to look real: no free UK source reaches street level, so the delivery-address line on a generated United Kingdom record is a clearly synthetic placeholder. The postcode itself is real and resolves to a real administrative area, which is the coherence level Fake Addresses actually claims for the United Kingdom.
Sources
- Universal Postal Union — The Universal Postal Union runs an addressing-solutions programme, including international addressing standards and assistance to member countries whose addresses do not follow a US or UK-style format.
- United States Postal Service — Postal Explorer — USPS Publication 28 defines a "standardized address" as one using official USPS abbreviations, and a "complete address" as one containing everything needed to match the ZIP+4 and City State files.