24-Hour Run: Pacing, Fueling and Night Strategy

A 24-hour run is not decided in the final three hours but in the first six. Start too fast and you pay for it with a night full of walking breaks and a result far below what your fitness was worth. This guide shows how pacing, fueling, foot care and night planning fit together — and what training build actually holds up.

What a timed race demands of the body

In a timed race the clock matters, not the course: 6, 12 or 24 hours, and the distance covered is your result. For most runners that means a mix of running and walking across a full day-night cycle, with an energy turnover of roughly 10,000 to 14,000 kilocalories — more than the body can absorb in that window.

That is the central constraint: you cannot make up in the morning what you lose during the night. A deficit of fluid, sodium or carbohydrate cannot be repaired on the following day. Anyone who treats fueling as a continuous process rather than a meal at every second aid station has a decisive advantage in the second half of the night.

Pacing: the first six hours decide

Start by calculating an honest target pace. 100 kilometres in 24 hours means 14:24 minutes per kilometre including all breaks; 160 kilometres equals 9:00 minutes; 200 kilometres 7:12. That number is your guard rail — not the pace that feels effortless in the first hour.

• Opening pace: In the first six hours never run faster than target pace, and take fixed walking breaks from the start. A ratio of four to five minutes running to one minute walking has proven itself; later the ratio shifts on its own.
• Walking is not failure: Walking breaks early cost a few minutes compared with continuous running but save muscle fatigue that would cost you many times more at night. You are also training for the uphill walking you will do anyway.
• Check every two hours: Record distance, fluid intake, complaints and mood. If your average drops more than five percent below plan, correct it now — not after midnight.
• Ignore day form: Form fluctuates several times across a day. A good patch is not a licence to push the pace.

The blunt truth behind it: beyond roughly 60 to 70 percent of your maximum distance, endurance stops being the limiter — how well you manage fatigue and gut tolerance takes over. Both can be trained, neither can be improvised.

Fueling: calories per hour, not meals

The rule for timed races is 60 to 90 grams of carbohydrate and 200 to 300 kilocalories per hour — spread evenly, not in three big servings. Across 24 hours that means roughly 20 to 30 fueling actions. It sounds like a lot, and that is the point: under sustained load the gut works better with many small amounts than with one large one.

• Hours 0–6 (afternoon): Normal race nutrition — gels, bars, bananas, salted crackers. Plus 400 to 600 millilitres of fluid per hour, part of it with electrolytes.
• Hours 6–12 (evening): The stomach gets more sensitive. Switch to soft, salty food: soup, boiled potatoes, rice cakes, broth. Carbohydrate stays at 60 to 80 grams per hour, mostly from solid food.
• Hours 12–20 (night): The critical window. Warm liquid food often works better than gels here, because cold and fatigue slow gastric emptying. Caffeine is fine but dosed: 100 to 200 milligrams around 1 or 2 a.m., not repeatedly through the night.
• Hours 20–24 (morning): Back to lighter solid food. If you stayed on liquid food all night, you now need something to chew to keep the gut occupied.

Sodium matters more in a timed race than over shorter distances. 300 to 600 milligrams per litre of drink is a sensible range, towards the upper end in heat and with heavy sweating. Too much plain water is the bigger risk here than too little — hyponatraemia is a documented problem in long races, not a theoretical one.

The night: strategy instead of endurance

Between 2 and 5 a.m. core temperature drops, digestion slows and motivation sags. That is physiology, not weakness — and it can be prepared for. Runners who plan the night as its own section with its own tactics come through far better than those who treat it as a continuation of the evening.

• Light: A bright headlamp with a spare battery and a warm secondary light. Darkness amplifies fatigue; good light measurably lifts alertness and mood.
• Company: A companion for two or three night hours is the single most effective measure. Pacers or crew do not need to run — talking is enough.
• Short nap: When fatigue tips over, 10 to 20 minutes of sleep in a car or tent helps. You then need 15 to 20 minutes of walking to get going again. Anything past 30 minutes costs more than it gives.
• Clothing: Night temperatures often drop by 8 to 12 degrees. Spare shoes, dry socks, long sleeves — planned at the crew station, not hunted for spontaneously.
• Fixed rituals: A sip every 60 minutes, a checkpoint every two hours. Rituals replace decisions, and decisions are expensive at night.

