Feast Get Feast
Menu

Portions and preparation · USDA nutrition

Fish, perch calories per cup: 155–302 across all 5 named USDA examples

Across all 5 named USDA examples, a cup contains 155–302 calories. Each included example lists 135 g for that measure. The same household label can carry a different gram weight elsewhere in USDA data.

Portion calculator

Estimate your portion

Choose a source measure or enter the weight you ate.

Preparation and portion

Named measures come from this exact source record.

Estimated for 1 small/regular fillet · 90 g

125calories

Fish, perch, baked or broiled

Protein
17.1 g
Carbs
0 g
Fat
5.8 g

These values scale the selected reference food by weight. Ingredients, preparation, and portion size can change your meal’s estimate.

FoodData Central Survey Foods (FNDDS) · FDC 2706271 Full nutrition profile →

Compare all 5 food records, nutrition tables and USDA sources

The 5 exact records in this guide report 104–202 calories in the records' own listed source servings and 115–224 calories per 100 grams. Those are observations from named database records—not a universal range or an estimate of an unseen plate.

Match my meal

Start with the description closest to what you ate

For Fish, perch, begin by separating “Fish, perch, baked or broiled” from “Fish, perch, steamed.” Choosing a card filters this source set; it does not infer the portion or fill in ingredients the chosen description does not name.

Showing all 5 linked records.

Equal-weight view

How fish, perch records compare at 100 grams

All 5 cited records are shown at the same 100-gram weight. The source servings may differ.

  1. Fish, perch, steamed 115 kcal
    115 kcal
  2. Fish, perch, grilled 121 kcal
    121 kcal
  3. Fish, perch, baked or broiled 139 kcal
    139 kcal
  4. Fish, perch, baked or broiled, coated 163 kcal
    163 kcal
  5. Fish, perch, fried 224 kcal
    224 kcal

Shared basis: 100 g · kilocalories

What this page compares

Named source records, not one universal meal

This guide keeps 5 named USDA records in view: 5 direct matches. All sit within “Fish.” The exact descriptions remain the unit of comparison; the familiar heading is only the doorway into the evidence.

Why these records appear together: The deterministic grouping rule “normalized first two description segments” placed these 5 records together under the exact grouping key “fish perch.” That rule determines membership before any nutrition result is read.

For Fish, perch, this page can compare 5 named records from FDC 2706271 through FDC 2706275. It cannot observe which preparation was eaten, recover unnamed additions, or supply the eaten grams.

Read the shared calculation, provenance, and uncertainty method →

Editor’s decision brief

The three facts to carry into the table

Carry the denominator, exact identity, and strongest observed contrast into every number below.

Portion

A shared 90 g comparison anchor

Equal source weights make the selected Fish, perch serving totals easier to compare, but the eaten portion still has to be measured or estimated.

Composition

109 kcal separates the fixed-weight endpoints

The lower endpoint is “steamed”; the higher is “fried.” This isolates density, not ingredient causation.

Discriminator

224 mg sodium gap per 100 g

Of protein, fiber, and sodium, the strongest normalized contrast is between “steamed” (176 mg) and “fried” (400 mg).

Observed source examples

Three landmarks inside this source set—not universal endpoints

These 5 records each use a 90 g serving. Their serving calories compare equal weights within this set. They do not define a calorie range for every fish, perch; match the preparation and adjust to your portion.

Important: “Lower” begins with Fish, perch, steamed; “higher” ends with Fish, perch, fried, using each record’s own source amount. Those labels order this selected set only—they are not endpoints for every fish, perch meal.

Full comparison

Compare every selected FNDDS record

For Fish, perch, serving columns preserve each record’s own listed amount, while calories per 100 g hold weight constant. A dash means the cited record does not supply that field; it does not mean the nutrient is absent.

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

USDA records selected for the Fish, perch nutrition guide
Exact source record Match Source amount Calories kcal / 100 g Protein Fiber Sodium USDA
Fish, perch, baked or broiled Direct name match 90 gUSDA reference amount 125 kcal 139 17.1 g 0 g 278 mg FDC 2706271 ↗
Fish, perch, baked or broiled, coated Direct name match 90 gUSDA reference amount 147 kcal 163 15.6 g 0.3 g 308 mg FDC 2706273 ↗
Fish, perch, fried Direct name match 90 gUSDA reference amount 202 kcal 224 12.2 g 0.5 g 360 mg FDC 2706274 ↗
Fish, perch, grilled Direct name match 90 gUSDA reference amount 109 kcal 121 17.5 g 0 g 273 mg FDC 2706272 ↗
Fish, perch, steamed Direct name match 90 gUSDA reference amount 104 kcal 115 22.1 g 0 g 158 mg FDC 2706275 ↗

Portion analysis

Serving total and calorie density answer different questions

Every selected record uses a 90-gram source amount, so serving-weight differences do not explain the calorie spread inside this set. Their own source servings run from 104 calories for “steamed” to 202 for “fried.” At a fixed 100 grams, “steamed” is 115 calories and “fried” is 224—a fixed-weight separation of 109 calories. For Fish, perch, the serving view answers “how much is in the database portion?”; the 100-gram view answers “how concentrated is the matched record?” Neither reveals how many grams were actually eaten.

