House prices in Ravensbourne Drive, Chelmsford CM1 2SL
1 - 20 of 20
| Address | Last sale | Price paid | |
|---|---|---|---|
|
50 Ravensbourne Drive CM1 2SL
|
Nov 2019
Jun 2017
£369,500
Feb 1999
£70,000
|
£380,000 | |
|
54 Ravensbourne Drive CM1 2SL
|
Jan 2002
|
£159,500 | |
|
55 Ravensbourne Drive CM1 2SL
|
Apr 2021
Jul 2000
£126,000
|
£410,000 | |
|
58 Ravensbourne Drive CM1 2SL
|
Feb 2015
Jun 2010
£205,000
|
£277,000 | |
|
59 Ravensbourne Drive CM1 2SL
|
Nov 2020
Oct 2000
£152,000
|
£415,000 | |
|
62 Ravensbourne Drive CM1 2SL
|
Jul 2022
|
£420,000 | |
|
63 Ravensbourne Drive CM1 2SL
|
Nov 2011
|
£247,500 | |
|
66 Ravensbourne Drive CM1 2SL
|
Jul 2017
|
£405,000 | |
|
68 Ravensbourne Drive CM1 2SL
|
Oct 2020
Mar 2014
£325,000
|
£415,000 | |
|
69 Ravensbourne Drive CM1 2SL
|
Oct 2022
Dec 2019
£388,500
Dec 2007
£220,000
Jul 1998
£50,000
|
£475,000 | |
|
70 Ravensbourne Drive CM1 2SL
|
Jun 2020
Sep 2016
£325,000
|
£385,000 | |
|
71 Ravensbourne Drive CM1 2SL
|
Dec 2011
|
£235,000 | |
|
72 Ravensbourne Drive CM1 2SL
|
Oct 1998
Feb 1997
£78,500
|
£98,000 | |
|
73 Ravensbourne Drive CM1 2SL
|
Jan 2010
|
£190,000 | |
|
75 Ravensbourne Drive CM1 2SL
|
May 2012
Dec 1996
£73,000
|
£249,995 | |
|
76 Ravensbourne Drive CM1 2SL
|
Mar 2021
|
£398,000 | |
|
77 Ravensbourne Drive CM1 2SL
|
Feb 2014
Feb 2014
£250,000
Jan 2005
£215,000
Jun 2004
£185,000
Jul 2000
£109,500
|
£250,000 | |
|
79 Ravensbourne Drive CM1 2SL
|
Jul 1997
|
£82,000 | |
|
80 Ravensbourne Drive CM1 2SL
|
Oct 2011
Nov 1996
£70,000
|
£237,500 | |
|
82 Ravensbourne Drive CM1 2SL
|
Feb 1996
|
£65,000 | |
Data on sold house prices, such as the results above for Ravensbourne Drive Chelmsford CM1 2SL, 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.