Location: Topcliffe, Yorkshire
Places / associated places: Topcliffe, Yorkshire
Location & Extent
GPS Location & Recorded Land Areas
Representative GPS point: 54.1727, -1.391
Identity: confirmed — The TNA/MDR record F240233 is explicitly catalogued as Asenby Manor in the Topcliffe, Yorkshire area. Independent local and historical sources identify Asenby as the township and manor associated with Topcliffe, North Riding, distinguishing it from other places named Asenby.
Representative point: 54.1727, -1.3910
Basis: settlement_proxy — Asenby Hall, at OS grid reference SE 39849 75378, is a documented historic hall and an important farm located in the centre of Asenby. It is used as a defensible representative point for the manor/township because no source located a separately documented medieval or early-modern manor-house site for Asenby Manor.
Point confidence: medium
Boundary status: representative_point_only
Boundary period: Nineteenth-century township/manorial context
Boundary confidence: none
Boundary basis: Sources establish that Asenby was a township and manor associated with Topcliffe and occupied approximately 1,130-1,135.5 acres in the nineteenth century. However, the evidence located does not provide a sufficiently clear, source-mappable perimeter for the historical manorial land itself. The township, modern parish, and manor cannot safely be treated as identical, so no polygon is returned.
Sources:
- The National Archives Discovery: Asenby Manor, MDR record F240233: https://discovery.nationalarchives.gov.uk/details/c/F240233 — Registry authority/reference GB/NNAF/M169312 and record F240233 identify the exact manor record supplied by the user.
- Historic England: Asenby Hall, Front Garden Wall and Gate Piers, NHLE 1150084: https://historicengland.org.uk/listing/the-list/list-entry/1150084 — Documents Asenby Hall at National Grid Reference SE 39849 75378, equivalent to approximately 54.1727, -1.3910. The listing confirms the historic building and its location in Asenby.
- Asenby Tithe Maps Project: https://northyorkstithes.com/project/asenby/ — Identifies Asenby as a township in Topcliffe parish, gives the 1838 tithe-map date, and records an area of 1,131 acres, mostly the property of the lord of the manor.
- GENUKI: Topcliffe, Yorkshire, 1868: https://www.genuki.org.uk/big/eng/YKS/NRY/Topcliffe/Topcliffe68 — Describes Asenby, or Azenby, as a township in Topcliffe parish and records the contemporary lord of the manor.
- GENUKI/Bulmer's Topcliffe Parish information, 1890: https://www.blunham.com/big/eng/YKS/NRY/Topcliffe/Topcliffe90.html — Reports Asenby township as containing approximately 1,135.5 acres and identifies the lord of the manor and principal landowners.
- Asenby Parish Council: About Asenby: https://www.asenby.org/about-asenby — States that Asenby was part of the manor of Topcliffe at the Norman Conquest and places the historic settlement on the south bank of the River Swale.
Warnings / uncertainty:
- The returned point is a representative settlement-centre proxy near Asenby Hall, not a proven medieval manor-house coordinate.
- The historical area figures describe the Asenby township/manorial context, but do not by themselves establish an exact manor boundary.
- No documented historical polygon for the manorial extent was located; do not inject a boundary polygon based on the modern civil parish or township boundary.
About the Manor
A manor associated with Asenby, a settlement in the parish of Topcliffe in the North Riding of Yorkshire.
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/asenby-manorPublic 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.