Portions and preparation · USDA nutrition

Burrito, beef calories per cup: 263–320 across all 4 named USDA examples

Across all 4 named USDA examples, a cup contains 263–320 calories. Each included example lists 120 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 small/regular · 190 g

507calories

Burrito, beef, cheese

Protein
25.3 g
Carbs
53.8 g
Fat
20.3 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 2708535 Full nutrition profile →

Compare all 4 food records, nutrition tables and USDA sources

The 4 exact records in this guide report 482–508 calories in the records' own listed source servings and 219–267 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 Burrito, beef, begin by separating “Burrito, beef, cheese” from “Burrito, beef, with rice, cheese.” 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 4 linked records.

Equal-weight view

How burrito, beef records compare at 100 grams

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

  1. 219 kcal
  2. 225 kcal
  3. 231 kcal
  4. 267 kcal

Shared basis: 100 g · kilocalories

What this page compares

Named source records, not one universal meal

This guide keeps 4 named USDA records in view: 4 direct matches. All sit within “Burritos and tacos.” 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 two description segments” placed these 4 records together under the exact grouping key “burrito beef.” That rule determines membership before any nutrition result is read.

For Burrito, beef, this page can compare 4 named records from FDC 2708535 through FDC 2708536. 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

190–220 g before composition

The largest source amount is 1.2× the smallest. Read per-serving calorie differences with that mass gap in view.

Composition

48 kcal separates the fixed-weight endpoints

The lower endpoint is “with beans”; the higher is “beef, cheese.” This isolates density, not ingredient causation.

Discriminator

1.0 g fiber gap per 100 g

Of protein, fiber, and sodium, the strongest normalized contrast is between “with rice” (1.5 g) and “with beans” (2.5 g).

Observed source examples

Three landmarks inside this source set—not universal endpoints

The cards are ordered by calories in each record's listed serving. Serving weights differ, so use per-100-gram values to compare composition. These selected records do not define a calorie range for every burrito, beef.

Important: “Lower” begins with Burrito, beef, with beans, cheese; “higher” ends with Burrito, beef, with rice, cheese, using each record’s own source amount. Those labels order this selected set only—they are not endpoints for every burrito, beef meal.

Full comparison

Compare every selected FNDDS record

For Burrito, beef, 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 Burrito, beef nutrition guide
Exact source record Match Source amount Calories kcal / 100 g Protein Fiber Sodium USDA
Burrito, beef, cheese Direct name match 190 gUSDA reference amount 507 kcal 267 25.3 g 3.8 g 863 mg FDC 2708535 ↗
Burrito, beef, with beans and rice, cheese Direct name match 220 gUSDA reference amount 495 kcal 225 23.8 g 4.4 g 1,023 mg FDC 2708538 ↗
Burrito, beef, with beans, cheese Direct name match 220 gUSDA reference amount 482 kcal 219 24.4 g 5.5 g 1,069 mg FDC 2708537 ↗
Burrito, beef, with rice, cheese Direct name match 220 gUSDA reference amount 508 kcal 231 22.9 g 3.3 g 979 mg FDC 2708536 ↗

Portion analysis

Serving total and calorie density answer different questions

The listed source amounts run from 190 to 220 grams—a 30-gram gap before composition enters the comparison. Their own source servings run from 482 calories for “with beans” to 508 for “with rice.” At a fixed 100 grams, “with beans” is 219 calories and “beef, cheese” is 267—a fixed-weight separation of 48 calories. For Burrito, beef, 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 “beef, cheese”, “beef, with beans and rice, cheese”, “beef, with beans, cheese”, and “beef, with rice, cheese”. Across the source formulations, the shared backbone includes beef as ingredient in recipes, beverages, water, tap, drinking, and cheese and queso as ingredient; differentiating rows include salt, table, refried beans, canned, traditional, reduced sodium, and rice, white, long-grain, regular, enriched, cooked. On this Burrito, beef 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 “Burrito, beef” cannot resolve the differences between Burrito, beef, cheese and Burrito, beef, with rice, cheese. The four checks below identify the record wording, source weight, and formulation evidence that can.

  1. 01

    Source weight before serving calories

    The source amounts span 190–220 grams. Compare per 100 grams before reading a serving-calorie gap as a composition gap.

  2. 02

    The words that split the family

    Representative record-level distinctions include “beef, cheese”, “beef, with beans and rice, cheese”, “beef, with beans, cheese”, and “beef, with rice, cheese”. Those phrases are evidence for choosing a record, not decorative subtitle text.

  3. 03

    Formulation evidence, with limits

    Shared source rows include beef as ingredient in recipes and beverages, water, tap, drinking; rows that vary across the set include salt, table, refried beans, canned, traditional, reduced sodium, and rice, white, long-grain, regular, enriched, cooked. Presence is inspectable evidence, not proof of nutrient causation.

  4. 04

    The unresolved plate

    Even “Burrito, beef, cheese” leaves the eaten grams and unnamed oils, sauces, toppings, substitutions, or leftovers unresolved. Preserve those Burrito, beef 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 burrito, beef is the right meal family. Then resolve the phrases that actually separate this set—“beef, cheese”, “beef, with beans and rice, cheese”, “beef, with beans, cheese”, and “beef, with rice, cheese”—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 Burrito, beef 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 4 exact records behind Burrito, beef 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

Burrito, beef, with beans, cheese is higher in potassium per 100 g

Burrito, beef, with beans, cheese reports 212 mg versus 127 mg for Burrito, beef, with rice, cheese: a 85 mg difference when both are normalized to 100 g.

Inspect the underlying evidence

The denominator changes the answer

Burrito, beef, cheese is denser; Burrito, beef, with rice, cheese is higher in its source amount

Burrito, beef, cheese reports 267 kcal per 100 g and 507 kcal in USDA source amount (190 g). Burrito, beef, with rice, cheese reports a lower 231 kcal per 100 g but a higher 508 kcal in USDA source amount (220 g).

Record identity is part of the estimate

Distinguish “Burrito, beef, cheese” from “Burrito, beef, with rice, cheese”

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 Burrito, beef 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 3 of 4 context records; its summed listed input weight spans 0.3–0.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
A formulation detail that separates records Refried beans, canned, traditional, reduced sodium

USDA input 16403 appears in 2 of 4 context records; its summed listed input weight spans 15–30 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
4 context records in this source topic Burritos and tacos

Burrito, beef, cheese and Burrito, beef, with beans and rice, cheese 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 Potassium: density and serving context

In this page’s records, potassium runs from 127 mg in Burrito, beef, with rice, cheese to 212 mg in Burrito, beef, with beans, cheese, all per 100 g.

Follow this evidence path
Inspect an exact record Burrito, beef, cheese

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

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

In this page’s records, dietary fiber runs from 1.5 g in Burrito, beef, with rice, cheese to 2.5 g in Burrito, beef, with beans, cheese, all per 100 g.

Follow this evidence path
Check another exact record Burrito, beef, with beans and rice, cheese

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

Follow this evidence path