BRAMBLETYE 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

BRAMBLETYE MANOR

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

← Back to Manorial Registry

Location: East Grinstead, Sussex

Places / associated places: East Grinstead, Sussex

Records & References

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

6 records found · showing 1–6.

1869-1869: rental, with other manors

Date / period: 1869-1869 Type: Rental Reference: Acc 3825/Box 1

Held by: West Sussex Record Office
Further information: NRA 4085

1840-1840: rentals, with other manors (2)

Date / period: 1840-1840 Type: Rental Reference: Acc 3825/Box 1

Held by: West Sussex Record Office
Further information: NRA 4085

1810-1810: rental, with other manors

Date / period: 1810-1810 Type: Rental Reference: Acc 3825/Box 1

Held by: West Sussex Record Office
Further information: NRA 4085

1795-1870: minutes

Date / period: 1795-1870 Type: Minutes Reference: Acc 3825/Box 10

Held by: West Sussex Record Office
Further information: NRA 4085

1708-1803: heriots (in court book), with other manors

Date / period: 1708-1803 Type: Court Book Reference: Add MS 17704

Held by: West Sussex Record Office
Further information: NRA 4085

1651-1870: court book, with other manors

Date / period: 1651-1870 Type: Court Book Reference: Add MS 17704

Held by: West Sussex Record Office
Further information: NRA 4085

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/brambletye-manor-6203

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.