USDA ingredient referenceUpdated August 22, 2026

Beans, baked, canned in 3 Feast-indexed USDA foods

Within Feast’s 3,850-record USDA FNDDS reference corpus, “Beans, baked, canned” appears as a formulation input in 3 finished-food records. Their calories and nutrients describe those complete foods, not the input label by itself. Use the catalog to choose the closest finished food and open its exact FoodData Central citation.

Browse all 3 linked food records →

Exact nutrition reference, complete food catalog and source methodology

This page helps you find complete foods that include Beans, baked, canned in USDA’s nutrition data. Choose the record that most closely matches what you ate; Feast does not turn a collection average into a standalone ingredient estimate.

What the code means

One exact source label across 3 complete records.

Every occurrence collected here uses ingredient code 16010 and the source description “Beans, baked, canned, with pork and sweet sauce.” The code is preserved exactly as it appears in the FNDDS input-food rows. It is not a FoodData Central FDC ID, so this page does not invent a standalone ingredient-record URL.

The strongest concentrations of linked records are currently Beans, peas, legumes (3). These are category counts within Feast’s selected 3,850-record corpus. They do not estimate how often the ingredient is eaten, how common it is in recipes generally, or its prevalence across every FNDDS release.

Collection-level interpretation

Grounded ways to understand this source label

These summaries describe the linked FNDDS records in this exact corpus. They do not estimate consumer frequency, market share, or the composition of a meal. This is a very small set of 3 records: each observation can move the percentages, buckets, and interpolated quartiles substantially, so read the complete catalog rather than treating the summaries as stable population estimates.

Typical listed-weight range

87.5%–100%

The middle half of linked records spans 12.5 percentage points from the 25th to the 75th percentile. This is more resistant to a single extreme record than the full minimum-to-maximum range.

Largest linked category

Beans, peas, legumes

3 of 3 linked records (100%) sit in this USDA category. The remainder span 0 other categories.

Most populated share band

60% to 100%

3 records (100%) fall in this band after repeated rows for code 16010 are combined within each food.

Most frequent eligible co-input

Frankfurter, low sodium

It appears alongside code 16010 in 1 linked record (33%). Co-occurrence describes database structure, not a required recipe.

Where USDA uses this input

Linked records by source-food category

Each record is counted once even if ingredient code 16010 appears on more than one input row inside that formulation. The category grouping describes the complete linked foods, not a culinary rule about the ingredient.

USDA survey-food categories

Source-formulation evidence

How the share of listed input weight changes

Repeated rows for code 16010 inside one food are combined before the percentage is calculated. The denominator is the sum of all positive-weight inputs listed for that USDA formulation.

All linked records, not just the extremes

Where the listed-weight shares fall

Each bar counts complete food records after repeated rows for ingredient code 16010 have been combined.

Under 1%0 records
0 of 3
1% to under 5%0 records
0 of 3
5% to under 15%0 records
0 of 3
15% to under 30%0 records
0 of 3
30% to under 60%0 records
0 of 3
60% to 100%3 records
3 of 3

The role changes by food type

Median listed share in the largest USDA categories

Category medians summarize source-formulation shares, not nutrient content or consumption frequency.

Listed-weight share distribution across the largest complete-food categories
Complete-food category	Records	Median	Middle 50%	Observed span
Beans, peas, legumes	3	100%	87.5%–100%	75%–100%

What the spread can tell you

In this collection, “Beans, baked, canned, with pork and sweet sauce” ranges from 75% to 100% of listed source-input weight, with a median of 100%. That variation can help distinguish a food where the input is a small supporting component from a record where it makes up much more of the standardized source formulation.

The spread remains descriptive. It does not show uncertainty around a single recipe, and a high source-weight share does not automatically mean the food supplies more of any particular nutrient. To compare nutrients, use the complete linked records below.

Important nutrition boundary

This collection does not support a verified standalone nutrition answer for “Beans, baked, canned, with pork and sweet sauce.”

No unique exact food-code match or reviewed sole-source bridge qualifies for a direct consumer answer. Feast therefore does not treat the collection median, minimum, maximum, or an arbitrary similar record as the nutrition of this input.

The table below describes the complete linked foods per 100 grams. Use it to find a closer finished-food record, not to infer what this formulation input supplies on its own.

Compare complete food records

Nutrient span across the linked foods

Every value in this table describes an entire USDA survey-food record per 100 grams. The values are not the nutrient content of ingredient code 16010, and differences cannot be attributed to this one input.

Nutrient span across complete food records linked to this source ingredient code
Whole-record nutrient	Observed minimum	Middle 50%	Median	Observed maximum	Linked records
Caloriesper 100 g of the complete food	105 kcal	105–122 kcal	105 kcal	138 kcal	3
Proteinper 100 g of the complete food	4.5 g	4.5–5.6 g	4.5 g	6.7 g	3
Carbohydrateper 100 g of the complete food	17.3 g	19.5–21.6 g	21.6 g	21.6 g	3
Total fatper 100 g of the complete food	0.9 g	0.9–3.1 g	0.9 g	5.2 g	3
Dietary fiberper 100 g of the complete food	3.3 g	3.9–4.4 g	4.4 g	4.4 g	3
Sodiumper 100 g of the complete food	391 mg	391–415 mg	391 mg	438 mg	3

