From the founder

The Long Run Your Fuel Log Can't See (Founder's Note)

Most runner-nutrition advice assumes food with a number on the box. Here is how to put a number on the dal-chawal you actually eat before a long run.

By Shaan, founder of NYUS ·

General training-nutrition information, not medical or coaching advice. Check with a qualified coach or dietitian before changing how you fuel, especially if you have a medical condition.

Ask a runner training for a half marathon in Pune or Hyderabad what they ate the night before a long run, and the answer is usually honest and Indian: dal-chawal, khichdi, curd rice, a banana and a glass of milk. Ask how much carbohydrate that plate held, and the conversation usually stops. Not because the runner doesn't care, since most serious runners care a lot about fuelling, but because nothing on that plate came with a number.

This is a narrower version of a problem across Indian fitness, and running exposes it sharply because running punishes poor fuelling quickly. A long run on too little carbohydrate tends to fall apart in the later kilometres, in a way you feel that afternoon. Too little protein across weeks of training can show up as slow recovery. Both trace back to the same root: the food many Indian runners use to fuel and recover is home-cooked, unpackaged and rarely measured.

Why mainstream fuelling advice doesn't transfer cleanly

Much popular runner-nutrition advice (carb-load with pasta, a protein shake after the run, gels during the race) is written for a pantry of labelled, portioned foods. Pasta has a number on the box. A gel has a number on the wrapper. The advice isn't wrong, but it assumes a food environment most Indian runners don't eat from day to day.

Dal is lentils, water, oil and a tadka in proportions that change kitchen to kitchen. A katori of rice depends on the katori. Khichdi's split between dal and rice is close to invisible unless you weigh the raw ingredients. None of it fits the label-reading model, so runners either swap their own food for imported "runner food", or keep eating what works for them and give up tracking it.

Both choices leave something on the table. Swapping home food for gels and pasta is expensive, hard to sustain and often unnecessary: carbohydrate-rich staples like dal-chawal, khichdi and curd rice are meals many runners already rely on. Giving up tracking means you never learn whether your pre-run meal matches what your plan assumes, or whether recovery meals are consistently short on protein.

A simple method to close the gap

The fix isn't switching to Western training food. It is building a reference for the dishes already in your rotation, once, and reusing it.

  1. Weigh your staples once, raw and cooked. Rice, dal and grain dishes change weight a lot between raw and cooked. Weigh your usual portion both ways once and you have a personal conversion you can reuse for the whole training cycle.
  2. Anchor to IFCT, not to a generic app entry. The Indian Food Composition Tables 2017, published by ICMR's National Institute of Nutrition, give values for 528 key foods; except for eggs, they are for raw foods. That suits the method: weigh the raw rice and dal, look them up, and divide by the portions you serve. Where a generic "lentil curry" entry disagrees sharply with your own IFCT-based calculation, trust your calculation.
  3. Log around the long run first. You don't need to count every plate forever. Logging the day before and the meal after your long runs and hard sessions is a practical place to start, because that is when fuelling choices are most noticeable.
  4. Look at the block, not the run. One run's fuelling tells you little. A few weeks of logs tell you whether there is a pattern, such as consistently light pre-run meals or protein that never reaches your target (our guide on daily protein needs helps set one).

Pair this with sensible recovery and rest days; fuelling and recovery work together.

Where NYUS fits

I have a direct stake in this: I build NYUS, an India-first AI fitness and nutrition coach, and this gap, Indian home food without a macro label, is why it exists. Its database has 8,900+ foods with macros, including the dal, rice, khichdi and curd-rice staples runners eat, logged by photo, barcode or search. With your permission it reads steps, sleep and heart data from compatible wearables through Health Connect, and a weekly check-in reviews what you logged and, once enough is logged, adjusts your calories, macros and step goal.

But the method above works with a kitchen scale and IFCT alone, no app required. The point isn't the tool. You can't fuel deliberately around a number you never measured, and for the Indian dishes most runners actually eat, that number usually has to be worked out at home.

NYUS is in early access

An AI fitness and diet coach built for Indian food: a weekly check-in that adjusts your calories, macros and step goal from what you log, 8,900+ foods with macros, in English, Hindi and Hinglish. No ads, no data sold.

Join the early-access list

Frequently asked questions

Is dal-chawal good before a long run?

Dal-chawal is a carbohydrate-rich meal that many runners use the evening before a long run. How well it suits you depends on portion, timing and your own digestion, so test it on training runs and check with a coach or dietitian if unsure.

How do I calculate macros for home-cooked dal or khichdi?

Weigh the raw rice and dal, look up their values in IFCT 2017 (which lists raw foods), add any oil or ghee, and divide the total by the number of portions. Reuse that per-portion figure each time you cook the same recipe.

Does NYUS work for runners?

NYUS logs meals and workouts, reads steps, sleep and heart data via Health Connect, and has a weekly check-in that adjusts calories, macros and step goal from what you log. It is a general fitness and nutrition coach, not a specialised running coach.

Sources

  1. IFCT 2017 (ICMR-NIN): 528 key foods; except eggs, values for raw foods