Your health comes first. This educational article provides general information. Discuss your individual circumstances, pregnancy, illness or symptoms with your clinician; the article cannot replace an individual assessment.

A marathon results list shows longer splits after kilometre thirty, and someone says: glycogen ran out. Energy supply may play a role, but a split is neither a muscle sample nor a blood test. Behind the word wall, distinguish the lived experience, researchers’ pace-based rule and possible explanations for slowing.

Three meanings hide within the same word

When a runner describes hitting the wall, they often name a powerful experience: running worked until it suddenly became very difficult. Physical fatigue, disappointment, disrupted rhythm and abandoning the previous plan may all be present. We need not dispute the experience’s reality to leave its cause open. Precise analysis begins by avoiding compressing every meaning into one word.

Research, however, needs an outcome identifiable more consistently than a personal account. Processing a million marathon splits does not allow interviewing every runner. A reference section, degree of slowing and minimum distance can define a consistently recognisable pace pattern. The pattern does not thereby become a direct physiological measurement.

The third meaning is explanation: why did the decline occur? Carbohydrate availability is one important possible component, but cannot be read from results alone. Keep three levels in separate sentences: it felt difficult; this pace drop appears; several causes need review. Such precision protects analysis from premature conclusions.

How are splits turned into a research definition?

The 2021 study of a large marathon split-time database used late slowing as a proxy for hitting the wall. Its chosen rule required at least 25% slowing sustained for at least five kilometres. The study separately examined how detected prevalence changed with other thresholds. This shows that frequency recognised in data also depends on definitional decisions.

A 2025 waist-sensor study used another detailed rule: it sought a large decline relative to baseline pace between kilometres 5 and 20, occurring after kilometre 25 and sustained for more than five kilometres. It defined a separate stable group and excluded intermediate cases from the model. The studies examine similar phenomena but do not generate their labels identically.

When articles report different frequencies, examine this methodological section first. One group of runners may not have prepared dramatically better or worse. Different events may have been counted using different resolution and rules. Research definitions serve consistent comparison, not permanently naming every everyday running experience.

A pace 25% slower is not a speed 25% lower

Pace and speed are inversely related. Moving from 5:00 to 6:15 min/km increases time per kilometre from 300 to 375 seconds, or 25%. Speed falls from 12 to 9.6 km/h, a 20% decrease. The same run has been described using different quantities, so the percentages differ.

This matters when one study says pace, another speed, or an app translates both loosely as slowing. Compare a number only with its variable and formula understood. A 25% deterioration in pace is not automatically the same speed decrease. Check baseline too: an early stable section, whole-race average and personal best pace use different denominators.

Duration matters just as much. Slowing for a few hundred metres at an aid station differs from declining across several kilometres. If a study requires persistence, a short fluctuation may not enter the labelled group. This does not make the brief difficulty insignificant; it means the study counted a different event.

A runner checks a phone at a covered entrance on a rainy morning, beside a packed bag and waterproof top for a flexible race-day plan.Enlarge image
AI-generated editorial illustration; not a documentary photograph.

What is glycogen, and what can the results list not show?

Glycogen is a storage form of carbohydrate in the muscles and liver, among other places. The Rapoport study modelling marathon energy supply examined relationships between available carbohydrate stores, intensity and individual physiological characteristics. A central idea is that marathon energy supply cannot be described by distance alone: selected intensity and available reserves matter too.

A split database, by contrast, knows when you crossed a timing point. It does not directly measure muscle glycogen, actual use of consumed carbohydrate or changes in substances in the blood. A performance curve’s link with a physiological cause may be real and important without proving that cause in each run merely because the curve looks similar.

Keep modelling separate from individual review. A model can describe a mechanism from assumptions and data, while understanding your race also requires pre-start and during-race events. Carbohydrate supply being important in marathons does not justify automatically explaining every late slowdown through the same deficit.

Two identical splits, two very different five-kilometre sections

