BILTON
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

BILTON

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

← Back to Manorial Registry

Location: Lesbury, Northumberland

Places / associated places: Lesbury, Northumberland

Records & References

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

18 records found · showing 9–16.

1674-1674: court roll, with Lesbury

Date / period: 1674-1674 Type: Court Roll Reference: AC:D/III/2/1

Held by: Alnwick Castle

1670-1670: call list (Alnwick Barony)

Date / period: 1670-1670 Type: Archive Record Reference: AC:D/ll/1

Held by: Alnwick Castle

1667-1730: calls of court (Alnwick Barony) (9)

Date / period: 1667-1730 Type: Archive Record Reference: AC:C/ll/1-9

Held by: Alnwick Castle

1663-1668: court rolls (Alnwick Barony) (5)

Date / period: 1663-1668 Type: Court Roll Reference: AC:D/ll/2a

Held by: Alnwick Castle

1652-1659: court files (Alnwick Barony) (13)

Date / period: 1652-1659 Type: Archive Record Reference: AC:C/l/1/a/1-13

Held by: Alnwick Castle

1618-1618: court minutes (Alnwick Barony) (1 file)

Date / period: 1618-1618 Type: Minutes Reference: AC:C/l/4

Held by: Alnwick Castle

1570-1570: survey, with other manors

Date / period: 1570-1570 Type: Survey Reference: E164/38

Held by: The National Archives

1520-1520: knights court rolls (Alnwick Barony) (2)

Date / period: 1520-1520 Type: Court Roll Reference: AC:D/ll/5d

Held by: Alnwick Castle

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/bilton-5491

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.