Monument record 0536300000 - TAPLOW MILLPOND

Summary

Eleventh to seventeenth century records of fishery at Taplow millpond

Protected Status/Designation

  • None recorded

Map

Find a placename, postcode or grid reference

Map layers

Base layers

Info

Record list

Tools

Type and Period (1)

  • FISHERY (11th Century to 17th Century - 1086 AD to 1699 AD)

Description

Plan Form - Linear.
Domesday records 1000 eels from Taplow fishery (B1).
c.1197 Amerden (incl. Fishery) held separately from Taplow (see Cass 01442:02) disputes between Cookham & Taplow over fishing rights C13-17, include topographic description of 5 fisheries, but position of parish boundary implies Taplow only had Millpond (B2-6).

Sources (6)

  • <1>SBC4271 Bibliographic reference: John Morris (ed). 1978. Domesday Book: Buckinghamshire.
  • <2>SBC20462 Bibliographic reference: William Page (ed). 1925. A History of Buckinghamshire (Victoria County History) Volume III. Volume 3. pp242,244.
  • <3>SBC14060 Bibliographic reference: SCRIMGEOUR G E & FARLEY M E NOV 1987 TAPLOW & ITS SETTING (TYPESCRIPT DRAFT IN FILE CAS 1542).
  • <5>SBC16753 Bibliographic reference: D G Wilson. 1977. THE MAKING OF THE MIDDLE THAMES. pp60.
  • <6>SBC5502 Map: G E SCRIMGEOUR FROM OS 1961 SIX INCH MAP.
  • <7>SBC15055 Bibliographic reference: F S Thaker. 1920. The Thames Highway. 2 Volumes. Vol 2, pp302-6.

Location

Grid reference Centred SU 9041 8242 (230m by 1060m)
Civil Parish TAPLOW, South Bucks, Buckinghamshire

Finds (0)

Related Monuments/Buildings (0)

Related Events/Activities (0)

Record last edited

Jan 16 2025 5:09PM

Comments and Feedback

Do you have any questions or more information about this record? Please feel free to comment below with your name and email address. All comments are submitted to the Heritage Portal maintainers for moderation, and we aim to respond/publish as soon as possible. Comments, questions and answers that may be helpful to other users will be retained and displayed along with the name you supply. The email address you supply will never be displayed or shared.