Feast Get Feast
Menu

Portions and preparation · USDA nutrition

Beets calories per cup: 53–117 across all 6 named USDA examples

Across all 6 named USDA examples, a cup contains 53–117 calories. Their listed weights span 135–175 g, so each calorie value is calculated from that example's own gram weight and published calories per 100 g.

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 88 g

47calories

Beets, canned, cooked, fat added

Protein
0.8 g
Carbs
6.2 g
Fat
2.4 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 2709876 Full nutrition profile →

Compare all 6 food records, nutrition tables and USDA sources

The 6 exact records in this guide report 26–59 calories in the records' own listed source servings and 31–67 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 Beets, begin by separating “Beets, canned, cooked, fat added” from “Beets, raw.” 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 6 linked records.

Equal-weight view

How beets records compare at 100 grams

Five rank landmarks are shown from all 6 cited records: minimum, 25th-ranked, median-ranked, 75th-ranked, and maximum. Weight is held at 100 grams; source-serving weights are listed in the table.

  1. Minimum: Beets, canned, cooked, no added fat 31 kcal
    31 kcal
  2. 25th-ranked landmark: Beets, raw 43 kcal
    43 kcal
  3. Median-ranked landmark: Beets, fresh, cooked, no added fat 45 kcal
    45 kcal
  4. 75th-ranked landmark: Beets, canned, cooked, fat added 53 kcal
    53 kcal
  5. Maximum: Beets, fresh, cooked, fat added 67 kcal
    67 kcal

Shared basis: 100 g · kilocalories

What this page compares

Named source records, not one universal meal

This guide keeps 6 named USDA records in view: 6 direct matches. All sit within “Other vegetables and combinations.” 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 6 records together under the exact grouping key “beets.” That rule determines membership before any nutrition result is read.

For Beets, this page can compare 6 named records from FDC 2709876 through FDC 2709770. 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

68–88 g before composition

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

Composition

36 kcal separates the fixed-weight endpoints

The lower endpoint is “canned, cooked, no added fat”; the higher is “fresh, cooked, fat added.” This isolates density, not ingredient causation.

Discriminator

1.7 g fiber gap per 100 g

