House prices in Ocklynge Close, Bexhill-on-Sea TN39 4PF
1 - 21 of 21
| Address | Last sale | Price paid | |
|---|---|---|---|
|
3 Ocklynge Close TN39 4PF
|
Feb 2004
|
£215,000 | |
|
4 Ocklynge Close TN39 4PF
|
Apr 1999
|
£120,000 | |
|
5 Ocklynge Close TN39 4PF
|
Oct 2014
Oct 2014
£262,000
Sep 2011
£206,000
|
£262,000 | |
|
6 Ocklynge Close TN39 4PF
|
Sep 2020
|
£335,000 | |
|
8 Ocklynge Close TN39 4PF
|
Oct 2017
Aug 2012
£275,000
Aug 2009
£284,000
Dec 2007
£242,500
|
£343,000 | |
|
9 Ocklynge Close TN39 4PF
|
Jan 2012
Apr 2011
£190,000
|
£242,500 | |
|
11 Ocklynge Close TN39 4PF
|
Mar 2018
|
£325,000 | |
|
12 Ocklynge Close TN39 4PF
|
Apr 2018
|
£318,000 | |
|
13 Ocklynge Close TN39 4PF
|
Sep 2013
Jul 2001
£151,950
Oct 2000
£119,500
|
£297,000 | |
|
14 Ocklynge Close TN39 4PF
|
Dec 2005
Dec 2005
£220,000
|
£220,000 | |
|
15 Ocklynge Close TN39 4PF
|
Nov 2005
|
£217,000 | |
|
16 Ocklynge Close TN39 4PF
|
Jan 2011
Oct 2001
£142,000
|
£249,000 | |
|
17 Ocklynge Close TN39 4PF
|
Feb 2015
|
£275,500 | |
|
18 Ocklynge Close TN39 4PF
|
Oct 2015
May 2011
£310,000
Dec 2002
£195,000
|
£360,000 | |
|
20 Ocklynge Close TN39 4PF
|
May 2007
|
£243,000 | |
|
21 Ocklynge Close TN39 4PF
|
Mar 2017
|
£308,000 | |
|
21a Ocklynge Close TN39 4PF
|
Aug 2006
Jan 2002
£168,000
|
£324,950 | |
|
22 Ocklynge Close TN39 4PF
|
Oct 2016
Aug 2013
£223,500
|
£334,950 | |
|
23 Ocklynge Close TN39 4PF
|
May 2022
Jul 2018
£325,000
Jan 2016
£262,000
|
£420,000 | |
|
28 Ocklynge Close TN39 4PF
|
Jun 2005
|
£219,950 | |
|
29 Ocklynge Close TN39 4PF
|
Jul 2016
Dec 2010
£227,000
|
£325,000 | |
Data on sold house prices, such as the results above for Ocklynge Close Bexhill-on-Sea TN39 4PF, 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.