BRENDON 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

BRENDON MANOR

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

← Back to Manorial Registry

Location: Brendon, Devon

Places / associated places: Brendon, Devon

Records & References

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

7 records found · showing 1–7.

1898-1899: rental

Date / period: 1898-1899 Type: Rental Reference: 1262M/E/20/155

Held by: Devon Archives and Local Studies Service (South West Heritage Trust)
Further information: NRA 6304 Fortescue

1553-1555: court book, with other manors

Date / period: 1553-1555 Type: Court Book Reference: E 315/86

Held by: The National Archives

1536-1538: ministers' accounts, with other manors

Date / period: 1536-1538 Type: Accounts Reference: SC 6/HENVIII/6212

Held by: The National Archives

1533-1544: court book, with other manors

Date / period: 1533-1544 Type: Court Book Reference: SE XXI

Held by: Longleat House

1525-1527: ministers' accounts, with other manors

Date / period: 1525-1527 Type: Accounts Reference: SC 6/HENVIII/6211

Held by: The National Archives

1523-1526: rental, with other manors

Date / period: 1523-1526 Type: Rental Reference: E 315/385/ff. 112-208

Held by: The National Archives

1422-1430: bailiffs' accounts

Date / period: 1422-1430 Type: Accounts Reference: SC 6/826/21-23

Held by: The National Archives

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/brendon-manor-6357

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.