BRAGENHAM 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

BRAGENHAM MANOR

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

← Back to Manorial Registry

Claim

Location: Soulbury, Buckinghamshire

Places / associated places: Soulbury, Buckinghamshire

Records & References

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

6 records found · showing 1–6.

1688-1688: court roll

Date / period: 1688-1688 Type: Court Roll Reference: D/BASM 68/1

Held by: Buckinghamshire Archives
Further information: NRA 44585

External source

1664-1664: court roll

Date / period: 1664-1664 Type: Court Roll Reference: D/BASM 68/1

Held by: Buckinghamshire Archives
Further information: NRA 44585

External source

1603-1606: court roll

Date / period: 1603-1606 Type: Court Roll Reference: D/BASM 68/1

Held by: Buckinghamshire Archives
Further information: NRA 44585

External source

1583-1583: court roll

Date / period: 1583-1583 Type: Court Roll Reference: D/BASM 68/1

Held by: Buckinghamshire Archives
Further information: NRA 44585

External source

1560-1560: survey, with Wavendon

Date / period: 1560-1560 Type: Survey Reference: D/BASM 77/2

Held by: Buckinghamshire Archives
Further information: NRA 44585

External source

1547-1553: survey, with other manors

Date / period: 1547-1553 Type: Survey Reference: LR2/188 (f 307)

Held by: The National Archives

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/bragenham-manor-6188

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.