House prices in Deeley Close, Watnall, Nottingham NG16 1FY
1 - 21 of 21
Address | Last sale | Price paid | |
---|---|---|---|
2 Deeley Close NG16 1FY
|
Feb 2007
|
£250,000 | |
4 Deeley Close NG16 1FY
|
Oct 2006
|
£261,500 | |
6 Deeley Close NG16 1FY
|
Apr 2006
|
£222,000 | |
8 Deeley Close NG16 1FY
|
Jan 2007
Jan 2007
£249,950
|
£249,950 | |
10 Deeley Close NG16 1FY
|
Apr 2021
Dec 2011
£198,000
Jul 2006
£225,000
|
£287,500 | |
12 Deeley Close NG16 1FY
|
Mar 2011
Jul 2006
£280,000
|
£230,000 | |
14 Deeley Close NG16 1FY
|
Jul 2015
Mar 2013
£249,999
Apr 2006
£325,000
|
£285,000 | |
16 Deeley Close NG16 1FY
|
Jul 2006
|
£270,000 | |
18 Deeley Close NG16 1FY
|
May 2006
|
£249,950 | |
20 Deeley Close NG16 1FY
|
Dec 2021
Jun 2006
£245,000
|
£390,000 | |
22 Deeley Close NG16 1FY
|
Dec 2018
Dec 2018
£264,000
Feb 2007
£355,000
|
£264,000 | |
24 Deeley Close NG16 1FY
|
Jun 2018
Jul 2005
£300,000
|
£300,000 | |
26 Deeley Close NG16 1FY
|
Aug 2018
Aug 2005
£260,000
|
£318,500 | |
28 Deeley Close NG16 1FY
|
Jun 2014
Jan 2006
£350,000
|
£324,000 | |
30 Deeley Close NG16 1FY
|
May 2018
Aug 2005
£330,000
|
£335,000 | |
32 Deeley Close NG16 1FY
|
Jul 2022
Dec 2005
£340,000
|
£427,500 | |
34 Deeley Close NG16 1FY
|
Dec 2005
|
£340,000 | |
36 Deeley Close NG16 1FY
|
Jul 2005
|
£370,000 | |
38 Deeley Close NG16 1FY
|
Jul 2013
Jul 2010
£245,000
Jun 2005
£230,000
|
£250,000 | |
40 Deeley Close NG16 1FY
|
Jun 2005
|
£340,000 | |
42 Deeley Close NG16 1FY
|
Nov 2004
|
£295,000 |
Data on sold house prices, such as the results above for Deeley Close Watnall Nottingham NG16 1FY, 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.