BIRLING 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

BIRLING MANOR

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

← Back to Manorial Registry

Location: Birling, Kent

Places / associated places: Birling, Kent

Records & References

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

40 records found · showing 33–40.

1586-1586: account of lordship and demesne lands

Date / period: 1586-1586 Type: Accounts Reference: U787/E9

Held by: Kent History and Library Centre

1578-1578: court roll, with other manors

Date / period: 1578-1578 Type: Court Roll Reference: U787/M19

Held by: Kent History and Library Centre

1578-1579: court roll, with other manors

Date / period: 1578-1579 Type: Court Roll Reference: U787/M13

Held by: Kent History and Library Centre

1558-1591: court rolls (5)

Date / period: 1558-1591 Type: Court Roll Reference: U787/M3-7

Held by: Kent History and Library Centre

1542-1544: court roll

Date / period: 1542-1544 Type: Court Roll Reference: U787/M2

Held by: Kent History and Library Centre

1529-1529: survey

Date / period: 1529-1529 Type: Survey Reference: U787/T4

Held by: Kent History and Library Centre

1522-1532: court roll

Date / period: 1522-1532 Type: Court Roll Reference: U787/M1

Held by: Kent History and Library Centre

1521-1522: survey

Date / period: 1521-1522 Type: Survey Reference: SC 12/9/4

Held by: The National Archives

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/birling-manor-5548

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.