Historical names: Battersea and Wandsworth (Manor)
Location: Battersea, Surrey
Places / associated places: Battersea, Surrey
About the Manor
Battersea Manor was the manor associated with Battersea and Wandsworth in Surrey. The supplied source context does not provide a reliable historical description beyond the manor's identity and alternative name.
Ownership / Holder Account
No secure ownership history could be established from the supplied source context. The fetched National Archives record was unavailable because it returned an anti-bot verification page, and the other supplied sources are unrelated commercial or general pages.
Records & References
Sources and references mentioning this manor/title which are not necessarily conveyances or transfers.
44 records found · showing 1–8.
1859-1864: Wandsworth Common wages books
Held by: Northamptonshire Archives Service
Further information: NRA 10410 Spencer
1800- 1900: custumal, with other manors
Held by: Surrey History Centre
Further information: NRA 3518 Surrey RO misc
1763-1766: account, with other manors
Held by: Surrey History Centre
1741-1874: court books (9)
Held by: Northamptonshire Archives Service
Further information: NRA 10410 Spencer
1640: map
Held by: Surrey History Centre
Further information: NRA 3518 Surrey RO misc
1628: court roll
Held by: Collection held privately: enquiries to West Sussex Record Office
Further information: NRA 15719 Wyndham (Petworth)
1621-1622: rental, with Allfarthing
Held by: The National Archives
1619: rental, with other manors
Held by: Cambridge University Library: Department of Manuscripts and University 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/battersea-manor-4970Public 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.