House prices in Cranbourne Drive, Chorley PR6
1 - 20 of 20
| Address | Last sale | Price paid | |
|---|---|---|---|
|
1 Cranbourne Drive PR6 0LJ
|
Jan 2017
Nov 2000
£54,000
|
£130,000 | |
|
2 Cranbourne Drive PR6 0LJ
|
Jul 2018
|
£126,000 | |
|
5 Cranbourne Drive PR6 0LJ
|
Dec 2021
Jun 2011
£110,000
|
£177,500 | |
|
7 Cranbourne Drive PR6 0LJ
|
Oct 2001
|
£58,000 | |
|
8 Cranbourne Drive PR6 0LJ
|
Sep 2022
Mar 2005
£159,000
Mar 2004
£108,000
|
£247,500 | |
|
11 Cranbourne Drive PR6 0LJ
|
Jul 2021
Mar 2018
£125,000
|
£231,000 | |
|
12 Cranbourne Drive PR6 0LJ
|
Jan 2017
Jan 2017
£134,000
Jun 2015
£118,000
Apr 2002
£60,000
|
£134,000 | |
|
14 Cranbourne Drive PR6 0LJ
|
Oct 2014
|
£118,000 | |
|
15 Cranbourne Drive PR6 0LJ
|
Jul 2017
|
£156,000 | |
|
16 Cranbourne Drive PR6 0LJ
|
Dec 2003
|
£91,500 | |
|
17 Cranbourne Drive PR6 0LJ
|
May 2000
|
£57,750 | |
|
19 Cranbourne Drive PR6 0LJ
|
Nov 2013
Apr 2002
£82,500
Aug 1996
£70,000
|
£166,250 | |
|
20 Cranbourne Drive PR6 0LJ
|
Dec 2019
Jul 2019
£112,500
|
£160,000 | |
|
21 Cranbourne Drive PR6 0LJ
|
May 2010
|
£121,000 | |
|
23 Cranbourne Drive PR6 0LJ
|
Feb 2018
|
£116,000 | |
|
25 Cranbourne Drive PR6 0LJ
|
Oct 2007
Feb 2023
£169,000
Oct 2007
£149,950
|
£149,950 | |
|
26 Cranbourne Drive PR6 0LJ
|
Apr 2022
Apr 2008
£125,000
|
£165,000 | |
|
29 Cranbourne Drive PR6 0LJ
|
May 2006
May 2006
£147,000
|
£147,000 | |
|
35 Cranbourne Drive PR6 0LJ
|
Apr 2006
|
£141,000 | |
|
37 Cranbourne Drive PR6 0LJ
|
Jun 2000
|
£62,450 | |
Data on sold house prices, such as the results above for Cranbourne Drive Chorley PR6, 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.