Winter Downs 200 (2024): my 200-mile race and the logistics behind it

In December 2024 I finished the Winter Downs 200 in 69:14:32, 18th overall, wearing bib 167. The event ran from 11 to 14 December. That is nearly three days of elapsed race time: long enough that a running challenge becomes a problem of organising movement, support and decisions across successive nights.

This is my verified race record and an explanation of the planning around it. The finish and checkpoint times below come from the official public tracker. The support discussion draws on my crew-supported planning, with private details left out. It is not a reconstructed diary of what I felt at each checkpoint.

The race ledger: what is actually recorded

The official event result identifies me by name and bib, marks the result as Finish and records an elapsed time of 69 hours, 14 minutes and 32 seconds. The 18th place belongs to this event result. Centurion’s historical statistics combine performances across years; a position in that list is not the same thing as my placing in the 2024 race.

Official result and checkpoint chronology — Winter Downs 200 2024. Search for Deepak Shukla or bib 167. Centurion Running’s Winter Downs 200 statistics provide a separate historical comparison.

A race measured in days, not just miles

The useful difference between a 100-mile race and this event is not simply another hundred miles. My South Downs Way 100 result earlier that year was 22:43:38. Winter Downs took 69:14:32: a little over three times as long, rather than twice as long. That arithmetic does not tell us why. Different routes, the season, terrain and time spent stopped all limit a direct comparison.

It does show the change in the planning horizon. A plan built around getting through one long day is not automatically a plan for several days. Equipment needs to remain usable, food needs to remain accessible and support needs to accommodate a runner whose arrival time can shift. The question becomes what still works when the initial timetable no longer does.

Selected checkpoints: the chronology, without invented splits

The public tracker gives clock readings as well as elapsed timing. I have selected a few entries to make the duration readable. These are recorded checkpoint timestamps, not proof of when I ate, rested, changed kit or spoke to my crew. The table keeps the tracker’s date and clock convention; it does not convert it into another time zone.

Crew support: make the handover simple

My preparation included crew support, checkpoint changes, timing, fuelling and filming. That is the safe, useful outline of the plan. A crew-supported event is still the runner’s race, but the work around it involves other people being ready at the right place, with the right supplies, as the expected arrival changes.

As a planning principle, separate essentials from nice-to-haves. A handover should make it easy to identify what the runner needs next: usable lighting, food and drink, appropriate layers and whatever the event rules require. Filming is a separate task, not a reason to delay a necessary handover. This describes how to think about logistics; it is not a claim that a particular intervention saved my race.

Checkpoint access and permitted crew locations must come from the organiser’s instructions for the edition you enter. A map point visible on a public tracker does not mean it is a legal place for outside assistance. Do not reproduce somebody else’s crew itinerary as though it were an approved support plan for your own race.

Overnight running and changing conditions

The selected entries show movement through overnight periods across the event. That is enough to explain why lighting, navigation and access to supplies belong in preparation. It does not tell us whether I slept, how much sleep I had or how alert I felt. I will not turn a timestamp into a memory.

Terrain also changes the usefulness of an average pace. Hills and variable surfaces mean the same effort does not produce the same speed everywhere. For a future attempt, plan around sections of the actual course and the current rules, not a flat-road pace multiplied by two hundred. Weather, ground conditions and required kit need checking close to the race; conditions in one edition are not a forecast for the next.

What a future runner can take from this result

First, look at elapsed time rather than only distance. Build a support plan that can move with the runner’s actual progress. Second, distinguish a checkpoint timestamp from time spent there: the result is not a nutrition or sleep log. Third, decide in advance who is monitoring updates and who is handling supplies, so a changed arrival does not become a confused handover.

None of this is an individual training prescription. A multi-day ultra needs preparation suited to the athlete and the event, with qualified guidance where appropriate. My finish is evidence that I completed this race, not evidence that copying my schedule will produce the same outcome.

Where this fits in my running story

I did not begin with a 200-mile event. Read my original Chicago marathon account, the story of my first ultramarathon and my Madeira diary for the earlier experiences. The title of the Madeira diary is historical; it should not be used as the verified finish time for a different race.

For the other half of my 2024 comparison, read South Downs Way 100: my 22:43:38 finish. The endurance collection brings the reports and training stories together, while my adventures connects running with Army preparation, Muay Thai and travel.