Taco, corn tortilla, with beans: pork vs standard USDA FDC 2708518 vs 2708521
Per 100 g, pork reports 10.3 g protein, while standard reports 5.8 g protein.
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 2708518
Taco, corn tortilla, pork, with beans, cheese
Check this record in FoodData Central ↗Record B · FDC 2708521
Taco, corn tortilla, with beans, cheese
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.
-
214 kcal -
176 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 · Taco, corn tortilla, pork, with beans… | B · Taco, corn tortilla, with beans, cheese | Difference |
|---|---|---|---|
| CaloriesMaterial difference | 214 kcal | 176 kcal | A +38 kcal |
| ProteinMaterial difference | 10.3 g | 5.8 g | A +4.5 g |
| Total fatMaterial difference | 10.9 g | 7.3 g | A +3.6 g |
| Carbohydrate | 19.1 g | 23 g | B +3.9 g |
| Dietary fiberMaterial difference | 3.2 g | 4.2 g | B +1 g |
| Total sugars | 0.5 g | 0.6 g | B +0.2 g |
| Sodium | 395 mg | 420 mg | B +25 mg |
| Saturated fatMaterial difference | 3.2 g | 1.8 g | A +1.4 g |
| Potassium | 230 mg | 249 mg | B +19 mg |
| Calcium | 74 mg | 76 mg | B +2 mg |
| Iron | 1.3 mg | 1.2 mg | No difference at displayed precision |
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
The material primary-nutrient differences run in both directions: A is higher on 3, while B is higher on 1.
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 176 kcal, compared with 214 kcal in the other record—a difference of 38 kcal.
Which reports more protein?
Record A
Record A reports 10.3 g, compared with 5.8 g in the other record—a difference of 4.5 g.
Which reports more fiber?
Record B
Record B reports 4.2 g, compared with 3.2 g in the other record—a difference of 1 g.
Which reports less sodium?
Record A
Record A reports 395 mg, compared with 420 mg in the other record—a difference of 25 mg.
What differs in the source descriptions
The exact names carry information the numbers cannot.
USDA assigns both records to “Burritos and tacos,” but the topic label is broad. Record A is “Taco, corn tortilla, pork, with beans, cheese.” Record B is “Taco, corn tortilla, with beans, cheese.” Feast paired them because their contrast-neutral food identities are closely related (83% token overlap after controlled modifiers are set aside), not merely because they share a generic category.
No controlled preparation phrase is needed to explain this pairing. The close source names instead differ in narrow food or ingredient terms. Record A has the distinctive neutral terms pork; Record B has the corresponding terms shown in its exact name. Read the full descriptions before selecting either profile.
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 105 g. Record B uses USDA reference amount at 105 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 miniature50 g
- 1 small/regular105 g
- 1 large160 g
- 1 cup120 g
- USDA reference amount105 g
Record B measures
- 1 miniature50 g
- 1 small/regular105 g
- 1 large160 g
- 1 cup120 g
- USDA reference amount105 g
One shared household label
1 small/regular: 105 g in A vs 105 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 small/regular.
| Nutrient | A · 105 g | B · 105 g |
|---|---|---|
| Calories | 225 kcal | 185 kcal |
| Protein | 10.8 g | 6.1 g |
| Dietary fiber | 3.4 g | 4.4 g |
| Sodium | 415 mg | 441 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 Tortillas, ready-to-bake or -fry, corn, Refried beans, canned, traditional, reduced sodium, Pork, fresh, shoulder, (Boston butt), blade (steaks), separable lean and fat, cooked, braised, Beverages, water, tap, drinking. Record B’s include Refried beans, canned, traditional, reduced sodium, Tortillas, ready-to-bake or -fry, corn, Cheese and Queso as ingredient, Vegetable oil, NFS. Ingredient-code overlap is 71%, and normalized listed-input-weight variation is 28%.
Record A · 7 coded inputs
Taco, corn tortilla, pork, with beans, cheese
- Tortillas, ready-to-bake or -fry, cornIngredient code 18363 · open source index34% of listed input weight
- Refried beans, canned, traditional, reduced sodiumIngredient code 16403 · open source index28.4% of listed input weight
- Pork, fresh, shoulder, (Boston butt), blade (steaks), separable lean and fat, cooked, braisedIngredient code 10081 · open source index23.6% of listed input weight
- Beverages, water, tap, drinkingIngredient code 14411 · open source index4.7% of listed input weight
- Cheese and Queso as ingredientIngredient code 99991410 · open source index4.7% of listed input weight
- Vegetable oil, NFSIngredient code 82101000 · open source index3.8% of listed input weight
- Salt, tableIngredient code 2047 · open source index0.8% of listed input weight
Record B · 5 coded inputs
Taco, corn tortilla, with beans, cheese
- Refried beans, canned, traditional, reduced sodiumIngredient code 16403 · open source index56.7% of listed input weight
- Tortillas, ready-to-bake or -fry, cornIngredient code 18363 · open source index34% of listed input weight
- Cheese and Queso as ingredientIngredient code 99991410 · open source index4.7% of listed input weight
- Vegetable oil, NFSIngredient code 82101000 · open source index3.8% of listed input weight
- Salt, tableIngredient code 2047 · open source index0.8% of listed input weight
5 shared coded inputs
The largest shared entries include Refried beans, canned, traditional, reduced sodium, Tortillas, ready-to-bake or -fry, corn, Cheese and Queso as ingredient, Vegetable oil, NFS, Salt, table. Shared codes can still carry different listed weights.
2 A-only and 0 B-only coded inputs
A-only entries include Pork, fresh, shoulder, (Boston butt), blade (steaks), separable lean and fat, cooked, braised, Beverages, water, tap, drinking.
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 narrow identity terms in the exact source names, while the listed formulations show 71% ingredient-code overlap and 28% 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 Taco, corn tortilla, pork, with beans, cheese versus Taco, corn tortilla, with beans, cheese. Links are chosen by record identity, controlled contrast, formulation input, nutrient spread, or serving context—not by loose keyword similarity.
Equal-weight result
Taco, corn tortilla, pork, with beans, cheese is higher in calories per 100 g
Taco, corn tortilla, pork, with beans, cheese reports 214 kcal versus 176 kcal for Taco, corn tortilla, with beans, cheese: a 38 kcal difference when both are normalized to 100 g.
Inspect the underlying evidenceThese listed servings have equal weights
2 listed servings each weigh 105 g
The 2 records with a listed serving weight on this page each use 105 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 “Taco, corn tortilla, pork, with beans, cheese” from “Taco, corn tortilla, with beans, cheese”
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 Taco, corn tortilla, pork, with beans, cheese versus Taco, corn tortilla, with beans, cheese, each path states why the destination belongs here, so you can distinguish a true evidentiary connection from a merely similar label.
Taco, corn tortilla, pork, with beans, cheese and Taco, corn tortilla, with beans, cheese are explicitly linked in this guide, which separates direct name matches from contextual variants.
Follow this evidence path 2 exact records carried forward TacoTaco, corn tortilla, pork, with beans, cheese and Taco, corn tortilla, with beans, cheese 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 176 kcal in Taco, corn tortilla, with beans, cheese to 214 kcal in Taco, corn tortilla, pork, with beans, cheese, all per 100 g.
Follow this evidence path A formulation detail that separates records Beverages, water, tap, drinkingUSDA input 14411 appears in 1 of 2 context records; its summed listed input weight spans 5–5 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 Pork, fresh, shoulder, (Boston butt), blade (steaks), separable lean and fat, cooked, braisedUSDA input 10081 appears in 1 of 2 context records; its summed listed input weight spans 25–25 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 Test a nearby record choice Taco, corn tortilla, beef, with beans, cheese vs Taco, corn tortilla, with beans, cheeseTaco, corn tortilla, with beans, cheese is held as one side of the comparison. The explicit record-description contrast is Calories: 212 versus 176 kcal per 100 g; it is a selection cue, not evidence of cause.
Follow this evidence path Test a nearby record choice Taco, corn tortilla, pork, cheese vs Taco, corn tortilla, pork, with beans, cheeseTaco, corn tortilla, pork, with beans, cheese is held as one side of the comparison. The explicit record-description contrast is Calories: 251 versus 214 kcal per 100 g; it is a selection cue, not evidence of cause.
Follow this evidence path