Of protein, fiber, and sodium, the strongest normalized contrast is between “reduced sodium” (1.2 g) and “fresh, cooked, no added fat” (2.9 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 beets.

Important: “Lower” begins with Beets, canned, cooked, no added fat; “higher” ends with Beets, fresh, cooked, fat added, using each record’s own source amount. Those labels order this selected set only—they are not endpoints for every beets meal.

Full comparison

Compare every selected FNDDS record

For Beets, 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 Beets nutrition guide
Exact source record Match Source amount Calories kcal / 100 g Protein Fiber Sodium USDA
Beets, canned, cooked, fat added Direct name match 88 gUSDA reference amount 47 kcal 53 0.8 g 1.5 g 173 mg FDC 2709876 ↗
Beets, canned, cooked, no added fat Direct name match 85 gUSDA reference amount 26 kcal 31 0.8 g 1.5 g 165 mg FDC 2709873 ↗
Beets, canned, reduced sodium, cooked Direct name match 85 gUSDA reference amount 45 kcal 53 0.7 g 1 g 26 mg FDC 2709877 ↗
Beets, fresh, cooked, fat added Direct name match 88 gUSDA reference amount 59 kcal 67 1.4 g 2.5 g 180 mg FDC 2709875 ↗
Beets, fresh, cooked, no added fat Direct name match 85 gUSDA reference amount 38 kcal 45 1.4 g 2.5 g 172 mg FDC 2709872 ↗
Beets, raw Direct name match 68 gUSDA reference amount 29 kcal 43 1.1 g 1.9 g 53 mg FDC 2709770 ↗

Portion analysis

Serving total and calorie density answer different questions

The listed source amounts run from 68 to 88 grams—a 20-gram gap before composition enters the comparison. Their own source servings run from 26 calories for “canned, cooked, no added fat” to 59 for “fresh, cooked, fat added.” At a fixed 100 grams, “canned, cooked, no added fat” is 31 calories and “fresh, cooked, fat added” is 67—a fixed-weight separation of 36 calories. For Beets, 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 “canned, cooked, fat added”, “canned, cooked, no added fat”, “fresh, cooked, fat added”, “fresh, cooked, no added fat”, and “raw”. The source formulations contain 5 distinct ingredient codes; examples that appear in only part of the set include beets, raw, oil or table fat, nfs, beets, canned, drained solids, and salt, table. On this Beets 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 “Beets” cannot resolve the differences between Beets, canned, cooked, fat added and Beets, raw. 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 68–88 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 “canned, cooked, fat added”, “canned, cooked, no added fat”, “fresh, cooked, fat added”, “fresh, cooked, no added fat”, and “raw”. Those phrases are evidence for choosing a record, not decorative subtitle text.

  3. 03

    Formulation evidence, with limits

    5 source-input codes appear across the selected records. Their presence and listed weights describe USDA formulations, not finished plated proportions.

  4. 04

    The unresolved plate

    Even “Beets, canned, cooked, fat added” leaves the eaten grams and unnamed oils, sauces, toppings, substitutions, or leftovers unresolved. Preserve those Beets 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 beets is the right meal family. Then resolve the phrases that actually separate this set—“canned, cooked, fat added”, “canned, reduced sodium, cooked”, “fresh, cooked, fat added”, and “raw”—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 Beets 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 6 exact records behind Beets 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

Beets, fresh, cooked, fat added is higher in total fat per 100 g

Beets, fresh, cooked, fat added reports 2.8 g versus 0.1 g for Beets, canned, cooked, no added fat: a 2.7 g difference when both are normalized to 100 g.

Inspect the underlying evidence

The denominator changes the answer

Beets, canned, cooked, no added fat is denser; Beets, canned, cooked, fat added is higher in its source amount

Beets, canned, cooked, no added fat reports 0.9 g per 100 g and 0.8 g in USDA source amount (85 g). Beets, canned, cooked, fat added reports a lower 0.9 g per 100 g but a higher 0.8 g in USDA source amount (88 g).

Choose the record before reading the number

Beets, canned, cooked, fat added and Beets, raw are not interchangeable

The page keeps both records at the same 100 g denominator and makes Preparation wording (No matching controlled term in the source name versus raw) the explicit record-description contrast. It does not show that the wording difference caused a nutrient difference. Pick the description that matches the food in front of you rather than averaging away the distinction.

Inspect the underlying evidence

Contextual knowledge graph

Follow the relationship that matches your question

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

Compare two records on this page Beets, canned, cooked, fat added vs Beets, raw

Both records appear in this page’s evidence set. The explicit record-description contrast is Preparation wording: No matching controlled term in the source name versus raw; it is a selection cue, not evidence of cause.

Follow this evidence path Compare two records on this page Beets, canned, reduced sodium, cooked vs Beets, fresh, cooked, no added fat

Both records appear in this page’s evidence set. The explicit record-description contrast is Added-fat wording: No matching controlled term in the source name versus no added fat; it is a selection cue, not evidence of cause.

Follow this evidence path 6 context records in this source topic Other vegetables and combinations

Beets, canned, cooked, fat added and Beets, canned, cooked, no added fat 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 A formulation detail that separates records Beets, raw

USDA input 11080 appears in 3 of 6 context records; its summed listed input weight spans 100–100 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 Oil or table fat, NFS

USDA input 81200100 appears in 3 of 6 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 Put the observed spread in corpus context Sodium: density and serving context

In this page’s records, sodium runs from 31 mg in Beets, canned, reduced sodium, cooked to 205 mg in Beets, fresh, cooked, fat added, 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 0.7 mg in Beets, canned, reduced sodium, cooked to 1.8 mg in Beets, canned, cooked, no added fat, all per 100 g.

Follow this evidence path