Turkey, duck, other poultry100 g vs 100 gTwo cited FDC recordsUpdated

Turkey, light meat: roasted vs skin eaten USDA FDC 2706109 vs 2706106

Per 100 g, roasted reports 139 calories, while skin eaten reports 169 calories.

The comparison uses two cited USDA records. Their complete source names, household portions, nutrient values, and FoodData Central links remain visible below.

Record A · FDC 2706109

Turkey, light meat, roasted, skin not eaten

Check this record in FoodData Central ↗

Record B · FDC 2706106

Turkey, light meat, skin eaten

Check this record in FoodData Central ↗

Highlighted difference

Calories at the same 100-gram weight

Bar length shows the two cited values on one shared denominator. It does not rank either food or establish why they differ.

  1. 139 kcal
  2. 169 kcal

Shared basis: 100 g · kcal

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.

On smaller screens, focus a comparison table and scroll horizontally to read every column.

Per-100-gram nutrient comparison for Turkey, light meat, roasted, skin not eaten and Turkey, light meat, skin eaten
NutrientA · Turkey, light meat, roasted, skin not eatenB · Turkey, light meat, skin eatenDifference
CaloriesMaterial difference 139 kcal 169 kcal B +30 kcal
Protein 28.8 g 28.3 g A +0.5 g
Total fatMaterial difference 2.1 g 5.6 g B +3.5 g
Carbohydrate 0 g 0 g No difference at displayed precision
Dietary fiber 0 g 0 g Same reported value
Total sugars 0 g 0 g Same reported value
Sodium 467 mg 468 mg B +1 mg
Saturated fatMaterial difference 0.6 g 1.6 g B +1 g
Potassium 247 mg 247 mg Same reported value
Calcium 11 mg 12 mg B +1 mg
Iron 0.7 mg 0.7 mg B +0.1 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.

Read the table by question

Every material primary-nutrient difference on this page is numerically higher in B (2 of 2).

These answers describe concentration per 100 grams. “More” and “less” identify the arithmetic direction only; they do not decide which record is a better match or which food is better for a person.

Which reports fewer calories?

Record A

Record A reports 139 kcal, compared with 169 kcal in the other record—a difference of 30 kcal.

Which reports more protein?

Record A

Record A reports 28.8 g, compared with 28.3 g in the other record—a difference of 0.5 g.

Which reports more fiber?

Same reported value

Both records report 0 g of fiber per 100 g.

Which reports less sodium?

Record A

Record A reports 467 mg, compared with 468 mg in the other record—a difference of 1 mg.

What differs in the source descriptions

The exact names carry information the numbers cannot.

USDA assigns both records to “Turkey, duck, other poultry,” but the topic label is broad. Record A is “Turkey, light meat, roasted, skin not eaten.” Record B is “Turkey, light meat, skin eaten.” 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 2 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 broiledNo matching controlled term in the source name
Skin wordingskin not eatenskin eaten

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 USDA reference amount at 85 g. Record B uses USDA reference amount at 85 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 representative amounts do not cross Feast’s material portion-difference threshold of both 15 grams and 20%. They are still separate source measures, so the 100-gram table remains the appropriate place for an equal-weight comparison.

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 small or thin slice30 g
  • 1 medium slice60 g
  • 1 large or thick slice85 g
  • 1 cup, cooked, diced135 g
  • 1 oz, boneless, cooked, skinless28 g
  • USDA reference amount85 g
Scale record A →

Record B measures

  • 1 small or thin slice30 g
  • 1 medium slice60 g
  • 1 large or thick slice85 g
  • 1 oz, boneless, cooked28 g
  • 1 cup, diced, cooked135 g
  • USDA reference amount85 g
Scale record B →

One shared household label

1 medium slice: 60 g in A vs 60 g in B

Here the household label and listed gram weight match at displayed precision, so this particular table is also an equal-mass comparison. The values remain specific to these two source records, not a universal weight for every 1 medium slice.

Nutrition for one 1 medium slice using each record’s own source gram weight
NutrientA · 60 gB · 60 g
Calories83 kcal101 kcal
Protein17.3 g17 g
Dietary fiber0 g0 g
Sodium280 mg281 mg

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 Turkey, all classes, light meat, cooked, roasted, Turkey from whole, light meat, meat only, with added solution, cooked, roasted, Salt, table. Record B’s include Turkey, whole, light meat, meat and skin, cooked, roasted, Turkey from whole, light meat, meat and skin, with added solution, cooked, roasted, Salt, table. Ingredient-code overlap is 20%, and normalized listed-input-weight variation is 99%.

