BEDWYN PREBEND 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

BEDWYN PREBEND MANOR

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

← Back to Manorial Registry

Claim

Location: Great Bedwyn, Wiltshire

Places / associated places: Great Bedwyn, Wiltshire

Records & References

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

13 records found · showing 9–13.

1761-1798: survey and valuations, with other papers

Date / period: 1761-1798 Type: Survey Reference: 9/4/89

Held by: Wiltshire and Swindon History Centre
Further information: NRA 30725 Brudenell-Bruce

External source

1759-1786: court roll

Date / period: 1759-1786 Type: Court Roll Reference: 9/4/86

Held by: Wiltshire and Swindon History Centre
Further information: NRA 30725 Brudenell-Bruce

External source

1738-1741: court roll

Date / period: 1738-1741 Type: Court Roll Reference: 9/4/85

Held by: Wiltshire and Swindon History Centre
Further information: NRA 30725 Brudenell-Bruce

External source

1734-1770: survey, with other manors

Date / period: 1734-1770 Type: Survey Reference: 9/1/102

Held by: Wiltshire and Swindon History Centre
Further information: NRA 30725 Brudenell-Bruce

External source

1572-1579: court rolls (5)

Date / period: 1572-1579 Type: Court Roll Reference: 9/4/84

Held by: Wiltshire and Swindon History Centre
Further information: NRA 30725 Brudenell-Bruce

External source

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/bedwyn-prebend-manor-5136

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.