House prices in Parkdale Grove, Glasgow G53
1 - 21 of 21
| Address | Last sale | Price paid | |
|---|---|---|---|
|
1 Parkdale Grove G53 7ZL
|
Sep 2007
Sep 2007
£240,000
|
£240,000 | |
|
2 Parkdale Grove G53 7ZL
|
Jul 2014
Oct 2007
£240,000
|
£189,995 | |
|
5 Parkdale Grove G53 7ZL
|
Nov 2007
|
£250,000 | |
|
6 Parkdale Grove G53 7ZL
|
Oct 2007
|
£225,000 | |
|
7 Parkdale Grove G53 7ZL
|
Jan 2012
Oct 2011
£200,000
Jan 2008
£250,000
|
£175,000 | |
|
8 Parkdale Grove G53 7ZL
|
Dec 2020
Oct 2014
£205,000
Jan 2008
£240,000
|
£80,000 | |
|
9 Parkdale Grove G53 7ZL
|
Nov 2007
|
£245,000 | |
|
10 Parkdale Grove G53 7ZL
|
Dec 2007
|
£245,000 | |
|
11 Parkdale Grove G53 7ZL
|
Jul 2016
Jul 2016
£215,000
May 2012
£180,000
Dec 2007
£245,000
|
£215,000 | |
|
14 Parkdale Grove G53 7ZL
|
Jan 2020
|
£255,000 | |
|
15 Parkdale Grove G53 7ZL
|
Nov 2013
Dec 2007
£250,000
|
£195,000 | |
|
16 Parkdale Grove G53 7ZL
|
Mar 2019
Apr 2016
£220,000
Jan 2008
£250,000
|
£250,000 | |
|
17 Parkdale Grove G53 7ZL
|
Aug 2017
Dec 2007
£247,000
|
£256,000 | |
|
18 Parkdale Grove G53 7ZL
|
Apr 2021
Feb 2008
£226,000
|
£255,000 | |
|
20 Parkdale Grove G53 7ZL
|
Apr 2009
Apr 2009
£210,000
|
£210,000 | |
|
22 Parkdale Grove G53 7ZL
|
Sep 2015
Feb 2008
£222,000
|
£210,000 | |
|
24 Parkdale Grove G53 7ZL
|
Oct 2019
Feb 2008
£218,000
Oct 2007
£233,000
|
£231,000 | |
|
26 Parkdale Grove G53 7ZL
|
Apr 2016
Dec 2008
£230,000
|
£220,000 | |
|
28 Parkdale Grove G53 7ZL
|
Dec 2015
|
£200,000 | |
|
30 Parkdale Grove G53 7ZL
|
May 2016
|
£175,000 | |
|
32 Parkdale Grove G53 7ZL
|
Mar 2014
|
£180,000 | |
Data on sold house prices, such as the results above for Parkdale Grove Glasgow G53, 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.