Real food on a loop

The camp stove caught on the second match, and the pot went on before the questions did. A folding table at the edge of a cinder track, a ladle, a sleeve of paper cups, and a crew member holding a card of notes: her runner had passed the 100-kilometer mark of a twenty-four-hour, the lap sheet said he was slowing, and she wanted to know what to cook for a man who still had most of the night in front of him. The broth was already turning over. The question was what to have ready when the broth stopped working. Behind her, the floodlights hummed over the same quarter mile they had hummed over all day.

a magazine of one region's food

The question on the card

Posed plainly: what do you cook for someone with eighty miles left? Not which gel, which mix, which fraction of a gram of sodium. Cook. She meant a stove, a real ingredient, something with a smell. The frame pinned to the clubhouse wall this month is that question, held against the folder of public material the sport actually keeps: race pages that publish their aid-station menus, the paperwork of the sanctioning bodies, race reports filed at iRunFar and in the pages of UltraRunning Magazine, and the DUV statistics, which will tell you what was run but never what was eaten. The habit of this notebook is to read the folder before answering at the table. So we read.

Why can a loop cook what a trail cannot?

Geometry comes before cooking. A point-to-point trail race has to move its kitchens with the field: aid stations set hours apart on foot, packed in coolers, reached by vehicle or by volunteers carrying crates up a forest road. Heat is a luxury out there, and hot soup at 3 a.m. is a minor miracle of logistics. A loop inverts the problem. Whether the course is a measured mile in a park, a 400-meter track, or a 2.5-kilometer trail loop, the same table comes back every few minutes. A burner can stay lit all night. A pot can hold its temperature from the first hour to the last. The drop bag is a lawn chair away, not a bin waiting at some far checkpoint. That is the whole case for the menu: the course returns, so the kitchen can stay.

What the published menus put on the table

Read the published aid-station information from enough fixed-time and loop events and one short list repeats itself: broths (chicken, miso, vegetable), potato soup, ramen, rice, salted boiled potatoes, watermelon and orange slices, grilled cheese, pancakes in the small hours, bacon held warm as morale, flat cola, coffee before dawn. Reading a race menu is a bit like reading a magazine of one region's food: it tells you what a place believes tired people eat, and it is more honest than most restaurant reviews. Race reports at iRunFar and coverage in UltraRunning Magazine describe close to the same table on different continents, at the old multiday events and the small local twenty-four-hours alike. The long-time race kitchens of this sport have run on soup and starch for decades, and no one has argued them out of it.

What stays down at hour eighteen?

On this point the reports agree more than the arguments do. Somewhere past the middle of a twenty-four-hour, the palate turns. Sweet becomes difficult, then impossible: the runner who lived on gels through the daylight cannot face the flavor by night. Salt and warmth take over: broth first, then plain potatoes, plain rice, cola with the fizz shaken out and the caffeine kept in. The sports-nutrition advice printed over the years has generally sat somewhere between 150 and 300 calories an hour, and every experienced crew knows a runner who never reached the number and finished anyway, and another who hit it exactly and lost the whole of it at the edge of the track. Hour eighteen is not an arithmetic problem. It is a question of what the stomach will still consider, and the stomach considers warm, salted, and familiar.

The standing argument: the pot against the powder

The sport keeps an old argument running between real food and engineered nutrition, and both sides publish. The powder camp counts: gels, drink mixes, capsules, calories per hour per lap, all of it neat enough that a crew could keep the sums on a clipboard. The pot camp answers that a packet is only good if it goes down and stays down, and that by hour eighteen the gel has been refused a dozen times while the paper cup of broth was taken without being asked for. Consistency against bearability. Measured sodium against a bowl of potato soup that costs nothing to swallow. The record of this sport ratifies results, not menus, so the argument has never been settled by authority. It is re-fought at folding tables, one race at a time.

The part the record does not keep

Here the frame stops, and it stops honestly. The DUV statistics will give you the names, the distances, the splits. The ratification paperwork of the IAU and USATF will confirm what was run, on which course, in what conditions. No document in the public folder records what the runner ate, which cup of broth turned the night around, or whose potatoes came back up at the curb. The lap sheet counts laps. It does not count cups. What was carried in the paper cup stays between the runner and the table, and the crew member's question lives exactly there, in the margin the sport does not archive. That is where the record ends and the cook begins.

Before your next lap

A gesture to close the page. Find a fixed-time race near you and read its published aid-station menu before you enter, the way you would study a course map. Better: stand at a loop's table at dawn, while the night is still on the runners' faces, and quietly count what the hands reach for; the count will teach you more than the argument did. Or open the DUV statistics for a name you know and notice how little of that runner's day lives in the numbers. Then put a pot of broth on your own stove, pour a paper cup, and walk a measured mile with it. If it sits right at the end, you have the first line of an answer to her card.