v1.0 industry review edition. Coverage, methodology and entity pages open for correction through March 2027. Release cadence.
Email [email protected].

Peak Forest Quarries

Last updated 25 May 2026

Derbyshire limestone quarry cluster in the Peak District National Park. The Cemex and RMC sidings handle outbound stone and cement-grade limestone to customer terminals across the Midlands and the south-east. Carried roughly evenly by DB Cargo and GB Railfreight.

Peak Forest Quarries website

Operating company Cemex UK; legacy RMC sidings; Tarmac terminating points
Commodity Limestone aggregates and cement-grade stone
Active since Rail connection from 1880s; current quarry configuration post-1960s
Rail connectivity Peak Forest branch off the Hope Valley line; private sidings within the quarry
TIPLOC footprint
PEAKRGB (Peak Forest Cemex GBRf)
PEAKCEM (Peak Forest FHH (Cemex) terminal)
PEAKRMC (Peak Forest R M C sidings)
PEAKDC (Peak Forest D&C reception)
PEAKUSG (Peak Forest Up Sidings)
PEAKFHH (Peak Forest FHH fuel point)
Carrier mix
DB Cargo (48%)
GB Railfreight (44%)
DC Rail (8%)
Trailing 12-period A2F Inaugural data window — per-period reliability figures from P1 2026-27 onwards.

Latest period summary

Peak Forest Quarries handled 82 monitored inbound services and 75 monitored outbound services in Period 2 2026-27. Inbound arrivals read 82% within 15 minutes of schedule against a national freight benchmark of 90%; outbound services read 85% within 15 minutes. The -5 percentage-point move on Period 1 2026-27 inbound and the +9 percentage-point move outbound sit within plausible sampling variation at these denominators; the ranges around each reading overlap. PRELIMINARY at T+2; FINAL re-publication at T+35 after Network Rail's batch correction.

Full breakdown — P2 2026-27 period report

Methodology & sources

All figures derive from Network Rail's NROD TRUST feed, processed via the Gauge Intelligence ingest pipeline. Period definitions, A2F (Arrival to Fifteen), the Wilson 90% interval, daily anomaly rules, cross-view reconciliation, and delay attribution are documented at:

Data window — period boundaries and the data-as-of cutoff
League tables — cross-view reconciliation across the four analytical views
Anomaly detection — daily A2F SPC rules
Delay attribution — DAPR cause-code breakdown
Forecasting — prediction intervals and possession-exposure estimates

Peak Forest is a cluster of Derbyshire limestone quarries inside the Peak District National Park, immediately south of the Hope Valley line. The principal operators on site are Cemex and (historically) RMC, with shipped product covering both aggregates and cement-grade limestone.

Activity window

Across the 90 days to 25 May 2026 the published archive observed 314 inbound and 306 outbound journeys at the Peak Forest cluster (queried gauge_intelligence_v2 at 2026-05-25, 90-day window). DB Cargo carried around 48% of journeys; GB Railfreight around 44%; smaller carriers (including DC Rail) the balance. Per-period reliability data for this site, once a closed-period window is available, will be published in the next quarterly archive edition. Corrections and additions welcomed via [email protected].

Methodology

Carrier and footprint figures are computed from Network Rail TRUST data, attributed by destination and origin TIPLOC. See the league-table methodology for the attribution rules, the data-window methodology for the period boundaries, and the supply-chain entity methodology for the entity classification and bundling rules.

Inaugural data window

This register entry covers identity and rail-freight footprint only. Per-period reliability figures — arrival-to-five-minute pass rate, cancellation rate, intraday pattern — publish from the first full closed rail period that completes under the current attribution model. Until that period closes, footprint counts are the only figures on this page.

Partial carrier attribution

Footprint counts on this page reflect the freight operators whose TRUST activations resolve to this site's TIPLOCs. Movements handled outside the named carriers — internal shunts, non-NROD-reporting operators, or flows attributed to network nodes rather than the site itself — are not captured here. Where the rail-served footprint is shared between several occupiers, the named carrier may not be the contracting party.