BAYLHAM 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

BAYLHAM MANOR

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

← Back to Manorial Registry

Location: Baylham, Suffolk

Places / associated places: Baylham, Suffolk

Records & References

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

33 records found · showing 25–32.

1485-1489: court roll

Date / period: 1485-1489 Type: Court Roll Reference: HB8/1/254

Held by: Suffolk Archives - Ipswich

1462-1477: court roll

Date / period: 1462-1477 Type: Court Roll Reference: HB8/1/254

Held by: Suffolk Archives - Ipswich

1452-1453: ministers' accounts

Date / period: 1452-1453 Type: Accounts Reference: HB8/1/277

Held by: Suffolk Archives - Ipswich

1433-1435: ministers' accounts (2)

Date / period: 1433-1435 Type: Accounts Reference: HB8/1/275-276

Held by: Suffolk Archives - Ipswich

1421-1421: court roll

Date / period: 1421-1421 Type: Court Roll Reference: HB8/1/254

Held by: Suffolk Archives - Ipswich

1418-1426: ministers' accounts (4)

Date / period: 1418-1426 Type: Accounts Reference: HB8/1/271-274

Held by: Suffolk Archives - Ipswich

1400-1413: court roll

Date / period: 1400-1413 Type: Court Roll Reference: HB8/1/254

Held by: Suffolk Archives - Ipswich

1380-1382: ministers' accounts (2)

Date / period: 1380-1382 Type: Accounts Reference: HB8/1/269-270

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/baylham-manor-5012

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.