Greenwich, Connecticut · Street record
Langhorne Lane
8 parcels and 14 recorded sales since 2007, from public transaction, assessor and parcel records.
Recorded sales14
Latest saleNov 2025
5-year median$3.38M7 sales
Parcels8
Most recent first
Recorded sales on Langhorne Lane
| Property | Recorded date | Sale price | |
|---|---|---|---|
| 11 Langhorne Lane | Nov 4, 2025 | $17.37M | View record → |
| 35 Langhorne Lane | Oct 1, 2025 | $3.85M | View record → |
| 34 Langhorne Lane | Sep 30, 2024 | $3.25M | View record → |
| 20 Langhorne Lane | Jul 2, 2024 | $5.50M | View record → |
| 35 Langhorne Lane | May 2, 2024 | $3.38M | View record → |
| 34 Langhorne Lane | Jun 8, 2023 | $2.51M | View record → |
| 33 Langhorne Lane | Oct 20, 2022 | $2.31M | View record → |
| 35 Langhorne Lane | May 16, 2014 | $1.49M | View record → |
| 11 Langhorne Lane | Apr 21, 2014 | $13.50M | View record → |
| 38 Langhorne Lane | Feb 7, 2012 | $6.45M | View record → |
| 20 Langhorne Lane | Feb 2, 2012 | $1.10M | View record → |
| 11 Langhorne Lane | Sep 16, 2008 | $13.75M | View record → |
| 28 Langhorne Lane | May 21, 2007 | $2.00M | View record → |
| 38 Langhorne Lane | Jan 31, 2007 | $1.25M | View record → |
Owner-free public parcel profiles
Parcels on Langhorne Lane
- 11 Langhorne Lanesold 2025
- 20 Langhorne Lanesold 2024
- 28 Langhorne Lanesold 2007
- 33 Langhorne Lanesold 2022
- 34 Langhorne Lanesold 2024
- 35 Langhorne Lanesold 2025
- 37 Langhorne Lane3,332 sq ft
- 38 Langhorne Lanesold 2012
About this page
Real records, grouped by street
Sales are observed public-record transactions; parcel facts are the latest owner-free public assessment context. Prices are not adjusted for size, condition or time. No owner names are collected or displayed.
Free weekly briefing · Greenwich edition
Researching Langhorne Lane? Get the Greenwich briefing.
Every Thursday: new recorded sales, planning decisions and market moves across Greenwich, sourced to public records. Free.
Free · Thursday email · unsubscribe anytime. Prefer Substack? Subscribe there instead.