House prices in Highgate, King's Lynn PE30
1 - 23 of 23
Address | Last sale | Price paid | |
---|---|---|---|
9 Highgate PE30 1PS
|
Dec 2014
Jun 2013
£129,995
Oct 2005
£103,000
|
£136,000 | |
10 Highgate PE30 1PS
|
Jun 2001
Jun 2001
£49,950
|
£49,950 | |
17 Highgate PE30 1PS
|
Aug 2007
Nov 2001
£60,000
Oct 2000
£50,000
Sep 1999
£36,000
|
£130,000 | |
20 Highgate PE30 1PS
|
Mar 2019
Mar 2019
£155,000
|
£155,000 | |
21 Highgate PE30 1PS
|
Sep 2014
|
£112,000 | |
23 Highgate PE30 1PS
|
Jan 2022
Oct 2015
£128,000
|
£165,000 | |
24 Highgate PE30 1PS
|
Apr 2017
|
£133,000 | |
25 Highgate PE30 1PS
|
Dec 2006
|
£124,000 | |
27 Highgate PE30 1PS
|
Oct 2010
Jul 1997
£34,500
|
£120,000 | |
28 Highgate PE30 1PS
|
May 2021
Aug 2007
£126,000
Mar 2005
£110,000
|
£170,000 | |
37 Highgate PE30 1PS
|
Dec 2019
Mar 2012
£122,000
|
£140,000 | |
38 Highgate PE30 1PS
|
Jan 2012
|
£93,000 | |
55 Highgate PE30 1PU
|
Jun 2006
|
£120,000 | |
56 Highgate PE30 1PU
|
Jan 2014
Apr 2009
£107,500
|
£120,000 | |
57 Highgate PE30 1PU
|
Aug 2002
Jan 2000
£30,000
|
£55,000 | |
62 Highgate PE30 1PU
|
Apr 2019
|
£83,000 | |
63 Highgate PE30 1PU
|
Sep 2019
Apr 2007
£90,950
|
£103,000 | |
64 Highgate PE30 1PU
|
Jul 2019
Jul 2019
£75,000
|
£75,000 | |
66 Highgate PE30 1PU
|
Jul 2007
Jun 1995
£36,000
|
£129,000 | |
71 Highgate PE30 1PU
|
Sep 2005
Sep 2005
£85,000
Feb 2001
£30,000
|
£85,000 | |
92 Highgate PE30 1PU
|
Aug 2012
Aug 2012
£116,500
|
£116,500 | |
93 Highgate PE30 1PU
|
Dec 2018
Nov 2014
£120,000
Jul 2009
£105,000
|
£150,000 | |
99 Highgate PE30 1PU
|
Jun 2002
Feb 1999
£25,500
|
£42,000 |
Data on sold house prices, such as the results above for Highgate King's Lynn PE30, 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.