Practical notes for runners who want to know the ground before they commit to it. Every route here is desk-researched from maps and access records and marked honestly until it has been run and field-checked.
Right now
27 routes across 6 regions
2 of 27 are field-checked from recorded runs; the rest are desk-researched and say so on their pages.
A small edit of routes across coast path, woodland, trail and traffic-free ground. Each one is marked plainly: desk-researched, or field-checked from a recorded run.
Recorded route line
Coast path
A full day on the far west's mining coast: engine houses, boulder fields and thirty kilometres of ground that never settles.
Field checked
Mapped route line
Multi-use path
A flat out-and-back on the old railway line beside the Camel estuary, built for steady miles.
Desk-researched
Mapped route line
Coast path
Cliff-top running past seal colonies and old engine houses, with wind that has an opinion.
Desk-researched
Dates shown with their honest status — provisional until checked against the organiser's page.
Methodology, data pieces and run reports — written to the same standard as the routes.
Run report
The last long run of a Lakeland 50 block, done in a heatwave with full race kit: real splits, saturated air and one 26-minute pub stop.
11 July 2026
Methodology
Where the lines, distances and climb figures come from — and why our gain numbers read lower than the guidebooks.
11 July 2026
Data
One number that predicts how a coastal run will actually feel — with the two places it lies to you.
11 July 2026
How this works
Routes start as desk research: lines and elevation computed from OpenStreetMap paths and open elevation data, with each page saying exactly that. When a route gets run, its line and profile are replaced with the recorded track and the status moves to field checked. Nothing is called verified until the practical details have been confirmed on the ground too.