The Spine races · 2027

Plan your race. Follow a runner.

Free pacing plans and live arrival forecasts for the Full Spine, Challenger North and Challenger South, built from the GPS tracks of past finishers.

Unofficial and independently developed: not affiliated with or endorsed by the Spine Race, its organisers or Open Tracking. Built from publicly available Open Tracking results and GPS tracks, with thanks. Official times, cut-offs and rules come from the race team.

Following someone?

1Pick their race and enter the checkpoint times you see on the tracker (or paste them from Open Tracking).
2See when they're likely at the next checkpoint, with a time window, and a cautious finish estimate.
3Bold times are confirmed; ~ italic times are predictions. One slow section isn't proof of fatigue.

All-time results

Every recorded finisher of all three races, with official times, notes on route changes, and runners who have done more than one race.

How it works

How the plans and forecasts are worked out, how they were tested on past races, and what they can't know.

Challenger North pacing planner

Unofficial and independently developed: not affiliated with or endorsed by the Spine Race or its organisers. Predictions are estimates from past races, not race timing.

h min
Used until their first checkpoint time is in, and to compare against.
Time now
Set a time to replay a past race or check "what if".
When I change a stop
Units
Fuel
g carbs/h
kcal/h
Your plan

When I change a stop

Keep my finish time (recommended for planning). Your target stays fixed. If you spend longer at a checkpoint, the plan asks you to move faster on the legs to make it back, and vice versa. The Leg time change column shows how much faster (green, minus) or slower (plus) each leg needs to be compared with a plan using typical stops.

Keep my fitness. Your moving speed stays at what the target needs with typical stops. Change a stop and everything after it moves later or earlier, so the finish moves too. The Arrival change column shows how much earlier (green, minus) or later you reach each point. Use it to ask "what if I only stopped 20 minutes at Alston?"

Typical stops are what finishers near your target actually took at each point, including any sleep, so put your full planned time at a checkpoint (eating, kit, sleep) in Your stop.

Conditions

Your target is for typical conditions. Choosing poor or very poor keeps the same fitness and slows every leg, so you can see your finish, cut-off margins, food needs and hours in the dark in a bad year. Save it as your bad-weather plan to compare.

Race timeline

Zoom in, then drag or swipe to scroll. Hover or tap for time, distance and height.
Moving Stop Dark (sun more than 6° below the horizon) Cut-off: where they reach the checkpoint, a line to the deadline (red tick) and the time to spare Arrive-by goal Predicted Now Course profile (elevation)

Live times

Type in arrival times from the tracker as they come in; departure times are optional but make predictions a little sharper. Bold times are confirmed (entered by you); ~ italic times are predictions. Ranges are shown for the next timing point and the finish only.

