House prices in Headland Rise, Walney, Barrow-in-Furness LA14

1 - 31 of 31
Address Last sale Price paid
1 Headland Rise LA14 3YP
May 2018
£289,950
2 Headland Rise LA14 3YP
Feb 2000
£58,500
5 Headland Rise LA14 3YP
Apr 2011
£210,000
6 Headland Rise LA14 3YP
Mar 2019
£147,500
7 Headland Rise LA14 3YP
May 1995
£58,000
8 Headland Rise LA14 3YP
Dec 2007
£112,000
9 Headland Rise LA14 3YP
Oct 2020
£183,000
10 Headland Rise LA14 3YP
Dec 2011
£132,000
11 Headland Rise LA14 3YP
Oct 2010
£145,000
13 Headland Rise LA14 3YP
Aug 2007
£174,000
15 Headland Rise LA14 3YP
Sep 2017
£179,950
16 Headland Rise LA14 3YP
May 2017
£130,000
18 Headland Rise LA14 3YP
Sep 2016
£138,950
19 Headland Rise LA14 3YP
Apr 2018
£165,000
20 Headland Rise LA14 3YP
Jul 2006
£85,000
21 Headland Rise LA14 3YP
Aug 2010
£128,500
22 Headland Rise LA14 3YP
Feb 2015
£117,000
23 Headland Rise LA14 3YP
Nov 2005
£122,500
24 Headland Rise LA14 3YP
Jun 2002
£79,950
25 Headland Rise LA14 3YP
Jun 2010
£122,500
26 Headland Rise LA14 3YP
Nov 2017
£150,000
27 Headland Rise LA14 3YP
May 2018
£176,000
28 Headland Rise LA14 3YP
Dec 2020
£186,000
30 Headland Rise LA14 3YP
Sep 2000
£53,000
34 Headland Rise LA14 3YP
Jun 2020
£166,000
36 Headland Rise LA14 3YP
Jul 2017
£129,950
38 Headland Rise LA14 3YP
May 2002
£67,500
42 Headland Rise LA14 3YP
Jul 2012
£118,000
44 Headland Rise LA14 3YP
Jan 2002
£61,250
46 Headland Rise LA14 3YP
Aug 1997
£52,000
50 Headland Rise LA14 3YP
Aug 2017
£167,500

Data on sold house prices, such as the results above for Headland Rise Walney Barrow-in-Furness LA14, 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.