Record A · 3 coded inputs

Turkey, light meat, roasted, skin not eaten

  1. Turkey, all classes, light meat, cooked, roastedIngredient code 5186
    65.5% of listed input weight
  2. Turkey from whole, light meat, meat only, with added solution, cooked, roastedIngredient code 5697
    33.7% of listed input weight
  3. Salt, tableIngredient code 2047 · open source index
    0.8% of listed input weight

Record B · 3 coded inputs

Turkey, light meat, skin eaten

  1. Turkey, whole, light meat, meat and skin, cooked, roastedIngredient code 5182
    65.5% of listed input weight
  2. Turkey from whole, light meat, meat and skin, with added solution, cooked, roastedIngredient code 5703
    33.7% of listed input weight
  3. Salt, tableIngredient code 2047 · open source index
    0.8% of listed input weight

1 shared coded input

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

2 A-only and 2 B-only coded inputs

A-only entries include Turkey, all classes, light meat, cooked, roasted, Turkey from whole, light meat, meat only, with added solution, cooked, roasted. B-only entries include Turkey, whole, light meat, meat and skin, cooked, roasted, Turkey from whole, light meat, meat and skin, with added solution, cooked, roasted.

Important: repeated rows carrying the same ingredient code are combined before the shares and overlap are calculated. These weights belong to USDA’s source formulation: they are not a reconstructed plate, final cooked yield, visitor serving, ingredient declaration, or estimate of what is visible in a photo. USDA’s FNDDS documentation explains that these calculation recipes can represent multiple variants, may include retention or moisture adjustments, and are not product-label ingredient lists.

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.

For this pair, the source names differ across 2 documented description dimensions, while the listed formulations show 20% ingredient-code overlap and 99% normalized listed-weight variation. Moisture, ingredient proportions, preparation, and record construction can therefore move together. The page can describe the combined record difference; it cannot isolate the effect of one word.

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.

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 2 exact records behind Turkey, light meat, roasted, skin not eaten versus Turkey, light meat, skin eaten. Links are chosen by record identity, controlled contrast, formulation input, nutrient spread, or serving context—not by loose keyword similarity.

Equal-weight result

Turkey, light meat, skin eaten is higher in calories per 100 g

Turkey, light meat, skin eaten reports 169 kcal versus 139 kcal for Turkey, light meat, roasted, skin not eaten: a 30 kcal difference when both are normalized to 100 g.

Inspect the underlying evidence

These listed servings have equal weights

2 listed servings each weigh 85 g

The 2 records with a listed serving weight on this page each use 85 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 “Turkey, light meat, roasted, skin not eaten” from “Turkey, light meat, skin eaten”

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 Turkey, light meat, roasted, skin not eaten versus Turkey, light meat, skin eaten, each path states why the destination belongs here, so you can distinguish a true evidentiary connection from a merely similar label.

Best next guide for this exact record Turkey, light meat

Turkey, light meat, roasted, skin not eaten and Turkey, light meat, skin eaten are explicitly linked in this guide, which separates direct name matches from contextual variants.

Follow this evidence path
Test a nearby record choice Turkey, light meat, breaded, baked or fried, skin eaten vs Turkey, light meat, roasted, skin not eaten

Turkey, light meat, roasted, skin not eaten is held as one side of the comparison. The explicit record-description contrast is Preparation wording: baked, roasted, or broiled; fried versus baked, roasted, or broiled; it is a selection cue, not evidence of cause.

Follow this evidence path
2 exact records carried forward Turkey

Turkey, light meat, roasted, skin not eaten and Turkey, light meat, skin eaten are explicitly linked in this guide, which separates direct name matches from contextual variants.

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

In this page’s records, calories runs from 139 kcal in Turkey, light meat, roasted, skin not eaten to 169 kcal in Turkey, light meat, skin eaten, all per 100 g.

Follow this evidence path
2 context records in this source topic Turkey, duck, other poultry

Turkey, light meat, roasted, skin not eaten and Turkey, light meat, skin eaten 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 shared source-formulation input Salt, table

USDA input 2047 appears in 2 of 2 context records; its summed listed input weight spans 0.8–0.8 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
Inspect an exact record Turkey, light meat, roasted, skin not eaten

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

Follow this evidence path