Simple calculation example
We assume a 75kg man with a medium to good performance level (VO2 max: 50 ml/min/kg, 10k best time: 45 min). For him, we assume a usable, endogenous carbohydrate store of approx. 500 g. We calculate within the Twaiv app with our algorithms Dependent carbohydrate consumption:
- 10 km/h: 90 g/h
- 11 km/h: 120 g/h
- 12 km/h: 150 g/h
When we Extrapolate these figures to the total time for the marathon, the result is as follows:
- 10 km/h: 90 g/h x 4:15 h = 380 g
- 11 km/h: 120 g/h x 3:50 h = 460 g
- 12 km/h: 150 g/h x 3:30 h = 525 g
This calculation shows us clearly: 4:15 h will be no problem at all. 3:50 h will work very precisely (the memory will in fact never be completely empty!). 3:30 hours will most likely not be enough (but this is depending on carbohydrate intake during running). We can make a similar calculation in the Twaiv app in our competition forecasts Include!
The relationship between carbohydrate consumption and VO2 max
More fat metabolism means “saving” carbohydrates. In order to metabolize more fat, the body needs oxygen. Oxygen is absorbed through the lungs and transported to the muscles via the cardiovascular system. The determining factor for fat metabolism is the amount of oxygen that the muscle can absorb and convert. The more oxygen the muscle can utilize, the higher the percentage of fat in the energy supply (2).
As part of our analytics within the Twaiv app We also determine the so-called maximum oxygen uptake (VO2 max). This parameter is highly correlated with the ability to metabolize fat and thus conserve important carbohydrate stores (see figure below).