USDA record comparison

Tomatoes calories and nutrition: 5 USDA records compared

The 5 exact records in this guide report 4–60 calories in the records' own listed source servings and 20–50 calories per 100 grams. Those are observations from named database records—not a universal range or an estimate of an unseen plate.

What this page compares

Named source records, not one universal meal

This page includes every selected Feast nutrition record whose normalized USDA description begins with “Tomatoes” under the documented one-segment family rule. The records fall within Tomatoes and Vegetables on a sandwich. Exact descriptions remain visible so this grouping does not erase preparation, ingredient, or source-serving differences.

How this guide was assembled: Feast deterministically grouped exact USDA FNDDS records by their source descriptions. Every nutrient number is computed from the linked source fields; this page does not use generated or invented nutrition estimates.

Every number on this page comes from the exact linked record. Values are descriptive observations from the selected records; they are not personalized estimates, recommended portions, or measurements of a meal in front of you.

Match my meal

Start with the description closest to what you ate

Choose an exact FNDDS description to focus the record cards and comparison table. This narrows the source evidence; it does not infer your portion or ingredients.

Showing all 5 linked records.

Observed source examples

Lower, middle, and higher within this selected set

These cards order the selected records by calories in each record's own FNDDS source serving. They do not define the calorie range of every tomatoes and should not be used as a personalized estimate.

Important: “Lower,” “middle,” and “higher” refer only to order within the selected source set above. Different source-serving weights and, where labeled, contextual records mean these cards are examples—not endpoints of a meal estimate.

Full comparison

Compare every selected FNDDS record

Serving values preserve each record's listed amount. Per-100-gram calories provide a shared weight basis. Dashes indicate that a value is not available, not that the nutrient is absent.

USDA records selected for the Tomatoes nutrition guide
Exact source record Match Source amount Calories kcal / 100 g Protein Fiber Sodium USDA
Tomatoes, canned, cooked Direct name match 120 gQuantity not specified 52 kcal 43 1 g 2.2 g 156 mg FDC 2709722 ↗
Tomatoes, canned, reduced sodium, cooked Direct name match 120 gQuantity not specified 47 kcal 39 0.9 g 2.2 g 22 mg FDC 2709724 ↗
Tomatoes, for use on a sandwich Direct name match 20 gQuantity not specified 4 kcal 20 0.2 g 0.2 g 1 mg FDC 2710255 ↗
Tomatoes, fresh, cooked Direct name match 120 gQuantity not specified 60 kcal 50 1.3 g 1.8 g 188 mg FDC 2709721 ↗
Tomatoes, raw Direct name match 90 gQuantity not specified 18 kcal 20 0.7 g 1.1 g 4 mg FDC 2709719 ↗

Portion analysis

Serving total and calorie density answer different questions

The listed source amounts span 20–120 grams, a 6.0× difference in mass before recipe or preparation is considered. Within the selected set, the source servings report 4–60 calories in the records' own listed source servings; the fixed-weight view reports 20–50 calories per 100 grams. A serving total and a per-100-gram value answer different questions, so neither should be substituted for the amount actually eaten.

To scale a record, divide the eaten grams by the record's source grams and multiply the listed serving values by that ratio. This assumes the eaten meal has the same composition as the matched record.

Preparation analysis

The dish name leaves ingredients unresolved

The record names distinguish canned, for use on a sandwich, fresh, and raw. USDA formulation rows also identify 8 distinct source-input codes across the set, including oil or table fat, nfs, tomatoes, red, ripe, raw, year round average, salt, table, and tomato, roma. These details can help select a closer record, but they do not isolate the cause of a nutrient difference or reconstruct a recipe.

A precise-looking result is only as specific as the record match and the portion information supporting it.

What changes the comparison

Four drivers worth checking before choosing a record

The visible dish name is a starting point. These details usually explain more of the variation in the selected source records.

  1. 01

    Source-serving weight

    The exact records list 20–120 grams, so serving totals can move even before composition is compared.

  2. 02

    Named source variant

    The set explicitly distinguishes canned, for use on a sandwich, fresh, and raw; those words identify different records rather than optional SEO phrasing.

  3. 03

    Nutrient profile

    Across each record's own source serving, the displayed data span protein 0.2–1.3 g, fiber 0.2–2.2 g, sodium 1–188 mg. Different serving weights remain visible beside those values.

  4. 04

    Formulation evidence

    The source rows include 8 distinct input codes across this set. Input presence and weight describe standardized source formulations, not final plated proportions.

Record matching

How to find the closest description

Begin with the full source description rather than the shortest dish name. Check whether the named form—such as canned, for use on a sandwich, fresh, and raw—matches the meal, then compare the listed source weight with the portion actually eaten. If the brand, recipe, toppings, cooking fat, or portion is known, keep that information with the estimate instead of assuming the generic record already includes it.

A practical matching checklist

  1. Read the complete tomatoes 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.