BROMHAM 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

BROMHAM MANOR

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

← Back to Manorial Registry

Claim

Historical names: Bromham Battle (Manor)

Location: Bromham, Wiltshire

Places / associated places: Bromham, Wiltshire

Records & References

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

22 records found · showing 17–22.

1362-1364: court roll

Date / period: 1362-1364 Type: Court Roll Reference: SC 2/208/16

Held by: The National Archives
Further information: See SC2/208/16;SC2

External source

1352-1354: court roll

Date / period: 1352-1354 Type: Court Roll Reference: SC 2/208/16

Held by: The National Archives
Further information: See SC2/208/16;SC2

External source

1287-1306: court rolls, with other manors

Date / period: 1287-1306 Type: Court Roll Reference: SC 2/208/15

Held by: The National Archives

External source

1272-1307: custumal and rental

Date / period: 1272-1307 Type: Rental Reference: E 315/57, ff. 42-43

Held by: The National Archives

External source

1272-1307: rental and custumal

Date / period: 1272-1307 Type: Rental Reference: E 315/57, ff. 42-43

Held by: The National Archives

External source

1216-1272: rental

Date / period: 1216-1272 Type: Rental Reference: E 315/18, fo. 25

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/bromham-manor-6576

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.