Historical names: Bloccanleah (Manor) | Blocclea (Manor)
Location: Blockley, Worcestershire
Places / associated places: Blockley, Worcestershire
Records & References
Sources and references mentioning this manor/title which are not necessarily conveyances or transfers.
104 records found · showing 65–72.
1647-1649: survey (Parliamentary), with other manors (extracts made c 18th cent) (1 vol)
Held by: Worcestershire Archive and Archaeology Service
Further information: NRA 9293 Worcester Diocese
1647-1649: survey (Parliamentary) (extracts made c 1841)
Held by: Worcestershire Archive and Archaeology Service
Further information: NRA 9293 Worcester Diocese
1647-1647: survey (Parliamentary) (contemporary copy and draft)
Held by: Worcestershire Archive and Archaeology Service
Further information: NRA 9293 Worcester Diocese
1644-1850: leases
Held by: Worcestershire Archive and Archaeology Service
Further information: NRA 9293 Worcester Diocese
1631-1631: bailiff's audit accounts, with other manors (1 vol)
Held by: Worcestershire Archive and Archaeology Service
Further information: NRA 9293 Worcester Diocese
1630-1633: court rolls (extracts in 18th cent lease register)
Held by: Worcestershire Archive and Archaeology Service
Further information: NRA 9293 Worcester Diocese
1630-1691: "manor book" comprising register of copyhold and leasehold grants, with other manors (begun 1661)
Held by: Worcestershire Archive and Archaeology Service
Further information: NRA 9293 Worcester Diocese
1628-1631: court book, with other manors
Held by: Worcestershire Archive and Archaeology Service
Further information: NRA 9293 Worcester Diocese
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/blockley-manor-5750Public 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.