White potatoes, baked or boiled100 g vs 100 gTwo cited FDC records

Potato, baked, peel eaten vs Potato, boiled, ready-to-heatUSDA FDC 2709524 vs 2709386

A controlled equal-weight comparison of two exact USDA survey-food records, with source descriptions, representative amounts, listed formulation inputs, and interpretation limits kept visible.

Record A · FDC 2709524

Potato, baked, peel eaten

Check this record in FoodData Central ↗

Record B · FDC 2709386

Potato, boiled, ready-to-heat

Check this record in FoodData Central ↗

Equal-weight evidence

Nutrition per 100 grams

Both columns use the same mass, which compares nutrient concentration without allowing the two representative source amounts to change the denominator. “A +” or “B +” reports the arithmetic difference between the cited values; it is not a quality score.

Per-100-gram nutrient comparison for Potato, baked, peel eaten and Potato, boiled, ready-to-heat
NutrientA · Potato, baked, peel eatenB · Potato, boiled, ready-to-heatDifference
CaloriesMaterial under the publication gate 93 kcal 126 kcal B +33 kcal
Protein 2.5 g 1.9 g A +0.6 g
Total fatMaterial under the publication gate 0.1 g 4.3 g B +4.1 g
Carbohydrate 21 g 20.4 g A +0.6 g
Dietary fiber 2.2 g 1.4 g A +0.8 g
Total sugars 1.2 g 1.6 g B +0.4 g
Sodium 186 mg 166 mg A +20 mg
Saturated fatMaterial under the publication gate 0 g 1.1 g B +1.1 g
PotassiumMaterial under the publication gate 533 mg 372 mg A +161 mg
Calcium 15 mg 5 mg A +10 mg
Iron 1.1 mg 0.3 mg A +0.7 mg

Values come from the two cited USDA FoodData Central Survey Foods records. Feast does not average records, impute missing values, or infer a nutrient from the food name.

Calories difference

33 kcal per 100 g

Potato, boiled, ready-to-heat reports 33 kcal more calories per 100 grams than Potato, baked, peel eaten (126 versus 93 kcal).

The absolute difference is 26% of the larger reported value. That percentage describes these two records only; it is not an estimate of biological effect or expected variation.

Total fat difference

4.1 g per 100 g

Potato, boiled, ready-to-heat reports 4.1 g more total fat per 100 grams than Potato, baked, peel eaten (4.3 versus 0.1 g).

The absolute difference is 97% of the larger reported value. That percentage describes these two records only; it is not an estimate of biological effect or expected variation.

What differs in the source descriptions

The exact names carry information the numbers cannot.

USDA assigns both records to “White potatoes, baked or boiled,” but the topic label is broad. Record A is “Potato, baked, peel eaten.” Record B is “Potato, boiled, ready-to-heat.” Feast paired them because their contrast-neutral food identities are an exact match, not merely because they share a generic category.

The controlled name parser found 3 interpretable distinctions. These labels organize wording already present in the names; they do not establish that a distinction caused a nutrient difference.

Controlled wording distinctions
Description dimensionRecord ARecord B
Preparation wordingbaked, roasted, or broiledboiled or poached
Peel wordingpeel eatenNo matching controlled term in the source name
Source contextNo matching controlled term in the source nameready to heat

Even a clean name contrast can carry hidden companions. A fried record may also include coating; a restaurant record can use a different recipe; a reduced-sodium description can differ in more than salt; and a source amount can reflect a different reporting convention. That is why this page reports the complete pair rather than treating one word as an intervention.

Portion context

A representative source amount is not a shared “serving.”

Record A uses Typical reported amount at 285 g. Record B uses Typical reported amount at 170 g. Those labels and gram weights come from their respective records. They are useful for scaling the chosen profile, but they are not recommendations and need not describe equal amounts.

The two representative amounts differ by 115 g (40% of the larger amount). This is why the main table holds mass at 100 g. After selecting the closer description, use its household measure or a gram estimate for the amount actually eaten.

A cup, piece, slice, sandwich, fillet, or fluid ounce can have different gram weights across records. A matching label is not enough: check the listed grams. If accuracy matters more than convenience, weighing the food or using a current package label can be more specific than a generic survey-food measure.

Record A measures

  • 1 small230 g
  • 1 medium285 g
  • 1 large400 g
  • 1 cup130 g
  • Quantity not specified285 g
Scale record A →

Record B measures

  • 1 baby potato60 g
  • 1 new potato60 g
  • 1 small130 g
  • 1 medium170 g
  • 1 large300 g
  • 1 cup160 g
  • Quantity not specified170 g