Consider an entirely fictional five-kilometre section taking 31 minutes 15 seconds. Anna ran throughout at about 6:15 min/km without stopping. Béla moved at 5:00 min/km but stood still for a total of 6 minutes 15 seconds. Both took the same time between timing points. The official section average is identical; their running stories differ.

If Anna previously ran steadily at 5:00 min/km, her late average may indicate a sustained change in moving pace. Béla’s moving pace could have remained unchanged, with stopping lengthening elapsed time. This does not explain why Béla stopped or Anna slowed. It shows precisely that section time cannot reliably separate these stories.

The same resolution issue arises when a five-kilometre average combines climbs, descents, turns and congestion. One final number compresses them all. A watch recording may be more detailed but has measurement error and pause handling too. Connect sources without attributing more information to either than it contains.

A restrained marathon throughout differs from a late collapse

A runner may deliberately start slower than usual for a shared finish or uncertain background. Continuing at a similar rhythm can produce a result below a previous best without major late decline. Another runner may start very fast and then slow markedly. Similar finish times can therefore conceal different pacing and interpretation questions.

The research label generally concerns change within a race, not achieving a planned time. “I missed my target” and “There was a large late pace drop” are separate statements. The first requires the plan and its realism; the second the race’s progression. Confusing them can label a steady performance simply at another level as hitting the wall.

In review, map the progression first. When was running stable? Where did it change? Gradually or suddenly? Did it recover later? These questions clarify experience too. Only then can you meaningfully discuss which explanations the available information supports.

Create a timeline instead of competing explanations

After finishing, briefly record important events: start and first stable section; aid stations; unusual stop; course change; first difficulty noticed; subsequent decision. One cause need not be selected immediately. Chronology lets memory and data sit alongside each other later. This simple note often adds nuance to later overconfident explanations.

For fuelling, separately record the plan and what actually happened. What was missed? What felt uncomfortable? Which point did you reach at a different time than expected? This is data gathering, not a retrospective dosing recipe. Pace changes and fuelling events appearing in sequence do not alone prove causation, but may provide a useful next discussion question.

Preserve other possible explanations too. A difficult course section, environment, clothing problem or deliberate tactical choice may relate to the split. You need not consider them equally likely. The aim is naming better- and less-supported explanations separately rather than ending analysis with a familiar label.

An experienced station leader shows a new volunteer the arrangement of a clean, prepared water-distribution station before a running event.Enlarge image
AI-generated editorial illustration; not a documentary photograph.

How should you read an article quantifying wall risk?

First find the definition and data source: self-report, official splits, watch files or laboratory results? Then examine inclusion and exclusion. A split-based rule’s sensitivity to distance resolution differs from a personal questionnaire answer. Different results may all be valuable while carrying different kinds of information.

Next consider the comparison’s meaning. More frequent labelled slowing in one group does not predict individual destiny. Groups may differ in training history, race selection and pacing. Ask which factor was actually measured and which possible explanations remained outside the data. A difference existing does not always establish its cause.

Finally check what the article promises from the finding. Recognising a pace pattern does not produce direct glycogen measurement, and a model does not yield an identical race recipe for everyone. Good explanation connects the phenomenon with possible mechanisms while preserving the difference between evidence types.

Let analysis lead to one observable next step

To understand your marathon better, choose one precise next question. You might track early pacing against later progression, document actual execution of the fuelling plan, or separate stopped time from moving pace. These can become observable tasks. The aim is less guessing in the next analysis.

Preparation trying to correct every explanation simultaneously can become confusing. Changing pace, fuelling, equipment and weekly load together makes attributing a different result harder later. Manage changes within the whole training plan with a clear purpose. A research label is not a standalone training programme.

The wall can remain part of runners’ shared language. For deeper understanding, look behind it: what experience did you name, what pace drop did the data record and what evidence supports the explanation? Separating these questions leaves more usable knowledge from the race than one quickly declared diagnosis.

Sources

Helpful? Pass it on.