The minimum and maximum preserve the complete observed span. The median is the middle linked-record value, not a prediction for a meal and not an ingredient-specific nutrient estimate.

Complete linked catalog

All 3 Feast-indexed food records that list code 16010

This is the complete qualifying-corpus catalog, not a hand-picked sample. Search by food name or USDA category, then open a profile for household portions, Feast’s 21-nutrient panel, formulation details, and its exact FDC citation.

Filter linked records

3 records shown

Complete USDA food-record catalog linked to this source ingredient code
Linked USDA food record	USDA category	Formulation	Listed input weight	Weight share	Calories	Protein	Sodium	Citation
Baked beans	Beans, peas, legumes	Sole source	100 g	100%	105 kcal	4.5 g	391 mg	FDC 2707390 ↗
Beans and franks	Beans, peas, legumes	3 input rows	75 g	75%	138 kcal	6.7 g	438 mg	FDC 2707405 ↗
Pork and beans	Beans, peas, legumes	Sole source	100 g	100%	105 kcal	4.5 g	391 mg	FDC 2707406 ↗

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 3 exact records behind Beans, baked, canned, with pork and sweet sauce (USDA input 16010). Links are chosen by record identity, controlled contrast, formulation input, nutrient spread, or serving context—not by loose keyword similarity.

Equal-weight result

Beans and franks is higher in total fat per 100 g

Beans and franks reports 5.2 g versus 0.9 g for Baked beans: a 4.3 g difference when both are normalized to 100 g.

Inspect the underlying evidence

These listed servings have equal weights

3 listed servings each weigh 130 g

The 3 records with a listed serving weight on this page each use 130 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 “Baked beans” from “Pork and beans”

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 Beans, baked, canned, with pork and sweet sauce (USDA input 16010), 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 Baked beans

Baked beans is explicitly linked in this guide, which separates direct name matches from contextual variants.

Follow this evidence path A formulation detail that separates records Frankfurter, meat and poultry, low fat

USDA input 42280 appears in 1 of 3 context records; its summed listed input weight spans 10–10 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 3 context records in this source topic Beans, peas, legumes

Baked beans and Beans and franks 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 Test a nearby record choice Baked beans vs Baked beans, reduced sodium

Baked beans is held as one side of the comparison. The explicit record-description contrast is Sodium wording: No matching controlled term in the source name versus reduced- or low-sodium wording; it is a selection cue, not evidence of cause.

Follow this evidence path Inspect an exact record Baked beans

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

Follow this evidence path Check another exact record Beans and franks

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

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

In this page’s records, protein runs from 4.5 g in Baked beans to 6.7 g in Beans and franks, all per 100 g.

Follow this evidence path

Method and provenance

How this ingredient-centered page was calculated

Feast begins with its pinned 3,850-record USDA FoodData Central Survey Foods reference corpus for FNDDS 2021–2023. Each exact food profile retains its FDC identifier, source-food description, nutrient values, household measures, and positive-weight input-food rows. This page groups those input rows by the exact ingredient code 16010; it does not merge similar-looking ingredient names or infer synonyms.

The distinct-record count deduplicates by FDC food record. When the same code is listed more than once inside one source formulation, its input weights are added before the listed-weight share is calculated. Category counts also count each food once. The 25th percentile, median, and 75th percentile use the sorted one-share-per-food values with linear interpolation between adjacent ranks when a percentile falls between two records.

USDA’s current FNDDS documentation explains that many nutrient profiles are generated with calculation recipes designed to represent multiple variants, and that their input codes are not necessarily the exact ingredients in a retail product or an ingredient declaration. It also documents moisture and nutrient-retention adjustments. Feast therefore treats these rows as transparent source-calculation evidence—not as a reverse-engineered recipe.

The complete-food nutrient table uses each linked record’s available published per-100-gram values so the denominator remains consistent; its middle-50% ranges use the same interpolated percentile method. It is presented for record selection and comparison only. No nutrient value is reassigned to the ingredient, no causal effect is inferred, and no “healthy” score is manufactured from the collection.

How to apply the evidence to a meal

Use the ingredient as a discovery clue. Compare the linked record names, food categories, preparation wording, source formulation, and portion measures. If a close record exists, its complete profile can provide a defensible reference estimate. If the meal differs materially in cooking fat, sauce, ingredient ratios, or portion size, keep looking or use recipe weights, a package label, or an editable photo estimate instead.

These pages are educational source indexes. They do not provide medical advice, personalized nutrient targets, food-safety guidance, or a recipe. If a clinician has given you individualized dietary instructions, follow that guidance and use the most specific current source available for the food you actually consumed.