BATTLESDEN 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

BATTLESDEN MANOR

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

← Back to Manorial Registry

Location: Battlesden, Bedfordshire

Places / associated places: Battlesden, Bedfordshire

Records & References

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

5 records found · showing 1–5.

1724-1724: rental(vol)

Date / period: 1724-1724 Type: Rental Reference: T46/2

Held by: Bedfordshire Archives
Further information: NRA 33213 Page-Turner

1559-1559: court book, (draft) with other manors (Honour of Gloucester)

Date / period: 1559-1559 Type: Court Book Reference: TW701

Held by: Bedfordshire Archives
Further information: NRA 7633 Trevor Wingfield

1547-1550: court roll, with other manors (Honour fo Gloucester)

Date / period: 1547-1550 Type: Court Roll Reference: SC 2/155/13

Held by: The National Archives
Further information: See SC2/155/13;SC2

1446-1447: court roll (Honour of Gloucester), with other manors

Date / period: 1446-1447 Type: Court Roll Reference: D641/1/4N/1

Held by: Staffordshire and Stoke-on-Trent Archive Service: Staffordshire County Record Office
Further information: See D 641;D 641/1/4N/1

1332-1334: ministers accounts, with other manors (Honour of Gloucester)

Date / period: 1332-1334 Type: Accounts Reference: SC 6/1119/3

Held by: The National Archives
Further information: See SC6/1119/3;SC6

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/battlesden-manor-4981

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.