How the live predictions work
    Keep several runners and switch between them. Saved on this device.
    Update for family and friends
    Add a confirmed time
    Checkpoint story
      Finish estimate after each confirmed time
      All timing points

      Stops and sleep

      These stops are a starting point, not advice. Each one is filled in with the typical stop that past runners with a similar finish time made at that checkpoint. They're there so you can see straight away where you might stop and how long for.

      Just because other runners stopped somewhere doesn't mean you need to. Change them to suit your own race: sleep somewhere else, skip a stop, or take longer where you know you'll need it. Everything else on the page (arrival times, daylight, cut-offs) updates as you go.

      Save and compare plans

      Try different versions of your race: the same finish time with sleep in different places, an A and a B goal, a bad-weather plan. Save each one, then compare up to three side by side to see what it means for each leg, your time in the dark and your cut-off margins.

      Saved plans stay in this browser on this device. Save to a file to keep a copy, or to move a plan to your phone.

      Arrive-by goals

      Leg by leg

      Columns

      Checkpoint jobs

      Pace card

      Sized for a phone screen. Print it (or save it as a PDF) and laminate it for your map case; to keep the plan itself on your phone, use "Save this plan to a file" above. Drop-bag checkpoints are in bold, with what to carry to the next bag and your jobs; the monitoring points and huts are shown for timing.

      Checkpoints

      From the 2027 race pack. Check the final race information, as details can change.

      About this tool

        How the plan is worked out

          All-time results

          Every finisher, every year

          Official finish times for the Full Spine, Challenger North and Challenger South, from publicly available Open Tracking results, with thanks. Unofficial and independently developed: not affiliated with or endorsed by the Spine Race, its organisers or Open Tracking.

          Routes, diversions and holds

          Times are official finish times as published, including any time added or credited. The route and conditions have changed over the years, so a faster time is not always a better run. Years marked ⚑ in the table had a notable difference.

            Source: publicly available Open Tracking results, 2014–2026 (all finishers, whether or not a GPS track survives), with thanks. The Full Spine began in 2012, but full results for 2012–2013 aren't on Open Tracking, so they aren't included. There was no race in 2021. Official results are held by the race organisers.
            How it works

            How to use this site

            A free, unofficial planner and dot-watch helper for the Spine races. It turns the GPS tracks of past runners into a pacing plan you can shape around your own race, and into arrival estimates for the people following you.

            Planning your race, step by step

            1. Pick your race at the top: Full Spine, Challenger North or Challenger South.
            2. Set your target finish time and the conditions you expect. Not sure? Start with a time from the All-time results for runners like you.
            3. Look at the stops. Every checkpoint starts with the typical stop past runners made there (see below). Change them to suit your race.
            4. Add arrive-by goals if you want to be somewhere by a set time, such as over Cross Fell before dark. The plan shifts your pace to meet them.
            5. Read the race timeline: where you'll be by day and night, your margin on each cut-off, and the climbs ahead.
            6. Check the leg-by-leg table for arrival and leave times, pace, daylight and what to carry to the next drop bag.
            7. Note your jobs for each checkpoint (food, kit change, sleep), so they print on your pace card.
            8. Save it, and try another version. Compare up to three plans side by side.
            9. Keep it with you: save the plan to a file on your phone, print the pace card, and share a code with the people following you.

            About the stops

            The stops are filled in for you as a starting point, not as advice. Each one is the typical stop that past runners with a similar finish time made at that checkpoint, including sleep. They're there so you can see straight away where you might stop and roughly how long for.

            Just because other runners stopped somewhere doesn't mean you need to. Sleep somewhere else, skip a stop, or take longer where you know you'll need it. Each stop shows whether it's still the typical value or one you've set yourself, and everything else on the page updates as you change them.

            Stops can't go over the race's maximum stay at each checkpoint, and the planner warns you if a plan would miss a cut-off.

            Comparing plans

            Save a plan under a name, change it, and save again. Tick up to three to compare them. For example, compare the same finish time with your sleep at Hawes, Alston or Bellingham.

            • A timeline for each plan on one clock, with night shaded and the long stops labelled.
            • Finish, moving time, stopped time, hours moving in the dark, nights out and your tightest cut-off.
            • Every drop-bag checkpoint: when you arrive, how long you stop, when you leave.
            • Each leg between drop bags: how long it takes and how much of it is in the dark.

            The best value in each row is in bold. Plans are kept in your browser; use Save this plan to a file to keep a copy on your phone, and Open a plan file to bring it back on any device.

            Following a runner, step by step

            1. Choose Follow a runner and pick their race.
            2. If they shared a plan code with you, paste it in. Estimates then use their target and planned stops.
            3. Enter the checkpoint times you see on the live tracker, or paste the tracker's checkpoint list and let the page read the times.
            4. Read the next arrival: the most likely time at their next checkpoint and a window around it.
            5. Look at the finish estimate, a wider and more cautious range that narrows as the race goes on.

            Departure times are optional. If you add them, the next-arrival estimate gets sharper.

            Reading the numbers

            • Bold times are confirmed checkpoint times you entered. ~ Italic times are estimates.
            • Windows show the range real runners' times fell in when the method was tested on past races. Most arrivals land inside the window; some won't.
            • Cut-off margins are coloured: green is comfortable, amber is under four hours, red is under an hour or missed.
            • Estimated position on the timeline is exactly that: an estimate between confirmed times, not a GPS fix.
            • All clock times are UK time (GMT).

            Where the numbers come from

            • Past runners' tracks. The GPS tracks of past finishers are measured against the 2027 course, leg by leg, so the plan knows how long each section really takes runners of different speeds.
            • Your target sets the pace. The planner blends the leg profiles of runners near your target, then finds the one pace that lands you on your finish time with the stops you've chosen.
            • Darkness is slower. Each leg's daylight is worked out for its place and predicted time, and moving in the dark is a little slower, as it was for past runners.
            • Course changes, diversions and holds in past years are left out of the data where they would mislead.
            • Live estimates blend the plan with how the runner's race is actually going and with past runners who were at the same point at a similar time.

            How accurate is it?

            Every method was tested on past races it hadn't seen: fitted without a year, then checked against what that year's runners really did. Leg times usually landed within about 7–10% of reality. Live finish estimates got steadily closer as more checkpoints came in. The figures for each race are in the detail at the bottom of this page.

            Weather and how each person runs their race cause most of the difference. Treat every time as a central estimate with a range around it.

            What it can't know

            • This year's weather, holds, diversions or course changes made on the day.
            • Injuries, navigation errors, kit problems, or how long someone decides to sleep.
            • Anything about a runner beyond the times you enter.

            It's a planning aid, not a navigation or safety tool. Official times, cut-offs and rules always come from the race team.

            Your data

            • Everything stays on your device. Plans, saved runners and times you enter are kept in this browser only. Nothing is sent anywhere.
            • Plan files and share codes contain only what you choose to save or share.
            • Clearing your browser data removes saved plans, so save the ones you care about to a file.

            Using it with no signal

            Once you've opened the site, your phone keeps a copy, so it still opens with no signal. That's handy in Edale or on the Pennine Way.

            To get an app-style icon: on iPhone, tap Share then Add to Home Screen; on Android, open the browser menu and tap Add to Home screen or Install app.

            Data, thanks and independence

            Thank you to Open Tracking. The results and GPS tracks this site is built on come from Open Tracking, who run the live tracking and results for the Spine races. Everything used here was publicly accessible on their website. None of this would be possible without the work they put into tracking every runner, every year. Thanks too to every runner whose track helps the next ones plan.

            Not affiliated or endorsed. This site is unofficial and independently developed. It is not affiliated with, endorsed by or connected to Open Tracking, the Spine Race, its organisers or its sponsors. They haven't checked or approved anything here, so please don't contact them about it.

            Official information comes from them. Official results belong to Open Tracking and the race; official times, cut-offs, kit and rules come from the race team. If anything here disagrees with the official information, the official information is right.

            The detail, race by race

            How each model was built and tested, for anyone who wants the full method.