Sweet potato, baked, fat added
- Source serving
- 115 kcal
- Per 100 g
- 115 kcal
- Protein
- 1.6 g
USDA record comparison
The 9 exact records in this guide report 20–187 calories in the records' own listed source servings and 57–187 calories per 100 grams. Those are observations from named database records—not a universal range or an estimate of an unseen plate.
What this page compares
This page includes every selected Feast nutrition record whose normalized USDA description begins with “Sweet potato” under the documented one-segment family rule. The records fall within Other red and orange vegetables and Other dark green vegetables. Exact descriptions remain visible so this grouping does not erase preparation, ingredient, or source-serving differences.
How this guide was assembled: Feast deterministically grouped exact USDA FNDDS records by their source descriptions. Every nutrient number is computed from the linked source fields; this page does not use generated or invented nutrition estimates.
Every number on this page comes from the exact linked record. Values are descriptive observations from the selected records; they are not personalized estimates, recommended portions, or measurements of a meal in front of you.
Match my meal
Choose an exact FNDDS description to focus the record cards and comparison table. This narrows the source evidence; it does not infer your portion or ingredients.
Showing all 9 linked records.
Observed source examples
These cards order the selected records by calories in each record's own FNDDS source serving. They do not define the calorie range of every sweet potato and should not be used as a personalized estimate.
20kcal
35 g source amount · 57 kcal per 100 g
Inspect this exact record115kcal
100 g source amount · 115 kcal per 100 g
Inspect this exact record187kcal
100 g source amount · 187 kcal per 100 g
Inspect this exact recordImportant: “Lower,” “middle,” and “higher” refer only to order within the selected source set above. Different source-serving weights and, where labeled, contextual records mean these cards are examples—not endpoints of a meal estimate.
Full comparison
Serving values preserve each record's listed amount. Per-100-gram calories provide a shared weight basis. Dashes indicate that a value is not available, not that the nutrient is absent.
| Exact source record | Match | Source amount | Calories | kcal / 100 g | Protein | Fiber | Sodium | USDA |
|---|---|---|---|---|---|---|---|---|
| Sweet potato, baked, fat added | Direct name match | 100 gQuantity not specified | 115 kcal | 115 | 1.6 g | 3 g | 161 mg | FDC 2709700 ↗ |
| Sweet potato, baked, no added fat | Direct name match | 100 gQuantity not specified | 82 kcal | 82 | 1.6 g | 3.1 g | 154 mg | FDC 2709699 ↗ |
| Sweet potato, boiled, fat added | Direct name match | 100 gQuantity not specified | 115 kcal | 115 | 1.6 g | 3 g | 161 mg | FDC 2709703 ↗ |
| Sweet potato, boiled, no added fat | Direct name match | 100 gQuantity not specified | 82 kcal | 82 | 1.6 g | 3.1 g | 154 mg | FDC 2709702 ↗ |
| Sweet potato, candied | Direct name match | 100 gQuantity not specified | 187 kcal | 187 | 1.2 g | 2.2 g | 121 mg | FDC 2709704 ↗ |
| Sweet potato, canned, fat added | Direct name match | 100 gQuantity not specified | 124 kcal | 124 | 1.6 g | 1.7 g | 211 mg | FDC 2709707 ↗ |
| Sweet potato, canned, no added fat | Direct name match | 100 gQuantity not specified | 91 kcal | 91 | 1.6 g | 1.8 g | 207 mg | FDC 2709706 ↗ |
| Sweet potato, casserole or mashed | Direct name match | 125 gQuantity not specified | 124 kcal | 99 | 2.4 g | 3 g | 165 mg | FDC 2709708 ↗ |
| Sweet potato, squash, pumpkin, chrysanthemum, or bean leaves, cooked | Direct name match | 35 gQuantity not specified | 20 kcal | 57 | 0.7 g | 0.6 g | 45 mg | FDC 2709642 ↗ |
Portion analysis
The listed source amounts span 35–125 grams, a 3.6× difference in mass before recipe or preparation is considered. Within the selected set, the source servings report 20–187 calories in the records' own listed source servings; the fixed-weight view reports 57–187 calories per 100 grams. A serving total and a per-100-gram value answer different questions, so neither should be substituted for the amount actually eaten.
To scale a record, divide the eaten grams by the record's source grams and multiply the listed serving values by that ratio. This assumes the eaten meal has the same composition as the matched record.
Preparation analysis
The record names distinguish baked, boiled, canned, candied, and casserole or mashed. USDA formulation rows also identify 7 distinct source-input codes across the set, including sweet potato, cooked, as ingredient, oil or table fat, nfs, sugars, granulated, and sweet potato, canned, vacuum pack. These details can help select a closer record, but they do not isolate the cause of a nutrient difference or reconstruct a recipe.
A precise-looking result is only as specific as the record match and the portion information supporting it.
What changes the comparison
The visible dish name is a starting point. These details usually explain more of the variation in the selected source records.
The exact records list 35–125 grams, so serving totals can move even before composition is compared.
The set explicitly distinguishes baked, boiled, canned, candied, and casserole or mashed; those words identify different records rather than optional SEO phrasing.
Across each record's own source serving, the displayed data span protein 0.7–2.4 g, fiber 0.6–3.1 g, sodium 45–211 mg. Different serving weights remain visible beside those values.
The source rows include 7 distinct input codes across this set. Input presence and weight describe standardized source formulations, not final plated proportions.
Record matching
Begin with the full source description rather than the shortest dish name. Check whether the named form—such as baked, boiled, canned, candied, and casserole or mashed—matches the meal, then compare the listed source weight with the portion actually eaten. If the brand, recipe, toppings, cooking fat, or portion is known, keep that information with the estimate instead of assuming the generic record already includes it.