House prices in Fortview Terrace, Bridge Street, Cainscross, Stroud GL5
1 - 17 of 17
Address | Last sale | Price paid | |
---|---|---|---|
1 Fortview Terrace, Bridge Street GL5 3ES
|
Jun 2000
Nov 1998
£20,000
|
£30,000 | |
1 Fortview Terrace, Bridge Street GL5 1JL
|
May 2020
|
£173,705 | |
2 Fortview Terrace, Bridge Street GL5 3ES
|
Mar 2002
Jul 1997
£37,500
|
£82,000 | |
2 Fortview Terrace, Bridge Street GL5 1JL
|
May 2020
|
£175,000 | |
2 Fortview Terrace, Bridge Street GL5 1AY
|
Nov 2008
|
£335,000 | |
3 Fortview Terrace, Bridge Street GL5 3ES
|
Dec 2011
|
£99,400 | |
4 Fortview Terrace, Bridge Street GL5 3ES
|
Jun 2021
Nov 2007
£125,000
|
£430,000 | |
5 Fortview Terrace, Bridge Street GL5 3ES
|
Nov 2011
Nov 2011
£117,500
Oct 2007
£149,000
Nov 1997
£46,250
Mar 1996
£39,500
|
£117,500 | |
5 Fortview Terrace, Bridge Street GL5 1DZ
|
Feb 2018
|
£172,500 | |
6 Fortview Terrace, Bridge Street GL5 3ES
|
Nov 2000
|
£59,400 | |
6b Fortview Terrace, Bridge Street GL5 2HA
|
Jan 2017
|
£159,999 | |
7 Fortview Terrace, Bridge Street GL5 3ES
|
Oct 1999
Oct 1999
£45,000
|
£45,000 | |
8 Fortview Terrace, Bridge Street GL5 3ES
|
Jan 2018
Jul 2014
£125,000
Aug 2005
£122,000
|
£178,000 | |
9 Fortview Terrace, Bridge Street GL5 3ES
|
Apr 2002
|
£72,950 | |
10 Fortview Terrace, Bridge Street GL5 3ES
|
Aug 2021
Jan 2002
£70,000
|
£162,500 | |
11 Fortview Terrace, Bridge Street GL5 3ES
|
Jun 2007
Jun 2007
£140,000
Oct 1996
£35,000
|
£140,000 | |
12 Fortview Terrace, Bridge Street GL5 3ES
|
Aug 2021
Oct 2019
£100,000
Aug 2019
£95,000
|
£220,000 |
Data on sold house prices, such as the results above for Fortview Terrace Bridge Street Cainscross Stroud GL5, 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.