Feet, skin and the small disasters

Blisters, chafing and macerated feet are the most common reason runners quit timed races early — more common than cramps or exhaustion. Prevention is unglamorous but decisive: coat feet with a thick barrier salve before the start, change socks every six to eight hours, and pick shoes half a size larger than usual because feet swell over the hours.

Chafing happens where two skin surfaces rub: groin, armpits, nipples in men, plus the bra line in women. Lubricant on all four spots before the start and again after twelve hours. Treat the first sign of raw skin immediately — at night it becomes a problem that forces you to walk within two hours.

One underrated factor: the crew. With support, pack gear into numbered boxes before the start — box 1 for the evening, box 2 for the night, box 3 for the morning. That saves ten minutes per aid-station stop and prevents the classic failure of the rain jacket being in the wrong bag.

The training build: six to nine months

A 24-hour run cannot be prepared in a 16-week block. Six to nine months is realistic, during which three things grow in parallel: weekly volume, the duration of individual sessions, and tolerance of food under fatigue.

• Base (months 1–2): Raise weekly volume from 60 to 80 kilometres, long run from two to three hours. Plus twice-weekly strength for trunk, calves and feet.
• Build (months 3–5): 80 to 110 weekly kilometres with back-to-back long runs at the weekend: Saturday four to five hours, Sunday three to four. This is the single most important stimulus because it simulates running on tired legs.
• Specific (months 6–7): Two sessions of six to eight hours, one of them at night. Test nutrition exactly as in the race, including the warm food around midnight.
• Rehearsal (month 8): One run of eight to ten hours with full race nutrition and crew. Then two easy weeks.
• Taper: Two to three weeks, volume down 50 to 60 percent, intensity kept. Details in the tapering article.

Pace in training is secondary. 80 to 90 percent of all kilometres are easy, at a pace you could comfortably hold a conversation at — aerobic base is the limiting factor in timed races, not top speed. Anyone doing intervals for a 24-hour run is training for the wrong race. Cycling and pool sessions are useful additions to running volume: they add time under load without extra impact stress.

The mental side: handling the low points

A 24-hour run has at least two lows — one in the early evening, one between 2 and 4 a.m. Both are predictable and both pass. Knowing that means you interpret them not as a signal to stop but as a section to get through.

Small concrete targets work better than big arithmetic: not "90 kilometres to go" but "to the next aid station". Add one prepared sentence you say to yourself at night — not motivational but factual: "I walk for 20 minutes now, then I'll see." The ability to break a low into manageable units is more trainable in timed races than any physical quality.

Common mistakes

• Starting too fast. The classic. Ten seconds per kilometre too quick in the first six hours costs one to two hours at night. The first 50 kilometres should feel too easy.
• Untested nutrition. Trying gels, soup and caffeine for the first time in the race ends with nausea for most runners. Every food tested at least three times in training under fatigue.
• Too few walking breaks early. Running the first hours because it feels good is paid for later with calf soreness that turns every rise into a problem.
• Night without a plan. No spare light, no dry socks, no warm jacket in the right bag — then cold decides the race, not fitness.
• Sleep debt before the start. Two short nights before the race are manageable, a week of poor sleep is not. The night before the race is the least important one.
• Chasing an unrealistic target. Setting an unattainable distance goal and being wrecked at kilometre 120 risks injuries that cost months. A realistic target plus reserve is the better strategy.

How Peakora plans timed races

In the Peakora engine, timed races are their own race class: periodisation builds across several months, weekly volume rises in steps of no more than ten percent, and weekend back-to-back long runs are scheduled automatically. The recovery monitor with TSB and ACWR shows whether the build is holding or whether you are ramping too fast — over a six-month preparation that is exactly the decisive question. For fueling, the fuel calculator returns hourly carbohydrate and fluid targets based on duration, temperature and body weight.

More on long-term training control is in the marathon training section and the Peakora glossary.

Frequently asked questions