What I learned from running the same race three times in a row
I have started the same 100-kilometre trail race three times: once to see whether I could finish, once to chase a cleaner time, and once to test what remained after years of chasing numbers. The start line stayed in the same place, but each version asked a different question. Comparing the three race reports is less a catalogue of suffering than a study in how small decisions compound over a long day.
My race sits in the Blue Mountains west of Sydney, where the course climbs from the lower valleys onto exposed sandstone and through eucalyptus forest. Summer can bring warm nights, humid mornings and sudden thunderstorms, while winter adds mud, cold rain and slippery rocks. The event operates more like a community gathering than a mass city marathon: local clubs supply volunteers, aid stations depend on folding tables and radios, entry places are capped, and cut-off times are firm.
The first run was dominated by unknowns. I knew the distance, but not how the climbs would affect my running, how quickly my hands would deteriorate, or whether I could make sensible choices after twelve hours without sleep. By the third start, I recognised the checkpoints, knew which volunteers would be manning the later aid stations and could anticipate the exposed section after the ridge.
That familiarity was useful, but it also created a trap. I began treating the course like a training session with a finish line, underestimating the emotional cost of returning to the same terrain. The deeper lesson was not that knowing a course makes it easier. It is that familiarity makes your habits easier to repeat, including the habits that cost you the race.
Familiarity changes the race
On my first attempt, every kilometre required fresh interpretation. The map provided distances, but the course kept supplying surprises: a technical descent that forced me to walk, a false-flat climb that tightened my hamstrings, and an aid station positioned just far enough to unsettle my timing. I finished, though not with the control I had expected.
By the third attempt, I could identify trouble before it became serious. I knew where the wind would catch runners on the exposed plateau and which descent would turn my poles into a liability. I also knew that this knowledge could make me careless. Familiarity shortened my thinking, but sometimes it also narrowed it, so I deliberately added questions to my checkpoint routine instead of relying on automatic reactions.
The best runners were not always the fastest on the climb. They were the ones who recognised when the course had changed and adjusted without drama. My repeated starts taught me to respect changing conditions, even on a route I believed I knew.
Pacing belongs to the terrain
My first race followed a simple plan: stay ahead early, bank time at the checkpoints and survive the back half. It looked disciplined on paper. In practice, an optimistic opening pace meant I reached the ridge before my fuel, sleep and patience could support it.
The better approach was to negotiate with the terrain. I ran the steep sections conservatively, used flatter ground to increase effort gradually, and treated cut-off times as limits rather than targets. A negative split sounds attractive, but it is not a universal rule. On a wet course with sharp rocks and a punishing climb late in the race, holding back too far can leave me racing against the clock when I should be racing against the conditions.
Australian race crews often talk about being “clocked”, while aid-station volunteers shorten forty kilometres to “forty k”. I borrowed that practical shorthand for pacing: I was not there to prove a split, only to arrive. That distinction made it easier to slow down before fatigue turned a controlled effort into damage.
Fuelling needs room for judgement
I treated the first race like a nutrition experiment. Each gel had a planned time, each drink mix had a measured concentration, and every solid food had been tested during training. The system failed because real hunger, heat and fatigue do not follow a spreadsheet. What looked like an inability to eat was often my body rejecting food because I was running too hard or drinking too much.
By the third attempt, my fuelling plan had checkpoints but not rigid rules. I could take in extra carbohydrate earlier when the next section looked long, sip rather than gulp when the temperature rose, and accept that swallowing might become difficult after prolonged effort. The useful plan identified what must happen, but left enough flexibility for changing conditions.
The aid stations also shaped this flexibility. Australian trail races often depend heavily on volunteers who replenish bottles, manage rubbish and keep runners moving through a narrow window. Knowing who would handle that work created a sense of shared responsibility. I was not simply consuming fuel; I was moving through a temporary community built to get runners safely to the next checkpoint.
Tired decisions need earlier rules
Around seventy kilometres, my thinking becomes less trustworthy. A minor twinge can seem like an injury, an unfamiliar noise can trigger doubt, and the attractive option is often to stop before anyone notices. That pattern matches what I wrote about decision-making under fatigue: once the body is depleted, every choice feels urgent and none feels fully informed.
The useful response was to make important decisions while rested. Before each race, I defined what would count as pain I could run through, what signs meant I should shorten the effort, and what evidence justified continuing. These were not rules for overriding common sense. They were anchors for the moment when common sense became clouded by exhaustion.
I also stopped treating a delayed finish as a failure of character. Sometimes the correct decision was to withdraw, preserve my running health and return for another attempt. Familiarity with the course made that choice harder because I could picture the finish, but it also gave me a baseline for judging whether the body was deteriorating or merely uncomfortable.
Repetition can build durable judgment
Those three starts changed my training more than any single race. I stopped adding volume simply because the calendar allowed it and began building around the demands I actually faced: sustained climbing, technical descents, overnight recovery and repeated fuelling. I also learned to review one decision at a time instead of blaming an entire race on fitness. Where I started too fast, what had triggered it? What information had I ignored?
The same pattern appears in long professional projects. Experience becomes useful when it turns into better judgement, not when it merely produces more hours. A familiar deadline, difficult stakeholder or recurring technical problem should create a clearer response than it did last time. The reward is not confidence alone; it is the ability to act without repeating every old mistake.
My practical takeaway is simple: before the next start, write down the one variable you will control by feel, the one you will control by the clock, and the checkpoint where you will reassess, then protect that plan with the same patience you bring to the final kilometre.