The scaling rule: multiply a per-100-gram value by eaten grams ÷ 100. The arithmetic is exact; the result is only as defensible as the record match and portion estimate.

Preparation analysis

The long description carries the evidence

The published descriptions distinguish forms such as “perch, baked or broiled”, “perch, baked or broiled, coated”, “perch, fried”, “perch, grilled”, and “perch, steamed”. Across the source formulations, the shared backbone includes salt, table; differentiating rows include fish, ocean perch, atlantic, raw, oil or table fat, nfs, breading or batter as ingredient in food, and fish, perch, mixed species, raw. On this Fish, perch page, those rows make the records inspectable, but they are not a controlled experiment: they cannot tell us that one named input, by itself, caused a nutrient difference.

Database precision is not meal certainty. Retain the exact description beside the number so later corrections remain possible.

What changes the comparison

Four drivers worth checking before choosing a record

The family label “Fish, perch” cannot resolve the differences between Fish, perch, baked or broiled and Fish, perch, steamed. The four checks below identify the record wording, source weight, and formulation evidence that can.

  1. 01

    A shared source weight

    Every selected record uses 90 grams. Inside this set, serving-calorie differences therefore reflect the published composition rather than a change in source weight.

  2. 02

    The words that split the family

    Representative record-level distinctions include “perch, baked or broiled”, “perch, baked or broiled, coated”, “perch, fried”, “perch, grilled”, and “perch, steamed”. Those phrases are evidence for choosing a record, not decorative subtitle text.

  3. 03

    Formulation evidence, with limits

    Shared source rows include salt, table; rows that vary across the set include fish, ocean perch, atlantic, raw, oil or table fat, nfs, and breading or batter as ingredient in food. Presence is inspectable evidence, not proof of nutrient causation.

  4. 04

    The unresolved plate

    Even “Fish, perch, baked or broiled” leaves the eaten grams and unnamed oils, sauces, toppings, substitutions, or leftovers unresolved. Preserve those Fish, perch unknowns for correction instead of converting them into false precision.

Record matching

Match identity first; scale quantity second

Read the source name as a sequence of decisions. First confirm that fish, perch is the right meal family. Then resolve the phrases that actually separate this set—“perch, baked or broiled”, “perch, baked or broiled, coated”, “perch, grilled”, and “perch, steamed”—before comparing gram weight. If a package, menu, or known recipe provides a closer first-party description, prefer it and keep this USDA record as a transparent fallback.

A practical matching checklist

  1. Read the complete Fish, perch source description, including preparation and additions.
  2. Compare the listed source weight with the amount actually eaten.
  3. Prefer a current package or restaurant source when a specific branded item is known.
  4. Record toppings, sauces, cooking fat, sides, and substitutions that the selected description does not name.

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 5 exact records behind Fish, perch source-record guide. Links are chosen by record identity, controlled contrast, formulation input, nutrient spread, or serving context—not by loose keyword similarity.

Equal-weight result

Fish, perch, fried is higher in carbohydrate per 100 g

Fish, perch, fried reports 11.7 g versus 0 g for Fish, perch, grilled: a 11.7 g difference when both are normalized to 100 g.

Inspect the underlying evidence

These listed servings have equal weights

5 listed servings each weigh 90 g

The 5 records with a listed serving weight on this page each use 90 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.

Choose the record before reading the number

Fish, perch, baked or broiled, coated and Fish, perch, steamed are not interchangeable

The page keeps both records at the same 100 g denominator and makes Preparation wording (baked, roasted, or broiled versus steamed) the explicit record-description contrast. It does not show that the wording difference caused a nutrient difference. Pick the description that matches the food in front of you rather than averaging away the distinction.

Inspect the underlying evidence

Contextual knowledge graph

Follow the relationship that matches your question

For Fish, perch source-record guide, each path states why the destination belongs here, so you can distinguish a true evidentiary connection from a merely similar label.

Compare two records on this page Fish, perch, baked or broiled, coated vs Fish, perch, steamed

Both records appear in this page’s evidence set. The explicit record-description contrast is Preparation wording: baked, roasted, or broiled versus steamed; it is a selection cue, not evidence of cause.

Follow this evidence path Compare two records on this page Fish, perch, baked or broiled vs Fish, perch, steamed

Both records appear in this page’s evidence set. The explicit record-description contrast is Preparation wording: baked, roasted, or broiled versus steamed; it is a selection cue, not evidence of cause.

Follow this evidence path 5 context records in this source topic Fish

Fish, perch, baked or broiled and Fish, perch, baked or broiled, coated 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 formulation detail that separates records Fish, ocean perch, Atlantic, raw

USDA input 15057 appears in 4 of 5 context records; its summed listed input weight spans 65–98 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 Oil or table fat, NFS

USDA input 81200100 appears in 3 of 5 context records; its summed listed input weight spans 2–4 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 Put the observed spread in corpus context Iron: density and serving context

In this page’s records, iron runs from 0.3 mg in Fish, perch, baked or broiled to 1.1 mg in Fish, perch, steamed, all per 100 g.

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

In this page’s records, vitamin D runs from 1 µg in Fish, perch, fried to 3.8 µg in Fish, perch, steamed, all per 100 g.

Follow this evidence path