House prices in Princes Drive, Leamington Spa CV32
1 - 22 of 22
Address | Last sale | Price paid | |
---|---|---|---|
2 Princes Drive CV32 6AE
|
Mar 2000
|
£132,500 | |
6 Princes Drive CV32 6AE
|
Apr 2022
Jul 2010
£207,000
|
£430,000 | |
8 Princes Drive CV32 6AE
|
May 2010
Jul 2004
£234,000
|
£245,000 | |
10 Princes Drive CV32 6AE
|
Jan 2011
Jul 2005
£248,500
|
£244,500 | |
14 Princes Drive CV32 6AE
|
Apr 2003
|
£250,000 | |
The Annexe, 14 Princes Drive CV32 6AE
|
Feb 2019
|
£229,500 | |
14a Princes Drive CV32 6AF
|
Apr 2004
|
£200,000 | |
20 Princes Drive CV32 6AF
|
Oct 2015
Oct 2015
£292,000
|
£292,000 | |
24 Princes Drive CV32 6AF
|
Jan 2003
Oct 1999
£118,000
May 1995
£77,500
|
£184,450 | |
26 Princes Drive CV32 6AF
|
Oct 2006
Jul 2000
£125,000
|
£219,000 | |
28 Princes Drive CV32 6AF
|
May 2014
|
£196,000 | |
34 Princes Drive CV32 6AF
|
Oct 2020
|
£335,000 | |
36 Princes Drive CV32 6AF
|
Nov 1999
Dec 1995
£66,000
|
£110,000 | |
40 Princes Drive CV32 6AF
|
Feb 2013
|
£230,000 | |
42 Princes Drive CV32 6AF
|
Mar 2009
Nov 1999
£136,000
Jul 1995
£89,000
|
£222,000 | |
44 Princes Drive CV32 6AF
|
Dec 2009
Mar 2002
£177,500
Feb 2001
£147,000
Feb 2000
£130,000
Jun 1999
£76,500
|
£250,000 | |
48 Princes Drive CV32 6AF
|
Dec 2006
|
£196,000 | |
50 Princes Drive CV32 6AF
|
May 2014
Jul 1997
£115,000
|
£307,000 | |
52 Princes Drive CV32 6AF
|
Mar 2021
|
£335,000 | |
54 Princes Drive CV32 6AF
|
May 2003
|
£171,000 | |
58 Princes Drive CV32 6AF
|
Jan 2003
Apr 1998
£95,000
|
£193,500 | |
64 Princes Drive CV32 6AF
|
Mar 2021
Jul 2014
£285,000
|
£430,000 |
Data on sold house prices, such as the results above for Princes Drive Leamington Spa CV32, 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.