House prices in Naseby Rise, Queensbury, Bradford BD13 1QP
1 - 24 of 24
Address | Last sale | Price paid | |
---|---|---|---|
1 Naseby Rise BD13 1QP
|
Jun 2018
|
£219,000 | |
3 Naseby Rise BD13 1QP
|
Sep 2000
|
£84,950 | |
4 Naseby Rise BD13 1QP
|
Aug 2019
|
£180,000 | |
5 Naseby Rise BD13 1QP
|
Jun 2009
|
£155,000 | |
6 Naseby Rise BD13 1QP
|
Oct 2005
Oct 2002
£98,950
Jul 1996
£59,900
|
£144,550 | |
7 Naseby Rise BD13 1QP
|
Nov 2020
Jul 2015
£185,000
Sep 2005
£142,000
Jan 1996
£65,000
|
£220,000 | |
8 Naseby Rise BD13 1QP
|
Aug 2003
|
£119,000 | |
9 Naseby Rise BD13 1QP
|
May 1996
|
£52,000 | |
15 Naseby Rise BD13 1QP
|
Jun 2005
Feb 1997
£72,000
|
£119,000 | |
16 Naseby Rise BD13 1QP
|
Oct 1998
|
£86,500 | |
19 Naseby Rise BD13 1QP
|
Feb 2019
Sep 2003
£88,000
Jan 1998
£48,250
|
£124,000 | |
21 Naseby Rise BD13 1QP
|
Jan 2001
Mar 1995
£48,000
|
£51,500 | |
23 Naseby Rise BD13 1QP
|
Mar 2005
|
£124,995 | |
24 Naseby Rise BD13 1QP
|
Feb 2004
|
£132,000 | |
25 Naseby Rise BD13 1QP
|
Aug 2001
Aug 1995
£69,000
|
£83,000 | |
26 Naseby Rise BD13 1QP
|
Jan 2001
Sep 2000
£59,950
|
£69,500 | |
30 Naseby Rise BD13 1QP
|
Jul 2007
Jul 2004
£115,000
Dec 1996
£51,000
|
£147,500 | |
31 Naseby Rise BD13 1QP
|
Jul 1998
|
£72,500 | |
32 Naseby Rise BD13 1QP
|
May 2011
|
£185,000 | |
33 Naseby Rise BD13 1QP
|
Nov 2000
|
£71,950 | |
35 Naseby Rise BD13 1QP
|
Jan 2016
Jan 2016
£173,000
Nov 2015
£190,000
|
£173,000 | |
39 Naseby Rise BD13 1QP
|
Sep 2020
|
£205,000 | |
41 Naseby Rise BD13 1QP
|
Dec 2002
|
£156,500 | |
43 Naseby Rise BD13 1QP
|
May 1998
|
£82,500 | |
Data on sold house prices, such as the results above for Naseby Rise Queensbury Bradford BD13 1QP, is supplied to us via monthly updates from the Land Registry for England and Wales and from the Registers of Scotland for Scotland. There may be a delay of up to 3 months from when a property is actually sold to when it becomes officially recorded with Land Registry and/or Registers of Scotland. We provide data on house prices for information only, on an 'as is' basis as supplied to us and accept no liability for any errors or omissions. If you have identified any incorrect information in, please Report an error.