Turkey bacon, cooked: standard sodium vs reduced sodium USDA FDC 2706135 vs 2706136
Per 100 g, standard sodium reports 2,020 mg sodium, while reduced sodium reports 900 mg sodium.
The comparison uses two cited USDA records. Their complete source names, household portions, nutrient values, and FoodData Central links remain visible below.
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.
- Turkey bacon, cooked 368 kcal
368 kcal - Turkey bacon, reduced sodium, cooked 253 kcal
253 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.
| Nutrient | A · Turkey bacon, cooked | B · Turkey bacon, reduced sodium, cooked | Difference |
|---|---|---|---|
| CaloriesMaterial difference | 368 kcal | 253 kcal | A +115 kcal |
| ProteinMaterial difference | 29.5 g | 13.3 g | A +16.2 g |
| Total fatMaterial difference | 25.9 g | 20 g | A +5.9 g |
| Carbohydrate | 4.2 g | 4.8 g | B +0.6 g |
| Dietary fiber | 0 g | 0 g | Same reported value |
| Total sugarsMaterial difference | 4.2 g | 0 g | A +4.2 g |
| SodiumMaterial difference | 2,020 mg | 900 mg | A +1,120 mg |
| Saturated fat | 6.9 g | 6.7 g | A +0.3 g |
| PotassiumMaterial difference | 666 mg | 156 mg | A +510 mg |
| Calcium | 163 mg | 10 mg | A +153 mg |
| Iron | 2.6 mg | 0.7 mg | A +1.9 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 A (5 of 5).
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 B
Record B reports 253 kcal, compared with 368 kcal in the other record—a difference of 115 kcal.
Which reports more protein?
Record A
Record A reports 29.5 g, compared with 13.3 g in the other record—a difference of 16.2 g.
Which reports more fiber?
Same reported value
Both records report 0 g of fiber per 100 g.
Which reports less sodium?
Record B
Record B reports 900 mg, compared with 2,020 mg in the other record—a difference of 1,120 mg.
What differs in the source descriptions
The exact names carry information the numbers cannot.
USDA assigns both records to “Bacon,” but the topic label is broad. Record A is “Turkey bacon, cooked.” Record B is “Turkey bacon, reduced sodium, cooked.” 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 1 interpretable distinction. These labels organize wording already present in the names; they do not establish that a distinction caused a nutrient difference.
| Description dimension | Record A | Record B |
|---|---|---|
| Sodium wording | No matching controlled term in the source name | reduced- or low-sodium wording |
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 22 g. Record B uses USDA reference amount at 22 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 oz, cooked28 g
- 1 oz, raw (yield after cooking)16 g
- 1 thin slice (yield after cooking)8 g
- 1 medium slice (yield after cooking)11 g
- 1 thick slice (yield after cooking)14 g
- 1 slice, NFS11 g
- 1 cup, pieces82 g
- USDA reference amount22 g
Record B measures
- 1 oz, cooked28 g
- 1 oz, raw (yield after cooking)16 g
- 1 thin slice (yield after cooking)8 g
- 1 medium slice (yield after cooking)11 g
- 1 thick slice (yield after cooking)14 g
- 1 slice, NFS11 g
- 1 cup, pieces82 g
- USDA reference amount22 g
One shared household label
1 medium slice (yield after cooking): 11 g in A vs 11 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 (yield after cooking).
| Nutrient | A · 11 g | B · 11 g |
|---|---|---|
| Calories | 40 kcal | 28 kcal |
| Protein | 3.2 g | 1.5 g |
| Dietary fiber | 0 g | 0 g |
| Sodium | 222 mg | 99 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 Bacon, turkey, microwaved. Record B’s include Bacon, turkey, low sodium. Ingredient-code overlap is 0%, and normalized listed-input-weight variation is 100%.
Record A · 1 coded input
Turkey bacon, cooked
- Bacon, turkey, microwavedIngredient code 7973100% of listed input weight
Record B · 1 coded input
Turkey bacon, reduced sodium, cooked
- Bacon, turkey, low sodiumIngredient code 7974100% of listed input weight
0 shared coded inputs
The two listed formulations do not share an ingredient code in this source extract. Shared codes can still carry different listed weights.
1 A-only and 1 B-only coded inputs
A-only entries include Bacon, turkey, microwaved. B-only entries include Bacon, turkey, low sodium.
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.
- NFS means “not further specified.” The record intentionally leaves the exact subtype, size, or preparation unresolved.
Choosing the closer record
Match context first; scale second.
- 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.
- 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.
- 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.
- 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 1 documented description dimension, while the listed formulations show 0% ingredient-code overlap and 100% 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 bacon, cooked versus Turkey bacon, reduced sodium, cooked. Links are chosen by record identity, controlled contrast, formulation input, nutrient spread, or serving context—not by loose keyword similarity.
Equal-weight result
Turkey bacon, cooked is higher in calories per 100 g
Turkey bacon, cooked reports 368 kcal versus 253 kcal for Turkey bacon, reduced sodium, cooked: a 115 kcal difference when both are normalized to 100 g.
Inspect the underlying evidenceThese listed servings have equal weights
2 listed servings each weigh 22 g
The 2 records with a listed serving weight on this page each use 22 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 bacon, cooked” from “Turkey bacon, reduced sodium, cooked”
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 evidenceContextual knowledge graph
Follow the relationship that matches your question
For Turkey bacon, cooked versus Turkey bacon, reduced sodium, cooked, each path states why the destination belongs here, so you can distinguish a true evidentiary connection from a merely similar label.
Turkey bacon, cooked and Turkey bacon, reduced sodium, cooked 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 contextIn this page’s records, calories runs from 253 kcal in Turkey bacon, reduced sodium, cooked to 368 kcal in Turkey bacon, cooked, all per 100 g.
Follow this evidence path Put the observed spread in corpus context Calcium: density and serving contextIn this page’s records, calcium runs from 10 mg in Turkey bacon, reduced sodium, cooked to 163 mg in Turkey bacon, cooked, all per 100 g.
Follow this evidence path Inspect an exact record Turkey bacon, cookedOpen the full nutrient table, household measures, formulation inputs, and FoodData Central 2706135 citation for this exact record—not a name-level average.
Follow this evidence path Check another exact record Turkey bacon, reduced sodium, cookedOpen the full nutrient table, household measures, formulation inputs, and FoodData Central 2706136 citation for this exact record—not a name-level average.
Follow this evidence path 2 records share this broad food family Meat & poultry: broader category contextTurkey bacon, cooked and Turkey bacon, reduced sodium, cooked are assigned to Feast’s Meat & poultry editorial category. Use the category page to compare nearby foods at a broad level; keep the exact USDA descriptions on this page for record-level decisions.
Follow this evidence path Put the observed spread in corpus context Vitamin D: density and serving contextIn this page’s records, vitamin D runs from 0.2 µg in Turkey bacon, reduced sodium, cooked to 1.2 µg in Turkey bacon, cooked, all per 100 g.
Follow this evidence path