House prices in Rossie Park Drive, Inchture, Perth PH14 9RT
1 - 20 of 20
| Address | Last sale | Price paid | |
|---|---|---|---|
|
1 Rossie Park Drive PH14 9RT
|
Nov 2005
|
£144,000 | |
|
2 Rossie Park Drive PH14 9RT
|
Apr 2006
Jan 2006
£105,000
|
£128,500 | |
|
4 Rossie Park Drive PH14 9RT
|
Dec 2013
|
£145,000 | |
|
6 Rossie Park Drive PH14 9RT
|
Apr 2003
Aug 2002
£70,000
|
£82,000 | |
|
7 Rossie Park Drive PH14 9RT
|
Jun 2015
Jun 2015
£147,500
|
£147,500 | |
|
8 Rossie Park Drive PH14 9RT
|
Dec 2021
Sep 2012
£152,500
Mar 2010
£152,595
May 2006
£145,000
Sep 2005
£130,000
Feb 2005
£105,000
|
£185,000 | |
|
9 Rossie Park Drive PH14 9RT
|
Sep 2014
Oct 2006
£140,000
|
£135,000 | |
|
10 Rossie Park Drive PH14 9RT
|
Jan 2015
|
£148,000 | |
|
11 Rossie Park Drive PH14 9RT
|
Dec 2007
|
£110,000 | |
|
13 Rossie Park Drive PH14 9RT
|
Feb 2011
Nov 2005
£120,000
|
£148,000 | |
|
14 Rossie Park Drive PH14 9RT
|
Jan 2021
|
£160,000 | |
|
15 Rossie Park Drive PH14 9RT
|
Nov 2021
Jul 2018
£180,000
|
£228,000 | |
|
16 Rossie Park Drive PH14 9RT
|
Aug 2015
|
£164,000 | |
|
19 Rossie Park Drive PH14 9RT
|
Sep 2015
|
£144,000 | |
|
20 Rossie Park Drive PH14 9RT
|
Apr 2002
|
£59,999 | |
|
23 Rossie Park Drive PH14 9RT
|
Jun 2014
Dec 2006
£166,066
Jul 2002
£85,500
|
£163,000 | |
|
24 Rossie Park Drive PH14 9RT
|
Nov 2012
Apr 2009
£123,000
|
£138,000 | |
|
25 Rossie Park Drive PH14 9RT
|
Apr 2018
May 2015
£158,000
Nov 2009
£155,000
|
£168,000 | |
|
26 Rossie Park Drive PH14 9RT
|
Dec 2004
|
£102,000 | |
|
27 Rossie Park Drive PH14 9RT
|
Sep 2019
|
£185,000 | |
Data on sold house prices, such as the results above for Rossie Park Drive Inchture Perth PH14 9RT, 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.