BASSETSBURY 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

BASSETSBURY MANOR

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

← Back to Manorial Registry

Current holder (unregistered): Duchy of Lancaster

Institutional holder

This named holder has no linked registry account. A signed-in user may request to claim this holder identity; an administrator approves or rejects that identity claim.

Current holder (legacy manor assignment): Duchy of Lancaster Unregistered
Institutional holder

Associated title (legacy text): Duchy of Lancaster ownership history (medieval)

Historical names: Bassetbury

Location: High Wycombe, Buckinghamshire

Places / associated places: High Wycombe, Buckinghamshire

About the Manor

Manor house associated with a lord of the manor; historic ownership and estate context as a manorial unit in medieval England.

Ownership / Holder Account

Duchy of Lancaster Current owner evidenced as Duchy of Lancaster in prompt. Medieval ownership history implied by associated title.

Records & References

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

44 records found.

1452-1454: reeves and bailiffs accounts, with other manors

Date / period: 1452-1454 Type: Accounts Reference: DL29/653/10577

Held by: The National Archives

1438-1440: ministers accounts, with other manors

Date / period: 1438-1440 Type: Accounts Reference: DL29/653/10565

Held by: The National Archives

1419-1420: extent, with Amersham and Long Crendon

Date / period: 1419-1420 Type: Extent Reference: DL43/14/4

Held by: The National Archives

1395-1459: court rolls

Date / period: 1395-1459 Type: Court Roll Reference: SGC XV.15.1

Held by: St George's Chapel Archives and Chapter Library

Conveyance & Descent

First holder to present holder: blood proximity & distance travelled

First recorded holder: Duchy of Lancaster

Present holder:

Recorded title journey: 1 holder entry in this manor's saved Conveyance & Descent history.

No recorded holder currently has a usable saved direct-blood or collateral-blood relationship path from which to calculate proximity percentages.

First recorded holder → present holder

A usable saved blood relationship path between the first recorded holder and the present holder has not yet been recorded, so that first-to-present genealogical distance cannot be calculated.

– present

Duchy of Lancaster

Holding arrangement: Other

Bassetsbury Manor record notes that from 1437 it was known as Bassetsbury and was held by the Duchy of Lancaster until 1483, after which it passed to the Dean and Canons of Windsor (B1).

Source: Duchy of Lancaster — source link

Lordship / Title Associations

Associations are recorded by period so changes in estate composition do not imply that every manor remained attached to the same title indefinitely.

Duchy of Lancaster ownership history (medieval)
Associated · Unverified
Record history (latest 2)
  1. Updated unregistered holder crest image id, unregistered holder arms profile.
    30 Aug 2026, 18:26 UTC · William James Dalrymple Bedding Fanshawe West Esq., Lord of Watlington-West, Norfolk
  2. Updated unregistered holder about, unregistered holder wikipedia, unregistered holder website, unregistered holder geni url, unregistered holder facebook, unregistered holder instagram, unregistered holder linkedin and 12 other field(s).
    30 Aug 2026, 18:25 UTC · William James Dalrymple Bedding Fanshawe West Esq., Lord of Watlington-West, Norfolk

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/bassetsbury-manor-4937

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.