BITTERNE 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

BITTERNE MANOR

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

← Back to Manorial Registry

Claim

Location: South Stoneham, Hampshire

Places / associated places: South Stoneham, Hampshire

Records & References

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

94 records found · showing 89–94.

1370: court roll

Date / period: 1370 Type: Court Roll Reference: 11M59/C1/9/1

Held by: Hampshire Archives
Further information: NRA 42952 CC Winchester

External source

1357-1361: accounts (2)

Date / period: 1357-1361 Type: Accounts Reference: 11M59/Bp/Bit/1-2 (E2/159468/box 62-63)

Held by: Hampshire Archives

External source

1323-1325: bailiff's accounts

Date / period: 1323-1325 Type: Accounts Reference: SC 6/1141/12

Held by: The National Archives

External source

1272- 1307: bailiff's accounts, with other manors

Date / period: 1272- 1307 Type: Accounts Reference: SC 6/1142/15

Held by: The National Archives

External source

1244-1636: Winchester pipe roll accounts (301 rolls/vols), with other manors

Date / period: 1244-1636 Type: Accounts Reference: 11M59/B1/18-318

Held by: Hampshire Archives

External source

1208-1237: Winchester pipe roll accounts (17 rolls), with other manors

Date / period: 1208-1237 Type: Accounts Reference: 11M59/B1/1-17

Held by: Hampshire 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/bitterne-manor-5625

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.