Lower observed Context record
206kcal
Vegetable curry with rice
200 g source amount · 103 kcal per 100 g
Inspect this exact recordUSDA record comparison
Chicken curry calories and nutrition: curry alone versus with rice
FNDDS provides two direct chicken-curry descriptions: curry alone and chicken curry with rice. Related curry-and-rice records are shown only as context, making the database boundary explicit instead of manufacturing extra chicken-curry variants.
What this page compares
Named source records, not one universal meal
The two direct matches anchor this page. Vegetable, fish, beef, and lentil curry-with-rice records are adjacent FNDDS context records; they illustrate how the survey system represents other curry bowls but are not substitutes for chicken curry. Cards and tables label that distinction throughout.
Every number on this page comes from the exact linked record. Values are descriptive observations from the selected records; they are not personalized estimates, recommended portions, or measurements of a meal in front of you.
Observed source examples
Lower, middle, and higher within this selected set
These cards order the selected records by calories in each record's own FNDDS source serving. They do not define the calorie range of every chicken curry and should not be used as a personalized estimate.
Middle observed Direct name match
232kcal
Chicken curry with rice
200 g source amount · 116 kcal per 100 g
Inspect this exact record Higher observed Direct name match
257kcal
Chicken curry
240 g source amount · 107 kcal per 100 g
Inspect this exact recordImportant: “Lower,” “middle,” and “higher” refer only to order within the curated source set above. Different source-serving weights and, where labeled, contextual records mean these cards are examples—not endpoints of a meal estimate.
Full comparison
Compare every selected FNDDS record
Serving values preserve each record's listed amount. Per-100-gram calories provide a shared weight basis. Dashes indicate that a value is not available, not that the nutrient is absent.
| Exact source record | Match | Source amount | Calories | kcal / 100 g | Protein | Fiber | Sodium | USDA |
|---|---|---|---|---|---|---|---|---|
| Chicken curry with rice | Direct name match | 200 gQuantity not specified | 232 kcal | 116 | 9.9 g | 2 g | 648 mg | FDC 2706438 ↗ |
| Chicken curry | Direct name match | 240 gQuantity not specified | 257 kcal | 107 | 15.6 g | 3.4 g | 902 mg | FDC 2706437 ↗ |
| Vegetable curry with rice | Context record | 200 gQuantity not specified | 206 kcal | 103 | 4.1 g | 2.6 g | 662 mg | FDC 2710068 ↗ |
| Fish curry with rice | Context record | 200 gQuantity not specified | 214 kcal | 107 | 8.1 g | 2 g | 618 mg | FDC 2706461 ↗ |
| Beef curry with rice | Context record | 200 gQuantity not specified | 238 kcal | 119 | 11.2 g | 2 g | 628 mg | FDC 2706389 ↗ |
| Lentil curry with rice | Context record | 200 gQuantity not specified | 236 kcal | 118 | 6.6 g | 4.4 g | 656 mg | FDC 2707432 ↗ |
Context record Context records are intentionally nearby but non-equivalent descriptions. Their presence documents a sparse source category; it does not broaden the meaning of Chicken curry.
Portion analysis
Serving total and calorie density answer different questions
The direct curry-alone record uses a 240-gram reference amount, while the chicken-curry-with-rice record uses 200 grams. The lower serving total for one record therefore cannot be attributed to rice or sauce without also considering the different source weight. Calories per 100 grams provide the needed second view.
To scale a record, divide the eaten grams by the record's source grams and multiply the listed serving values by that ratio. This assumes the eaten meal has the same composition as the matched record.
Preparation analysis
The dish name leaves ingredients unresolved
The chicken-to-sauce ratio, cut of chicken, coconut milk or other sauce base, added oil, and rice quantity can all change the finished profile. The generic FNDDS name does not specify a regional recipe. A thick curry and a broth-like curry may have different densities even at the same volume.
A precise-looking result is only as specific as the record match and the portion information supporting it.
What changes the comparison
Four drivers worth checking before choosing a record
The visible dish name is a starting point. These details usually explain more of the variation in the selected source records.
- 01
Rice included or separate
The direct records represent curry alone and curry with rice using different source weights.
- 02
Chicken-to-sauce ratio
More sauce or more chicken changes both density and macronutrient composition.
- 03
Sauce base
Coconut milk, stock, tomato, yogurt, and other bases are not distinguished by the generic source name.
- 04
Added cooking fat
Oil incorporated during sautéing or finishing may not be visually separable from the sauce.
Record matching
How to find the closest description
First decide whether rice is included in the weighed portion or recorded separately. Then estimate the ratio of chicken to sauce and identify conspicuous additions. Use one of the two direct records when its description fits; use the contextual records only to understand database boundaries, never to relabel a different protein as chicken.
A practical matching checklist
- Keep rice inside the matched serving or log it separately—never both.
- Choose a direct chicken record before considering contextual entries.
- Compare curry thickness and chicken-to-sauce ratio.
- Use recipe quantities when the sauce base and oil are known.