BLEDLOW MANOR
Deprecated: preg_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /home/u626884147/domains/manorialregistry.com/public_html/wp-includes/kses.php on line 2025
Search Menu

BLEDLOW MANOR

Sponsored by William James Dalrymple West, Esq,. Lord of Watlington-West, Norfolk

← Back to Manorial Registry

Location: Bledlow, Buckinghamshire

Places / associated places: Bledlow, Buckinghamshire

Records & References

Sources and references mentioning this manor/title which are not necessarily conveyances or transfers.

69 records found · showing 17–24.

1797-1861: court rolls (2 vols)

Date / period: 1797-1861 Type: Court Roll Reference: COLL/EST/BLE.3-4

Held by: Eton College

1797-1797: terrier (copied 1808)

Date / period: 1797-1797 Type: Terrier Reference: COLL/EST/BLE.71

Held by: Eton College

1789-1789: terrier

Date / period: 1789-1789 Type: Terrier Reference: COLL/EST/BLE.70

Held by: Eton College

1781-1781: list of fines and heriots

Date / period: 1781-1781 Type: Archive Record Reference: COLL/EST/BLE.74

Held by: Eton College

1775-1775: estimate of annual value of demesne (in bundle with other items)

Date / period: 1775-1775 Type: Archive Record Reference: COLL/EST/BLE.60/5

Held by: Eton College

1775-1775: terrier

Date / period: 1775-1775 Type: Terrier Reference: 152

Held by: Eton College

1768-1768: minutes of special court

Date / period: 1768-1768 Type: Minutes Reference: COLL/EST/BLE.62

Held by: Eton College

1768-1768: terrier (attached to lease of demesne)

Date / period: 1768-1768 Type: Terrier Reference: 98

Held by: Eton College

Corrections / Challenges

Sign in to challenge or submit evidence against a recorded assertion.

JSON API

Machine-readable published manor data, including public images, mapped land areas, notes, rights, conveyances, relationships, records, source/document-library entries and public file links.

https://manorialregistry.com/index.php?rest_route=/mhr/v1/manor/bledlow-manor-5727

Public API access is currently disabled. Authorised API clients must use a private X-MHR-API-Key; currently only administrator keys are enabled.

Private source files, pending edits, moderation/admin information, user API keys and non-public import identifiers are not returned.