BOULGE 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

BOULGE MANOR

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

← Back to Manorial Registry

Historical names: Boulge Hall (Manor)

Location: Boulge , Suffolk

Places / associated places: Boulge , Suffolk

Records & References

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

23 records found · showing 17–23.

1576-1587: estreats, with other manors

Date / period: 1576-1587 Type: Archive Record Reference: C 116/247

Held by: The National Archives

1560-1560: extent

Date / period: 1560-1560 Type: Extent Reference: HD207/A3/1

Held by: Suffolk Archives - Ipswich

1494-1494: rental

Date / period: 1494-1494 Type: Rental Reference: D/Y 37/2/156

Held by: Essex Record Office

1494-1497: court roll

Date / period: 1494-1497 Type: Court Roll Reference: GC16/1/2

Held by: Suffolk Archives - Ipswich
Further information: NRA 7822 Suffolk RO misc

1430-1431: bailiff's accounts

Date / period: 1430-1431 Type: Accounts Reference: HD1538/139/3

Held by: Suffolk Archives - Ipswich
Further information: NRA 39544

1372-1373: reeve's accounts

Date / period: 1372-1373 Type: Accounts Reference: HD1538/139/2

Held by: Suffolk Archives - Ipswich
Further information: NRA 39544

1356-1357: reeve's accounts

Date / period: 1356-1357 Type: Accounts Reference: HD1538/139/1

Held by: Suffolk Archives - Ipswich
Further information: NRA 39544

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/boulge-manor-6002

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.