BINHAM 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

BINHAM MANOR

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

← Back to Manorial Registry

Claim

Location: Binham, Norfolk

Places / associated places: Binham, Norfolk

Records & References

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

14 records found · showing 9–14.

1643-1652: court roll

Date / period: 1643-1652 Type: Court Roll Reference: MS 21010

Held by: Norfolk Record Office

External source

1624-1637: court rolls (2)

Date / period: 1624-1637 Type: Court Roll Reference: MC 847/1-2

Held by: Norfolk Record Office

External source

1576: survey, with rental and memorandum of customs (1 vol)

Date / period: 1576 Type: Rental Reference: DDSQ(3)/19

Held by: Hull History Centre (Hull University Archives)
Further information: NRA 23700

External source

1570-1570: extent (1 roll)

Date / period: 1570-1570 Type: Extent Reference: AYL 63

Held by: Norfolk Record Office
Further information: NRA 27820

External source

1486-1492: court rolls

Date / period: 1486-1492 Type: Court Roll Reference: MS ch. Norfolk 850

Held by: Oxford University: Bodleian Library, Special Collections

External source

1423-1441: court rolls

Date / period: 1423-1441 Type: Court Roll Reference: MS ch. Norfolk 849

Held by: Oxford University: Bodleian Library, Special Collections

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/binham-manor-5504

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.