BEAUSALE 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

BEAUSALE MANOR

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

← Back to Manorial Registry

Historical names: Bewsall (Manor)

Location: Hatton, Warwickshire

Places / associated places: Hatton, Warwickshire

Records & References

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

6 records found · showing 1–6.

1813-1817: pains and orders, with other manors

Date / period: 1813-1817 Type: Archive Record Reference: CR 3134/63

Held by: Warwickshire County Record Office

1808-1825: court roll, with other manors

Date / period: 1808-1825 Type: Court Roll Reference: MR 22/2-6

Held by: Warwickshire County Record Office

1795-1795: court roll, with other manors

Date / period: 1795-1795 Type: Court Roll Reference: MR 22/1

Held by: Warwickshire County Record Office

1728-1728: survey map, with other manors

Date / period: 1728-1728 Type: Survey Reference: P 43

Held by: Warwickshire County Record Office

1533-1533: court roll, with Whitnash

Date / period: 1533-1533 Type: Court Roll Reference: Mi 6/173/276

Held by: University of Nottingham Manuscripts and Special Collections
Further information: NRA 7428

1530-1530: court roll (muitlated)

Date / period: 1530-1530 Type: Court Roll Reference: Mi 6/173/275

Held by: University of Nottingham Manuscripts and Special Collections
Further information: NRA 7428

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/beausale-manor-5079

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.