BOTONNETT 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

BOTONNETT MANOR

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

← Back to Manorial Registry

Claim

Historical names: Botonett (Manor) | Botonnat (Manor)

Location: Lezant, Cornwall

Places / associated places: Lezant, Cornwall

Records & References

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

6 records found · showing 1–6.

1715-1715: account, with other manor

Date / period: 1715-1715 Type: Accounts Reference: U133/C2/11

Held by: Kent History and Library Centre

External source

1715-1715: account

Date / period: 1715-1715 Type: Accounts Reference: U133/C2/1

Held by: Kent History and Library Centre

External source

1710-1710: survey

Date / period: 1710-1710 Type: Survey Reference: X827/5

Held by: Kresen Kernow (formerly Cornwall Record Office)

External source

1700-1800: valuation, with other manor

Date / period: 1700-1800 Type: Valuation Reference: AD32/2

Held by: Kresen Kernow (formerly Cornwall Record Office)

External source

1700-1800: survey, with other manor

Date / period: 1700-1800 Type: Survey Reference: AD32/2

Held by: Kresen Kernow (formerly Cornwall Record Office)

External source

1627-1631: reeve's account, with other manors

Date / period: 1627-1631 Type: Accounts Reference: X827/2-4

Held by: Kresen Kernow (formerly Cornwall Record Office)

External source

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/botonnett-manor-5983

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.