Scale record B →

USDA source formulation evidence

The listed inputs provide another way to audit the match.

FNDDS includes input-food rows behind each standardized survey-food record. Record A’s leading listed inputs include Potatoes, baked, flesh and skin, without salt, Salt, table. Record B’s include Potatoes, baked, flesh, without salt, Oil or table fat, NFS, Salt, table. Ingredient-code overlap is 25%, and normalized listed-input-weight variation is 100%.

Record A · 2 input rows

Potato, baked, peel eaten

  1. Potatoes, baked, flesh and skin, without saltIngredient code 11674
    99.5% of listed input weight
  2. Salt, tableIngredient code 2047
    0.5% of listed input weight

Record B · 3 input rows

Potato, boiled, ready-to-heat

  1. Potatoes, baked, flesh, without saltIngredient code 11363
    94.9% of listed input weight
  2. Oil or table fat, NFSIngredient code 81200100
    4.7% of listed input weight
  3. Salt, tableIngredient code 2047
    0.4% of listed input weight

1 shared coded input

The largest shared entries include Salt, table. Shared codes can still carry different listed weights.

1 A-only and 2 B-only coded inputs

A-only entries include Potatoes, baked, flesh and skin, without salt. B-only entries include Potatoes, baked, flesh, without salt, Oil or table fat, NFS.

Important: these weights belong to USDA’s source formulation. Their percentages are shares of the listed input weight, not a reconstructed plate, final cooked yield, visitor serving, ingredient declaration, or estimate of what is visible in a photo.

Choosing the closer record

Match context first; scale second.

  1. 01

    Read both names literally

    Compare cooking method, coating, edible skin or peel, sauce, additions, venue, source form, and food subtype. For this pair, the full A and B descriptions above are the evidence—not shortened search labels.

  2. 02

    Use listed inputs as a check

    If the name still leaves ambiguity, compare the leading and unique source inputs. They can reveal that two near names refer to meaningfully different standardized formulations, but they do not reconstruct your dish.

  3. 03

    Choose an amount for that record

    After choosing A or B, use its own named measure and gram weight. Do not transfer a cup, slice, or “typical amount” from the other record as if the measures were interchangeable.

  4. 04

    Account for missing details

    Brand, current restaurant recipe, cooking oil, drained weight, toppings, substitutions, and unfinished portions may not be captured. A label or weighed recipe can supersede a generic reference when it better matches the actual food.

Limits and responsible interpretation

This is a comparison of records, not a causal study.

The two records come from 2021–2023 FoodData Central Survey Foods data. The nutrient table faithfully compares their published values on the same weight basis. It does not measure two plates prepared at the same time, isolate one ingredient, or estimate the uncertainty around either value.

Several details can change together. Moisture affects concentration per 100 grams. Coating or sauce can add carbohydrate and sodium. Edible skin or fat changes the portion represented. Restaurant, school, frozen, canned, fresh, home-recipe, and ready-to-heat records may use distinct standardized formulations. The source descriptions and input lists help show those differences, but they cannot assign cause.

A higher or lower number is not an overall verdict. Protein, fiber, sodium, energy, fat, micronutrients, preferences, allergies, budget, portion, and an individual’s goals answer different questions. Feast therefore reports directions and magnitudes without applying a universal “healthier” label.

This page is educational and does not diagnose a condition, prescribe a target, or replace advice from a qualified professional. For an allergy, medically directed diet, or strict ingredient limit, use verified ingredient information and guidance appropriate to that situation.

How this page qualified

A page is published only when the pair clears materiality and diversity gates.

Both records must occupy the same USDA survey-food topic and share a close food identity after a controlled vocabulary separates preparation, edible-part, source, claim, crust, and sauce wording. Exact contrast-neutral identities receive priority. Close ingredient or form substitutions can qualify when name overlap remains high and the numerical evidence is material.

For primary nutrients, Feast requires both an absolute and relative difference: at least 20 kcal and 12% for energy; 2 g and 18% for protein or fat; 5 g and 15% for carbohydrate; 1 g and 20% for fiber; 4 g and 20% for sugars; or 100 mg and 20% for sodium. A focused one-nutrient pair also needs a material representative-amount or formulation distinction. Rounding-only pairs are not published.

Unordered FDC IDs define a canonical pair, so reversing A and B cannot create another page. Each source record can appear twice at most, each USDA topic contributes no more than 40 pages, and closely repeated identity families are capped. Those rules produced a selective comparison library rather than every mathematical combination in the corpus.

Read the complete nutrition-page methodology for import, nutrient mapping, portion scaling, Daily Value, and uncertainty rules.