House prices in Rayens Cross Road, Long Ashton, Bristol BS41 9DY
1 - 20 of 20
| Address | Last sale | Price paid | |
|---|---|---|---|
|
50 Rayens Cross Road BS41 9DY
|
Aug 2010
|
£312,500 | |
|
52 Rayens Cross Road BS41 9DY
|
Jul 2020
Oct 2007
£340,000
Sep 2004
£305,000
Jun 2002
£175,000
Jan 2001
£130,000
Jun 1995
£92,000
|
£488,950 | |
|
57 Rayens Cross Road BS41 9DY
|
Jul 2002
|
£160,000 | |
|
59 Rayens Cross Road BS41 9DY
|
Jan 2019
|
£425,000 | |
|
61 Rayens Cross Road BS41 9DY
|
Sep 2019
Aug 1996
£92,000
|
£521,000 | |
|
62 Rayens Cross Road BS41 9DY
|
Mar 2015
|
£541,500 | |
|
63 Rayens Cross Road BS41 9DY
|
Aug 2007
|
£312,000 | |
|
65 Rayens Cross Road BS41 9DY
|
Feb 2017
Jun 2006
£289,950
May 2002
£190,000
|
£523,000 | |
|
66 Rayens Cross Road BS41 9DY
|
Aug 1998
|
£117,700 | |
|
67 Rayens Cross Road BS41 9DY
|
Jul 2006
|
£312,000 | |
|
68 Rayens Cross Road BS41 9DY
|
Mar 2010
Jan 2008
£240,000
|
£324,500 | |
|
70 Rayens Cross Road BS41 9DY
|
Aug 2020
|
£445,000 | |
|
71 Rayens Cross Road BS41 9DY
|
Feb 2017
Jul 2011
£292,500
Jun 2001
£184,000
|
£442,500 | |
|
72 Rayens Cross Road BS41 9DY
|
Aug 1999
|
£120,000 | |
|
75 Rayens Cross Road BS41 9DY
|
Dec 1998
|
£106,500 | |
|
80 Rayens Cross Road BS41 9DY
|
Jan 2017
|
£410,000 | |
|
82 Rayens Cross Road BS41 9DY
|
Jul 2014
|
£355,000 | |
|
84 Rayens Cross Road BS41 9DY
|
Jul 2014
Aug 2001
£187,500
|
£370,000 | |
|
86 Rayens Cross Road BS41 9DY
|
Sep 2013
Apr 2007
£352,000
Dec 2004
£200,000
|
£330,000 | |
|
90 Rayens Cross Road BS41 9DY
|
Oct 2018
Sep 2005
£282,500
|
£520,000 | |
Data on sold house prices, such as the results above for Rayens Cross Road Long Ashton Bristol BS41 9DY, 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.