Trail nutrition guide

Understand your nutrition profile

Trailboard does not lock you into a permanent category. A profile selects a coherent starting point, then training trials and race feedback refine the next strategy.

Reference profile

Trailboard’s average profile

Medium

This is not the biological average of every trail runner. It is a neutral simulation used to explain the engine: an 8-hour trail at moderate intensity, in mild weather, with average gut tolerance and 60 g/h already tested.

Carbohydrates
60 g/h
480 g over 8 hours · reference range 50–70 g/h
Hydration
500 ml/h
4 L over 8 hours · reference range 400–600 ml/h
Sodium
300–600 mg/h
Starting range to reconcile with drinks and selected products
Caffeine
Optional
Always totalled in mg and mg/kg, then tested before race day

Simulation assumptions

  • 70 kg athlete — body mass is mainly used to interpret caffeine.
  • Expected duration: 8 hours, moderate intensity, trail terrain.
  • Average gut tolerance and a confirmed capacity of 60 g/h.
  • Mild weather and average sweating, without an individual sweat test.
  • Electrolyte drink, varied foods and no guaranteed aid-station intake.

Scientific reading of the average profile

  • Beyond 2.5 hours, guidance extends up to 90 g/h according to need, tolerance and practicality. A 60 g/h target therefore sits at the lower end of a long-event strategy.

  • The ultra-specific position stand suggests 30–50 g/h and 450–750 ml/h for racing. A real ultra may therefore require a lower approach than general endurance guidance.

  • No absolute fluid volume suits everyone. Weather, body-mass change and sweat rate should progressively replace the average setting.

  • The gastrointestinal system is adaptable. A value tested in training is more informative than a self-declared category alone.

Compare

Four profiles, four starting points

Duration remains fixed at 8 hours so that only the profile changes. These figures are coherent Trailboard engine outputs, not performance goals.

Limited data

Cautious start

50 g/h

For a first long-distance build or gut tolerance that is still uncertain.

  • Low tolerance
  • Unconfirmed capacity
  • Mild weather
  • Average sweating
Carbohydrates
50 g/h
range 30–50
Hydration
500 ml/h
range 400–600
Sodium
300–600 mg/h

Regular intake and gut training come first. A higher target is possible only after it has been tolerated during long training sessions.

Trailboard reference

Average profile

60 g/h

The central setting for a runner who has already validated 60 g/h without precise physiological measurements.

  • Average tolerance
  • 60 g/h tested
  • Mild weather
  • Average sweating
Carbohydrates
60 g/h
range 50–70
Hydration
500 ml/h
range 400–600
Sodium
300–600 mg/h

This is a stable starting point, not a universal target. Selected products and aid stations then determine the actual quantities to carry.

Confirmed data

Gut trained

75 g/h

For an athlete who has repeatedly tolerated 75 g/h during comparable efforts.

  • Good tolerance
  • 75 g/h tested
  • Mild weather
  • Average sweating
Carbohydrates
75 g/h
range 60–85
Hydration
500 ml/h
range 400–600
Sodium
300–600 mg/h

Required capacity should not exceed trained capacity. Above 75 g/h, carbohydrate variety and repeated practice become central.

Demanding context

Heat and heavy sweating

60 g/h

Shows how weather and sweat narrow digestive margin and increase fluid logistics.

  • Average tolerance
  • 60 g/h tested
  • Hot weather
  • Self-reported heavy sweating
Carbohydrates
60 g/h
range 50–60
Hydration
750 ml/h
range 600–900
Sodium
500–900 mg/h

Confidence is lower without a sweat test. Carrying volume and water-point spacing must be checked before increasing intake.

Understand the controls

What actually changes the plan

Each setting answers a different question. No single control summarises athletic ability.

FactorWhen low or unknownWhen high or confirmed
Intensity

When low or unknownMore room to eat, with needs still driven by duration.

When high or confirmedLess digestive margin; simpler and more frequent intakes.

Gut tolerance

When low or unknownConservative start and progressive gut training.

When high or confirmedThe upper range is possible once it has been repeated.

Carbohydrate experience

When low or unknownTrailboard limits ambition and lowers confidence.

When high or confirmedThe tested value bounds the target without automatically exceeding it.

Heat

When low or unknownStandard fluid range, still adjusted to thirst.

When high or confirmedFluid and sodium rise while carbohydrate margin narrows.

Sweat / salt

When low or unknownA cautious assumption when measurement is missing.

When high or confirmedFluid and sodium rise but still require individual confirmation.

Drink and variety

When low or unknownCarbohydrates mainly come from carried foods.

When high or confirmedA carbohydrate drink counts only when a real product is selected.

Confidence level

A value and how certain it is

Low

Weather, sweat or experience data is missing. Trailboard uses a broad, non-blocking range.

Medium

Duration and main settings are known, but no physiological measure confirms the strategy.

High

Intake has been tested during comparable efforts and sweat or product data is known.

Isotonic drinks: avoid double counting

Choosing “isotonic” describes a strategy. Carbohydrates become actual intake only when a drink with known composition is selected. Trailboard therefore separates assumed composition from what is actually planned in the bag.

Before medical validation

These references are informational. Kidney, cardiac or metabolic conditions, previous hyponatraemia, repeated gastrointestinal problems, pregnancy or medication interacting with caffeine or hydration require advice from a physician or sports dietitian.

References

Where do the ranges come from?

Trailboard uses recognised consensus statements for its boundaries, then applies cautious trail-specific adaptations. Field experience never replaces scientific references when setting a number.

The plan remains editable: feedback from training and races should progressively replace assumptions.

Back to guides