Feast Get Feast
Menu

Portions and preparation · USDA nutrition

Soup, tomato calories per cup: 47–86 across all 3 named USDA examples

Across all 3 named USDA examples, a cup contains 47–86 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

47calories

Soup, tomato

Protein
1.6 g
Carbs
8.9 g
Fat
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 2709757 Full nutrition profile →

Compare all 3 food records, nutrition tables and USDA sources

The 3 exact records in this guide report 47–86 calories in the records' own listed source servings and 19–35 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, tomato, begin by separating “Soup, tomato” from “Soup, tomato, canned / carton, reduced sodium.” 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 soup, tomato records compare at 100 grams

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

  1. Soup, tomato 19 kcal
    19 kcal
  2. Soup, tomato, canned 34 kcal
    34 kcal
  3. Soup, tomato, canned / carton, reduced sodium 35 kcal
    35 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 “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 3 records together under the exact grouping key “soup tomato.” That rule determines membership before any nutrition result is read.

For Soup, tomato, this page can compare 3 named records from FDC 2709757 through FDC 2709760. 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, tomato serving totals easier to compare, but the eaten portion still has to be measured or estimated.

Composition

16 kcal separates the fixed-weight endpoints

The lower endpoint is “tomato”; the higher is “canned / carton; reduced sodium.” This isolates density, not ingredient causation.

Discriminator

72 mg sodium gap per 100 g

Of protein, fiber, and sodium, the strongest normalized contrast is between “canned / carton; reduced sodium” (191 mg) and “canned” (263 mg).

Observed source examples

Three landmarks inside this source set—not universal endpoints

These 3 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, tomato; match the preparation and adjust to your portion.

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

Full comparison

Compare every selected FNDDS record

For Soup, tomato, 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, tomato nutrition guide
Exact source record Match Source amount Calories kcal / 100 g Protein Fiber Sodium USDA
Soup, tomato Direct name match 245 gUSDA reference amount 47 kcal 19 1.6 g 2.2 g 598 mg FDC 2709757 ↗
Soup, tomato, canned Direct name match 245 gUSDA reference amount 83 kcal 34 1.5 g 1.5 g 644 mg FDC 2709759 ↗
Soup, tomato, canned / carton, reduced sodium Direct name match 245 gUSDA reference amount 86 kcal 35 1.6 g 1.5 g 468 mg FDC 2709760 ↗

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 47 calories for “tomato” to 86 for “canned / carton; reduced sodium.” At a fixed 100 grams, “tomato” is 19 calories and “canned / carton; reduced sodium” is 35—a fixed-weight separation of 16 calories. For Soup, tomato, 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 “tomato”, “tomato, canned”, and “tomato, canned / carton, reduced sodium”. Across the source formulations, the shared backbone includes beverages, water, tap, drinking, salt, table, and tomato products, canned, puree, without salt added; differentiating rows include flour, rice, glutinous, onions, cooked, as ingredient, sugars, granulated, and mirepoix, cooked, as ingredient. On this Soup, tomato 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, tomato” cannot resolve the differences between Soup, tomato and Soup, tomato, canned / carton, reduced sodium. 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 “tomato”, “tomato, canned”, and “tomato, canned / carton, reduced sodium”. Those phrases are evidence for choosing a record, not decorative subtitle text.

  3. 03

    Formulation evidence, with limits

    Shared source rows include beverages, water, tap, drinking and salt, table; rows that vary across the set include flour, rice, glutinous, onions, cooked, as ingredient, and sugars, granulated. Presence is inspectable evidence, not proof of nutrient causation.

  4. 04

    The unresolved plate

    Even “Soup, tomato” leaves the eaten grams and unnamed oils, sauces, toppings, substitutions, or leftovers unresolved. Preserve those Soup, tomato 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, tomato is the right meal family. Then resolve the phrases that actually separate this set—“tomato”, “tomato, canned”, and “tomato, canned / carton, reduced sodium”—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, tomato 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 Soup, tomato 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, tomato, canned / carton, reduced sodium is higher in carbohydrate per 100 g

Soup, tomato, canned / carton, reduced sodium reports 7.7 g versus 3.6 g for Soup, tomato: a 4 g difference when both are normalized to 100 g.

Inspect the underlying evidence

These listed servings have equal weights

3 listed servings each weigh 245 g

The 3 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, tomato” from “Soup, tomato, canned / carton, reduced sodium”

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, tomato 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 Onions, cooked, as ingredient

USDA input 99997510 appears in 2 of 3 context records; its summed listed input weight spans 10–10 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 Sugars, granulated

USDA input 19335 appears in 2 of 3 context records; its summed listed input weight spans 6–6 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 Soups, broth-based

Soup, tomato and Soup, tomato, 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 Calories: density and serving context

In this page’s records, calories runs from 19 kcal in Soup, tomato to 35 kcal in Soup, tomato, canned / carton, reduced sodium, all per 100 g.

Follow this evidence path Inspect an exact record Soup, tomato

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

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

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

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

In this page’s records, potassium runs from 113 mg in Soup, tomato, canned to 169 mg in Soup, tomato, all per 100 g.

Follow this evidence path