BODMIN MANOR AND BOROUGH
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

BODMIN MANOR AND BOROUGH

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

← Back to Manorial Registry

Location: Bodmin, Cornwall

Places / associated places: Bodmin, Cornwall

Records & References

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

71 records found · showing 25–32.

1789-1789: valuation

Date / period: 1789-1789 Type: Valuation Reference: C 108/273/3/8

Held by: The National Archives

1789-1789: surveys (2)

Date / period: 1789-1789 Type: Survey Reference: C 108/273/3/8

Held by: The National Archives

1789-1789: particular

Date / period: 1789-1789 Type: Particular Reference: C 108/273/3/13

Held by: The National Archives

1789-1789: valuation

Date / period: 1789-1789 Type: Valuation Reference: C 108/273/3/7

Held by: The National Archives

1789-1789: surveys (2)

Date / period: 1789-1789 Type: Survey Reference: C 108/273/3/7

Held by: The National Archives

1789-1789: survey

Date / period: 1789-1789 Type: Survey Reference: C 108/273/4/17

Held by: The National Archives

1786-1786: rental

Date / period: 1786-1786 Type: Rental Reference: C 108/272/7/4

Held by: The National Archives

1781-1781: rental

Date / period: 1781-1781 Type: Rental Reference: WH/1/5495

Held by: Kresen Kernow (formerly Cornwall Record Office)
Further information: NRA 2687

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/bodmin-manor-and-borough-5831

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.