Feast Get Feast
Menu

Portions and preparation · USDA nutrition

Soup, vegetable calories per cup: 66–108 across all 4 named USDA examples

Across all 4 named USDA examples, a cup contains 66–108 calories. Each included example lists 245 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 · 245 g

66calories

Soup, vegetable

Protein
2.1 g
Carbs
12.4 g
Fat
1.1 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 2710113 Full nutrition profile →

Compare all 4 food records, nutrition tables and USDA sources

The 4 exact records in this guide report 66–108 calories in the records' own listed source servings and 27–44 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 Soup, vegetable, begin by separating “Soup, vegetable” from “Soup, vegetable, with meat.” 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 soup, vegetable records compare at 100 grams

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

  1. Soup, vegetable 27 kcal
    27 kcal
  2. Soup, vegetable, canned 38 kcal
    38 kcal
  3. Soup, vegetable, canned, reduced sodium 38 kcal
    38 kcal
  4. Soup, vegetable, with meat 44 kcal
    44 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 “Soups, broth-based.” 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 “soup vegetable.” That rule determines membership before any nutrition result is read.

For Soup, vegetable, this page can compare 4 named records from FDC 2710113 through FDC 2710116. 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 245 g comparison anchor

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

Composition

17 kcal separates the fixed-weight endpoints

The lower endpoint is “vegetable”; the higher is “with meat.” This isolates density, not ingredient causation.

Discriminator

2.5 g protein gap per 100 g

Of protein, fiber, and sodium, the strongest normalized contrast is between “vegetable” (0.8 g) and “with meat” (3.4 g).

Observed source examples

Three landmarks inside this source set—not universal endpoints

These 4 records each use a 245 g serving. Their serving calories compare equal weights within this set. They do not define a calorie range for every soup, vegetable; match the preparation and adjust to your portion.

Important: “Lower” begins with Soup, vegetable; “higher” ends with Soup, vegetable, with meat, using each record’s own source amount. Those labels order this selected set only—they are not endpoints for every soup, vegetable meal.

Full comparison

Compare every selected FNDDS record

For Soup, vegetable, 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 Soup, vegetable nutrition guide
Exact source record Match Source amount Calories kcal / 100 g Protein Fiber Sodium USDA
Soup, vegetable Direct name match 245 gUSDA reference amount 66 kcal 27 2.1 g 2.5 g 595 mg FDC 2710113 ↗
Soup, vegetable, canned Direct name match 245 gUSDA reference amount 93 kcal 38 2.7 g 2.9 g 637 mg FDC 2710111 ↗
Soup, vegetable, canned, reduced sodium Direct name match 245 gUSDA reference amount 93 kcal 38 2.7 g 2.9 g 448 mg FDC 2710112 ↗
Soup, vegetable, with meat Direct name match 245 gUSDA reference amount 108 kcal 44 8.2 g 2 g 610 mg FDC 2710116 ↗

Portion analysis

Serving total and calorie density answer different questions

Every selected record uses a 245-gram source amount, so serving-weight differences do not explain the calorie spread inside this set. Their own source servings run from 66 calories for “vegetable” to 108 for “with meat.” At a fixed 100 grams, “vegetable” is 27 calories and “with meat” is 44—a fixed-weight separation of 17 calories. For Soup, vegetable, 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 “vegetable”, “vegetable, canned”, “vegetable, canned, reduced sodium”, and “vegetable, with meat”. The source formulations contain 11 distinct ingredient codes; examples that appear in only part of the set include beverages, water, tap, drinking, mirepoix, cooked, as ingredient, salt, table, and vegetable oil, nfs. On this Soup, vegetable 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 “Soup, vegetable” cannot resolve the differences between Soup, vegetable and Soup, vegetable, with meat. 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 245 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 “vegetable”, “vegetable, canned”, “vegetable, canned, reduced sodium”, and “vegetable, with meat”. Those phrases are evidence for choosing a record, not decorative subtitle text.

  3. 03

    Formulation evidence, with limits

    11 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 “Soup, vegetable” leaves the eaten grams and unnamed oils, sauces, toppings, substitutions, or leftovers unresolved. Preserve those Soup, vegetable 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 soup, vegetable is the right meal family. Then resolve the phrases that actually separate this set—“vegetable”, “vegetable, canned”, “vegetable, canned, reduced sodium”, and “vegetable, with meat”—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 Soup, vegetable 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 Soup, vegetable 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

Soup, vegetable, with meat is higher in total fat per 100 g

Soup, vegetable, with meat reports 1.6 g versus 0.4 g for Soup, vegetable, canned: a 1.2 g difference when both are normalized to 100 g.

Inspect the underlying evidence

These listed servings have equal weights

4 listed servings each weigh 245 g

The 4 records with a listed serving weight on this page each use 245 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 “Soup, vegetable” from “Soup, vegetable, with meat”

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 Soup, vegetable 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 Beverages, water, tap, drinking

USDA input 14411 appears in 3 of 4 context records; its summed listed input weight spans 50–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 Mirepoix, cooked, as ingredient

USDA input 99997805 appears in 3 of 4 context records; its summed listed input weight spans 10–15 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 Soups, broth-based

Soup, vegetable and Soup, vegetable, canned 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 Protein: density and serving context

In this page’s records, protein runs from 0.8 g in Soup, vegetable to 3.4 g in Soup, vegetable, with meat, all per 100 g.

Follow this evidence path Inspect an exact record Soup, vegetable

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

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

In this page’s records, calories runs from 27 kcal in Soup, vegetable to 44 kcal in Soup, vegetable, with meat, all per 100 g.

Follow this evidence path Check another exact record Soup, vegetable, canned

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

Follow this evidence path