What the chole entry describes
The current FitTrackPro food database hub lists cooked Kabuli chana / chole masala as a 175g bowl. That stored row contains 240 kcal, 13g protein, 33g carbohydrate, 6g fat and 8.5g fiber. Use the cooked serving label as the reference point; the table's other weights are estimates scaled from it.
A home bowl is not a fixed weight. If your katori is smaller or larger than 175g, weigh the cooked chole you serve and use the matching gram estimate. A heaped bowl can weigh much more than a level one. The table preserves the stored 175g serving and clearly marks the scaled rows so they are not mistaken for separately tested values.
The database calls the record “Cooked Kabuli Chana / Chole Masala,” so it should not be treated as a precise nutrition label for all plain boiled chickpeas or every chole recipe. Preparation can include onion, tomato, oil, spices and other ingredients in different amounts. The record does not provide a recipe yield or a measured amount of cooking oil, so restaurant and home versions can vary.
Count the food served with chole separately. Rice, roti, bhatura, puri, pickle and salad are not part of the 175g chole row. The rajma curry page provides another stored bean-curry reference, and the dal calculator compares cooked dal portions. Browse single-food records in the Indian food database or use the daily meal tracker to total several foods together.
The database hub has its own in-page food list, separate from the meal counter's TypeScript data. This chole page uses the 175g row currently displayed by that hub. The site's nutrition methodology explains that per-item source citations are not currently retained and that parallel lists can differ.
Method note
The 175g base value comes from the current in-page chole row on the Indian food database hub, not from a per-item IFCT citation. Other weights are estimates scaled from that entry. Recipe variations, cooking oil and accompaniments are not measured by this page. See the nutrition methodology for data limits and use the contact page to report a suspected error.