Feast Get Feast
Menu

Portions and preparation · USDA nutrition

Beans and rice calories per cup: 233–315 across all 3 named USDA examples

Across all 3 named USDA examples, a cup contains 233–315 calories. Each included example lists 170 g for that measure. The same household label can carry a different gram weight elsewhere in USDA data.

Portion calculator

Estimate your portion

Choose a source measure or enter the weight you ate.

Preparation and portion

Named measures come from this exact source record.

Estimated for 1 cup · 170 g

315calories

Beans and rice, from fast food / restaurant

Protein
10.7 g
Carbs
41.5 g
Fat
11.9 g

These values scale the selected reference food by weight. Ingredients, preparation, and portion size can change your meal’s estimate.

FoodData Central Survey Foods (FNDDS) · FDC 2708986 Full nutrition profile →

Compare all 3 food records, nutrition tables and USDA sources

The 3 exact records in this guide report 233–315 calories in the records' own listed source servings and 137–185 calories per 100 grams. Those are observations from named database records—not a universal range or an estimate of an unseen plate.

Match my meal

Start with the description closest to what you ate

For Beans and rice, begin by separating “Beans and rice, from fast food / restaurant” from “Beans and rice, with tomatoes.” Choosing a card filters this source set; it does not infer the portion or fill in ingredients the chosen description does not name.

Showing all 3 linked records.

Equal-weight view

How beans and rice records compare at 100 grams

All 3 cited records are shown at the same 100-gram weight. The source servings may differ.

  1. Beans and rice, with tomatoes 137 kcal
    137 kcal
  2. Beans and rice, with meat 162 kcal
    162 kcal
  3. Beans and rice, from fast food / restaurant 185 kcal
    185 kcal

Shared basis: 100 g · kilocalories

What this page compares

Named source records, not one universal meal

This guide keeps 3 named USDA records in view: 3 direct matches. All sit within “Bean, pea, legume dishes.” The exact descriptions remain the unit of comparison; the familiar heading is only the doorway into the evidence.

Why these records appear together: The deterministic grouping rule “normalized first description segment” placed these 3 records together under the exact grouping key “beans and rice.” That rule determines membership before any nutrition result is read.

For Beans and rice, this page can compare 3 named records from FDC 2708986 through FDC 2708991. It cannot observe which preparation was eaten, recover unnamed additions, or supply the eaten grams.

Read the shared calculation, provenance, and uncertainty method →

Editor’s decision brief

The three facts to carry into the table

Carry the denominator, exact identity, and strongest observed contrast into every number below.

Portion

A shared 170 g comparison anchor

Equal source weights make the selected Beans and rice serving totals easier to compare, but the eaten portion still has to be measured or estimated.

Composition

48 kcal separates the fixed-weight endpoints

The lower endpoint is “with tomatoes”; the higher is “from fast food / restaurant.” This isolates density, not ingredient causation.

Discriminator

2.8 g protein gap per 100 g

Of protein, fiber, and sodium, the strongest normalized contrast is between “with tomatoes” (4.7 g) and “with meat” (7.5 g).

Observed source examples

Three landmarks inside this source set—not universal endpoints

These 3 records each use a 170 g serving. Their serving calories compare equal weights within this set. They do not define a calorie range for every beans and rice; match the preparation and adjust to your portion.

Important: “Lower” begins with Beans and rice, with tomatoes; “higher” ends with Beans and rice, from fast food / restaurant, using each record’s own source amount. Those labels order this selected set only—they are not endpoints for every beans and rice meal.

Full comparison

Compare every selected FNDDS record

For Beans and rice, serving columns preserve each record’s own listed amount, while calories per 100 g hold weight constant. A dash means the cited record does not supply that field; it does not mean the nutrient is absent.

On smaller screens, focus the table and scroll horizontally to read every column.

USDA records selected for the Beans and rice nutrition guide
Exact source record Match Source amount Calories kcal / 100 g Protein Fiber Sodium USDA
Beans and rice, from fast food / restaurant Direct name match 170 gUSDA reference amount 315 kcal 185 10.7 g 6.1 g 508 mg FDC 2708986 ↗
Beans and rice, with meat Direct name match 170 gUSDA reference amount 275 kcal 162 12.7 g 7.5 g 447 mg FDC 2708992 ↗
Beans and rice, with tomatoes Direct name match 170 gUSDA reference amount 233 kcal 137 8 g 6.5 g 525 mg FDC 2708991 ↗

Portion analysis

Serving total and calorie density answer different questions

Every selected record uses a 170-gram source amount, so serving-weight differences do not explain the calorie spread inside this set. Their own source servings run from 233 calories for “with tomatoes” to 315 for “from fast food / restaurant.” At a fixed 100 grams, “with tomatoes” is 137 calories and “from fast food / restaurant” is 185—a fixed-weight separation of 48 calories. For Beans and rice, the serving view answers “how much is in the database portion?”; the 100-gram view answers “how concentrated is the matched record?” Neither reveals how many grams were actually eaten.

The scaling rule: multiply a per-100-gram value by eaten grams ÷ 100. The arithmetic is exact; the result is only as defensible as the record match and portion estimate.

Preparation analysis

The long description carries the evidence

