© Copyright Middlewich Heritage Trust 2025. Registered Charity No 1161871. Company Limited by Guarantee No 9441581
Made with 🤍 by Bloom Digital Marketing Ltd.
The excavation at Buckley’s Field uncovered a range of archaeological deposits, primarily of Romano-British date, which have been subdivided into sixteen ‘Phases’. Each phase describes a broad chronological period of particualr activitis on the site; these can be summarised as follows:
Phase | Description |
1 | Natural |
2 | Pre-Roman buried soil |
3 | Pre- Roman features |
4 | Mid-late 1st century buried land surface and cut features |
5 | Late 1st century cultivation deposits and surfaces (Trench 1) |
6 | Late 1st – early 2nd century road construction (Trench 1) |
7 | Early-mid-2nd century structures and pits |
8 | Mid-late 2nd century reorganisation of building plot |
9 | Midden deposit (Trench 12) |
10 | Late 2nd – 3rd century cut features (Trench 1) |
11 | Early 3rd century burnt layer (Trench 1) |
12 | Cleaning layers (All Trenches) |
13 | Subsoil |
14 | 1960’s John Bestwick Trench (Buckley’s Field) |
15 | Topsoil |
16 | Redeposited clay and topsoil (Trench 9) |
For a detailed definition of archaeological phases follow this link: http://en.wikipedia.org/wiki/Archaeological_phase
Click on the individual sectiond below to read deatilaed descriptions of each phase.
NOTE: In each phase, the deposits are referred to by their deposit (or ‘context’) numbers. Each number relates to a single event, such as the filling of a pit or the laying of a surface (a positive feature), or the action of digging a pit or ditch (known as a negative feature, or ‘cut’). Positive features are represented in the text by numbers in rounded brackets (e.g. (101), (1258) etc), negative features are shown in square brackets (e.g. [1259], [1221] etc).
The numbers are taken from a register on site in sequence so that every event has a unique number to identify it. The numbers are therefore simply an identifier- they do not have any special significance. As an example, we can imagine how a rubbish pit might be formed; a pit is first excavated to make a hole; this is context [1]. Kitchen waste is then thrown into the base of the pit containing food waste, bits of broken pottery and so on; this is context (2). More rubbish could be thrown into the pit over time, maybe from different sources such as bedding straw from a stable, ash or charcoal from a fire, and these would each be given a new number. By recording each deposit with a unique number, we can separate the artefacts out and record precisely where they came from which allows us not only to date the deposits, but to comment on such factors such as diet, land use, industry, animal husbandry etc.
On the Community Dig site, all context numbers begin with the trench number, so the deposits in Trench 1 start at 100, Trench 2 starts at 200, and so on. Deposits in Trench 12 start from 1200.
In some instances, single deposits have been given more than one number, primarily where the same deposit has been excavated more than once in different locations. These deposits are shown with an ‘=’ sign and can be considered as a single entity.
Phase 2: Pre-Roman Buried Soil
Phase 3: Possible Pre-Roman Deposits
Phase 4: Mid-late 1st century buried land surface and cut features
The Trust is established for the preservation and promotion of the heritage of Middlewich (including buildings, artefacts and archives) as a resource for the benefit of the residents of Cheshire East, of Cheshire West and Chester, and of the wider public. Middlewich Heritage Trust is a not for profit organisation and welcomes volunteers from all walks of life in a number of different areas.
There are many ways to get involved with Middlewich Heritage and volunteers are a crucial part of what we do. For more information on how to become a volunteer please contact us.
Mike Walton
Chair, Middlewich Heritage Trust
Cookie | Duration | Description |
---|---|---|
yt-player-headers-readable | never | The yt-player-headers-readable cookie is used by YouTube to store user preferences related to video playback and interface, enhancing the user's viewing experience. |
yt-remote-cast-available | session | The yt-remote-cast-available cookie is used to store the user's preferences regarding whether casting is available on their YouTube video player. |
yt-remote-cast-installed | session | The yt-remote-cast-installed cookie is used to store the user's video player preferences using embedded YouTube video. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. |
yt-remote-device-id | never | YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. |
yt-remote-fast-check-period | session | The yt-remote-fast-check-period cookie is used by YouTube to store the user's video player preferences for embedded YouTube videos. |
yt-remote-session-app | session | The yt-remote-session-app cookie is used by YouTube to store user preferences and information about the interface of the embedded YouTube video player. |
yt-remote-session-name | session | The yt-remote-session-name cookie is used by YouTube to store the user's video player preferences using embedded YouTube video. |
ytidb::LAST_RESULT_ENTRY_KEY | never | The cookie ytidb::LAST_RESULT_ENTRY_KEY is used by YouTube to store the last search result entry that was clicked by the user. This information is used to improve the user experience by providing more relevant search results in the future. |
Cookie | Duration | Description |
---|---|---|
_ga | 1 year 1 month 4 days | Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors. |
_ga_* | 1 year 1 month 4 days | Google Analytics sets this cookie to store and count page views. |
Cookie | Duration | Description |
---|---|---|
PREF | 8 months | PREF cookie is set by Youtube to store user preferences like language, format of search results and other customizations for YouTube Videos embedded in different sites. |
VISITOR_INFO1_LIVE | 6 months | YouTube sets this cookie to measure bandwidth, determining whether the user gets the new or old player interface. |
VISITOR_PRIVACY_METADATA | 6 months | YouTube sets this cookie to store the user's cookie consent state for the current domain. |
YSC | session | Youtube sets this cookie to track the views of embedded videos on Youtube pages. |
yt.innertube::nextId | never | YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. |
yt.innertube::requests | never | YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. |
Cookie | Duration | Description |
---|---|---|
_pk_id.43236.731c | 1 year 1 month | Description is currently not available. |
_pk_ses.43236.731c | 1 hour | Description is currently not available. |