BRAMFORD 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

BRAMFORD MANOR

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

← Back to Manorial Registry

Location: Bramford, Suffolk

Places / associated places: Bramford, Suffolk

Records & References

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

30 records found · showing 9–16.

1749-1875: steward's papers, chiefly minutes, surrenders and admissions

Date / period: 1749-1875 Type: Minutes Reference: HB8/1/694

Held by: Suffolk Archives - Ipswich

1747-1747: rental, with other manors

Date / period: 1747-1747 Type: Rental Reference: HB8/1/939

Held by: Suffolk Archives - Ipswich

1742-1742: rental

Date / period: 1742-1742 Type: Rental Reference: HB8/1/688

Held by: Suffolk Archives - Ipswich

1725-1725: rental

Date / period: 1725-1725 Type: Rental Reference: HB8/1/687

Held by: Suffolk Archives - Ipswich

1703-1703: rental

Date / period: 1703-1703 Type: Rental Reference: HB8/1/686

Held by: Suffolk Archives - Ipswich

1700-1723: court rolls (2)

Date / period: 1700-1723 Type: Court Roll Reference: HB8/1/674-675

Held by: Suffolk Archives - Ipswich

1685-1693: court roll

Date / period: 1685-1693 Type: Court Roll Reference: HB8/1/673

Held by: Suffolk Archives - Ipswich

1680-1775: court book, with Baylham (indexed)

Date / period: 1680-1775 Type: Court Book Reference: HB8/1/677

Held by: Suffolk Archives - Ipswich

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/bramford-manor-6211

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.