BRADWELL (LOWNDES) 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

BRADWELL (LOWNDES) MANOR

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

← Back to Manorial Registry

Claim

Location: Bradwell, Buckinghamshire

Places / associated places: Bradwell, Buckinghamshire

Records & References

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

6 records found · showing 1–6.

1834-1834: appointment of steward

Date / period: 1834-1834 Type: Archive Record Reference: D 242/2/5/5

Held by: Buckinghamshire Archives

External source

1792-1792: court roll with draft and quit rents

Date / period: 1792-1792 Type: Court Roll Reference: D 242/2/5/3-4

Held by: Buckinghamshire Archives

External source

1777-1777: court roll, with quit rents

Date / period: 1777-1777 Type: Court Roll Reference: D 242/2/5/2

Held by: Buckinghamshire Archives

External source

1741-1741: court roll, with quit rents

Date / period: 1741-1741 Type: Court Roll Reference: D 242/2/5/1

Held by: Buckinghamshire Archives

External source

1474-1475: account roll, with Dodford, Northants

Date / period: 1474-1475 Type: Accounts Reference: ZA9209

Held by: Northamptonshire Archives Service

External source

1449-1459: valor and compotus roll

Date / period: 1449-1459 Type: Archive Record Reference: Add Ch 74168-78

Held by: British Library, Manuscript Collections

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/bradwell-lowndes-manor-6182

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.