BINBURY 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

BINBURY MANOR

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

← Back to Manorial Registry

Historical names: Bembury (Manor) | Bemgebury (Manor) | Bimbury (Manor) | Binberry (Manor)

Location: Thurnham, Kent

Places / associated places: Thurnham, Kent

Records & References

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

5 records found · showing 1–5.

1685-1685: rental, with other manors (with later annotations) (mutilated)

Date / period: 1685-1685 Type: Rental Reference: U312/M23/2

Held by: Kent History and Library Centre
Further information: NRA 4130

1675-1675: rental, with other manors (with later annotations) (mutilated)

Date / period: 1675-1675 Type: Rental Reference: U312/M23/1

Held by: Kent History and Library Centre
Further information: NRA 4130

1653-1653: rental of quit rents, with other manors (1 small vol)

Date / period: 1653-1653 Type: Rental Reference: U312/M28/15

Held by: Kent History and Library Centre
Further information: NRA 4130

1648-1648: terrier, with other manors

Date / period: 1648-1648 Type: Terrier Reference: U312/M33

Held by: Kent History and Library Centre
Further information: NRA 4130

1639-1647: rentals of quit rents, with other manors (6 small vols)

Date / period: 1639-1647 Type: Rental Reference: U312/M28/8, 10-14

Held by: Kent History and Library Centre
Further information: NRA 4130

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/binbury-manor-5493

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.