Subject property
EPC register Nothing typed by hand- Floor area
- 82 m²
- EPC assessor measurement — not IPMS
- Property type
- House, end-terrace
- EPC
- Built
- 1900 to 1929
- EPC age band B
- Habitable rooms
- 5
- Not bedrooms — no source
- Extensions
- 0
- EPC
- Energy rating
- D
- Lodged 16 Nov 2020
- Certificate lodged for
- Marketed sale
- Most reliable transaction type
- Bedrooms · condition · tenure
- Not available from open data
- Manual
Six of these eight fields came from one lookup. The two that did not — bedrooms and condition — are exactly the fields that keep a researcher and a valuer in the loop. Nothing here was typed by hand, and nothing was assumed.
1. Location
Live- Postcode
- —
- Coordinates
- —
- District
- —
- Ward
- —
- LSOA
- —
2. Candidate comparables
Live HM Land RegistrySearching…
| Select | Address | Postcode | Sold | Price | Type | Tenure | Floor area |
|---|---|---|---|---|---|---|---|
| No search run yet. | |||||||
3. Comparable analysis
Live UK House Price IndexBuilding…
4. Environmental and area records
Report section 7What is genuinely live here, and what is not
Three sources run live in your browser: api.postcodes.io for postcode resolution and radius search, landregistry.data.gov.uk SPARQL for recorded sales since 1995, and data.police.uk for street-level crime. All three are Open Government Licence, need no API key and permit commercial use.
The seven marked Server or Manual are not callable from a browser — they need an API key, a hosted bulk dataset, or a WMS. In production every one runs server-side, which is the correct architecture regardless: the server controls key handling, caching, retries and the provenance record.
Interface built with GOV.UK Frontend v5.14.0 (MIT) in unbranded mode — GDS Transport and GOV.UK branding are reserved for service.gov.uk, so the typeface and accent are our own.