BARTON 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

BARTON MANOR

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

← Back to Manorial Registry

Claim

Location: Barton, Lancashire

Places / associated places: Barton, Lancashire

Records & References

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

7 records found · showing 1–7.

1830-1832: defaulters of fines

Date / period: 1830-1832 Type: Archive Record Reference: DDTS Box 100

Held by: Lancashire Archives

External source

1826-1827: court books (2)

Date / period: 1826-1827 Type: Court Book Reference: DDTS Box 100

Held by: Lancashire Archives

External source

1820-1820: court book

Date / period: 1820-1820 Type: Court Book Reference: DDTS Box 100

Held by: Lancashire Archives

External source

1817-1825: call books (2)

Date / period: 1817-1825 Type: Archive Record Reference: DDTS Box 100

Held by: Lancashire Archives

External source

1817-1831: verdicts (13)

Date / period: 1817-1831 Type: Archive Record Reference: DDTS Box 100

Held by: Lancashire Archives

External source

1772-1772: rental

Date / period: 1772-1772 Type: Rental Reference: DDHK 5/1/55

Held by: Lancashire Archives
Further information: NRA 43628

External source

1769-1815: court books (48)

Date / period: 1769-1815 Type: Court Book Reference: DDTS Box 100

Held by: Lancashire Archives

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/barton-manor-4868

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.