The published descriptions distinguish forms such as “from fast food / restaurant”, “with meat”, and “with tomatoes”. Across the source formulations, the shared backbone includes rice, white, cooked, no added fat; differentiating rows include beans and tomatoes, fat added, black beans with meat, pinto beans with meat, and salt, table. On this Beans and rice page, those rows make the records inspectable, but they are not a controlled experiment: they cannot tell us that one named input, by itself, caused a nutrient difference.

Database precision is not meal certainty. Retain the exact description beside the number so later corrections remain possible.

What changes the comparison

Four drivers worth checking before choosing a record

The family label “Beans and rice” cannot resolve the differences between Beans and rice, from fast food / restaurant and Beans and rice, with tomatoes. The four checks below identify the record wording, source weight, and formulation evidence that can.

  1. 01

    A shared source weight

    Every selected record uses 170 grams. Inside this set, serving-calorie differences therefore reflect the published composition rather than a change in source weight.

  2. 02

    The words that split the family

    Representative record-level distinctions include “from fast food / restaurant”, “with meat”, and “with tomatoes”. Those phrases are evidence for choosing a record, not decorative subtitle text.

  3. 03

    Formulation evidence, with limits

    Shared source rows include rice, white, cooked, no added fat; rows that vary across the set include beans and tomatoes, fat added, black beans with meat, and pinto beans with meat. Presence is inspectable evidence, not proof of nutrient causation.

  4. 04

    The unresolved plate

    Even “Beans and rice, from fast food / restaurant” leaves the eaten grams and unnamed oils, sauces, toppings, substitutions, or leftovers unresolved. Preserve those Beans and rice unknowns for correction instead of converting them into false precision.

Record matching

Match identity first; scale quantity second

Read the source name as a sequence of decisions. First confirm that beans and rice is the right meal family. Then resolve the phrases that actually separate this set—“from fast food / restaurant”, “with meat”, and “with tomatoes”—before comparing gram weight. If a package, menu, or known recipe provides a closer first-party description, prefer it and keep this USDA record as a transparent fallback.

A practical matching checklist

  1. Read the complete Beans and rice source description, including preparation and additions.
  2. Compare the listed source weight with the amount actually eaten.
  3. Prefer a current package or restaurant source when a specific branded item is known.
  4. Record toppings, sauces, cooking fat, sides, and substitutions that the selected description does not name.

Decision support from the exact records on this page

Turn source data into a better next decision

These conclusions and reading paths are computed from 3 exact records behind Beans and rice source-record guide. Links are chosen by record identity, controlled contrast, formulation input, nutrient spread, or serving context—not by loose keyword similarity.

Equal-weight result

Beans and rice, with tomatoes is higher in total sugars per 100 g

Beans and rice, with tomatoes reports 0.8 g versus 0.2 g for Beans and rice, from fast food / restaurant: a 0.6 g difference when both are normalized to 100 g.

Inspect the underlying evidence

These listed servings have equal weights

3 listed servings each weigh 170 g

The 3 records with a listed serving weight on this page each use 170 g. Their serving totals therefore compare equal weights, even if the household labels differ. Match the preparation and adjust the weight to the amount you eat.

Record identity is part of the estimate

Distinguish “Beans and rice, from fast food / restaurant” from “Beans and rice, with tomatoes”

These are separate USDA records with separate formulations or survey descriptions. Match preparation, additions, and the named household amount before borrowing either record’s nutrients.

Inspect the underlying evidence

Contextual knowledge graph

Follow the relationship that matches your question

For Beans and rice source-record guide, each path states why the destination belongs here, so you can distinguish a true evidentiary connection from a merely similar label.

A formulation detail that separates records Salt, table

USDA input 2047 appears in 1 of 3 context records; its summed listed input weight spans 0.2–0.2 g across those source formulations. These are source-formulation input weights, not plated or serving weights. Follow the code to inspect every represented occurrence.

Follow this evidence path A formulation detail that separates records Vegetable oil, NFS

USDA input 82101000 appears in 1 of 3 context records; its summed listed input weight spans 3–3 g across those source formulations. These are source-formulation input weights, not plated or serving weights. Follow the code to inspect every represented occurrence.

Follow this evidence path 3 context records in this source topic Bean, pea, legume dishes

Beans and rice, from fast food / restaurant and Beans and rice, with meat belong to this USDA source-category collection. Its displayed ranges and complete exact-record catalog provide the peer set for a manual comparison; the destination does not preselect this page’s record.

Follow this evidence path Put the observed spread in corpus context Calcium: density and serving context

In this page’s records, calcium runs from 23 mg in Beans and rice, with tomatoes to 53 mg in Beans and rice, from fast food / restaurant, all per 100 g.

Follow this evidence path Put the observed spread in corpus context Iron: density and serving context

In this page’s records, iron runs from 1.5 mg in Beans and rice, with tomatoes to 2.5 mg in Beans and rice, from fast food / restaurant, all per 100 g.

Follow this evidence path Inspect an exact record Beans and rice, from fast food / restaurant

Open the full nutrient table, household measures, formulation inputs, and FoodData Central 2708986 citation for this exact record—not a name-level average.

Follow this evidence path Check another exact record Beans and rice, with meat

Open the full nutrient table, household measures, formulation inputs, and FoodData Central 2708992 citation for this exact record—not a name-level average.

Follow this evidence path