BEDLINGTON
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

BEDLINGTON

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

← Back to Manorial Registry

Claim

Location: Bedlington, Northumberland

Places / associated places: Bedlington, Northumberland

Records & References

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

39 records found · showing 33–39.

1582-1858: surrenders and admissions (26)

Date / period: 1582-1858 Type: Surrender / Admission Reference: ZBS 37 Box 5

Held by: Northumberland Archives

External source

1519-1720: court books (97)

Date / period: 1519-1720 Type: Court Book Reference: DHC1/I/1-97

Held by: Durham University Library and Collections

External source

1438-1619: court books (14)

Date / period: 1438-1619 Type: Court Book Reference: DURH 3/15-28

Held by: The National Archives

External source

1413-1414: rental

Date / period: 1413-1414 Type: Rental Reference: DHC1/M.65

Held by: Durham University Library and Collections

External source

1388-1425: court books (2)

Date / period: 1388-1425 Type: Court Book Reference: DURH 3/13

Held by: The National Archives

External source

1381-1382: court book

Date / period: 1381-1382 Type: Court Book Reference: DURH 3/135

Held by: The National Archives

External source

1348-1362: court book

Date / period: 1348-1362 Type: Court Book Reference: DURH 3/12

Held by: The National Archives

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/bedlington-5122

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.