Protein In Beef Per 100g: Raw and Cooked Examples

Protein in beef per 100g is about 20g for raw ground beef described as 90% lean and 10% fat, and about 27g for a 90%-lean ground-beef patty cooked by broiling, according to these specific USDA FoodData Central records: raw ground beef, 90% lean and broiled ground-beef patty, 90% lean. These are rounded reference values for two described foods, not a universal value for every beef cut or a measured before-and-after result for the same portion.

What the raw and cooked figures describe

The raw example is ground beef listed as 90% lean and 10% fat. The cooked example is a ground-beef patty listed as 90% lean and cooked by broiling. That distinction matters: one record describes raw mince, while the other describes a patty after a particular cooking method. The figures are useful estimates for foods resembling those descriptions, but they are not interchangeable labels for all mince, steaks, roasts or prepared beef.

FoodData Central contains records drawn from different data types and sources, so a similar-sounding food name does not guarantee the same product or preparation. USDA’s FoodData Central documentation explains the database’s data types and sources. The practical takeaway is to treat each figure as attached to its record, rather than as a fixed property of “beef.”

The difference between the two values should not be used as a cooking conversion. The records are not a controlled comparison of one batch before and after cooking, and a broiled patty is not the same food description as pan-cooked mince. If you are looking for a steak value or a particular supermarket product, these two entries do not establish it.

Why protein per 100g can rise after cooking

Weight loss changes concentration

A per-100g figure is a concentration: it tells you how much protein is in a 100g portion of the food in the state described. When beef cooks, it can lose water and become lighter. If much of the protein remains while the food weighs less, a 100g portion of the cooked food can contain more protein than a 100g portion of the raw food. The higher concentration does not mean cooking creates protein.

Think of the original piece and the cooked piece as different weight bases. If raw mince weighs more than the cooked mince left in the pan, 100g raw and 100g cooked do not represent the same share of the original food. Comparing those two 100g quantities answers a concentration question, not “how much protein did this original portion gain?” The two USDA examples above illustrate why the basis matters, but their difference cannot tell you the exact yield or protein in your own batch.

What happens to drippings and juices

Cooking can also change what ends up in the food you eat. Rendered fat or liquid may be drained away, left in the pan, or incorporated into a sauce. A plain cooked-beef entry may therefore be a poor description of a finished dish that includes retained juices, added oil or other ingredients. This is especially relevant when you cook a large batch and divide it into meals: the contents of each container depend on how the batch was cooked and portioned.

• Drained mince: the food in the serving excludes what you poured away, so a record for undrained mince may not describe it as closely.
• Mince cooked into a sauce: the juices and other ingredients remain part of the meal, so consider the recipe rather than treating the mince as the whole dish.
• Broiled patty: the USDA cooked example is most relevant when the food and method resemble its record, not simply because the food is beef.

For a recipe, choose one consistent way to account for ingredients. You can log the raw ingredients and divide the completed recipe into portions, or use an appropriate cooked-food entry for portions weighed after cooking. These are alternative accounting approaches; mixing a raw ingredient weight with a cooked-food value is what makes the result hard to interpret.

Why other beef can have a different value

Cut, visible fat and mince blend

Beef composition varies with the cut and the part of the portion included in the weighing. For mince, the lean-to-fat description helps distinguish blends. For steak, the cut and whether visible fat is included affect what the entry needs to describe. A reference for lean ground beef is not automatically a suitable estimate for a fattier mince or a steak with a different amount of trimmed or untrimmed fat.

Protein is only one part of a product comparison. A change in fat content can also change the fat and energy figures, so choosing the largest protein number alone may not suit your macro target. For two packs, compare their full nutrition information and descriptions, not just the protein line. A product with less protein per 100g may still fit a meal plan if its portion size, other macros or recipe role is a better match.

Plain beef versus prepared products

Seasoned mince, formed patties and beef-containing meals may include ingredients beyond plain beef. Those additions can change the nutrition information per 100g of the product or finished dish. For Australian food-composition estimates, the Australian Food Composition Database provides records searchable by food description. A database record can help estimate a described food, but it does not verify what is in a specific supermarket pack or butcher’s cut.

Before using a generic record, make a short description of what you actually have:

• For mince: note whether it is plain or seasoned and what lean-to-fat description is provided.
• For steak: record the cut if known and whether the weighed portion includes visible fat.
• For cooked beef: note the method and whether drippings were drained or retained.
• For a mixed meal: include the other ingredients rather than assigning the whole dish the nutrition of plain beef.

If no record closely matches, report the result as an estimate and keep the mismatch visible in your notes. More decimal places do not make an estimate more accurate when the cut, product or preparation is uncertain.

How to read Australian labels and database entries

Start with the pack in front of you

For packaged beef, the nutrition information panel is usually the most product-specific starting point available to a shopper. Australian requirements for nutrition information panels are set out in Food Standards Code Standard 1.2.8. Read the protein value alongside the product description and the basis shown on the pack. Where the panel gives both per-serving and per-100g figures, the per-100g value can help compare products with different serving sizes.

Check whether the packaging describes nutrition for the product as sold or for a prepared food, and follow any relevant wording on the pack. A value for raw packaged mince is not automatically the concentration in a cooked portion after your own preparation. If the basis is unclear, check the packaging information or ask the manufacturer rather than assuming the figure represents your cooked meal.

For an unlabelled cut or a food without a useful panel, search a food-composition database using the most specific description you know. A database can provide a reasonable reference for a described food, while the pack label is tied to a particular product. Neither approach can remove uncertainty when the food description or measurement basis is unknown.

Compare products for the decision you need to make

A Coles shopper comparing mince for a weekly plan has at least two separate questions: what nutrition does the product provide, and what will buying the pack cost? Protein per 100g helps with the first; it cannot answer the second by itself. Pack price, pack size, how much the recipe uses and what happens to the unused amount all affect grocery budgeting. Keep those measures separate so a protein comparison does not get mistaken for a value comparison.

• For a macro target: use the product’s panel when it describes the item you bought and its stated basis suits the amount you are tracking.
• For a recipe: account for the beef and other ingredients using one consistent recipe or ingredient approach.
• For grocery value: compare price and usable quantity as well as nutrition; protein per 100g is not a price measure.

These distinctions are useful when planning several meals from one pack. The pack can have one purchase cost, while each meal uses only part of its contents. Tracking the full pack cost against a single serving can overstate that meal’s cost; dividing it evenly without noting different portion sizes can also misrepresent how much each meal contains.

Turn a per-100g value into a portion estimate

Once you have a suitable protein value and a portion weight measured on the same basis, calculate: protein in portion = protein per 100g × portion weight ÷ 100. For a clearly hypothetical example, if a chosen food record listed 20g per 100g and your matching-basis portion weighed 150g, the calculation would be 20 × 150 ÷ 100 = 30g. This illustrates the arithmetic; it is not a claim that every 150g portion of beef contains 30g of protein.

For batch cooking, the main choice is whether your records follow the ingredients before cooking or portions after cooking. If you weigh raw ingredients, log those ingredients and divide the recipe according to the servings you make. If you weigh cooked portions, use a cooked-food value that resembles the result. Either approach can be useful for macro tracking; the value comes from using the same approach consistently and knowing what the recorded weight represents.

For example, a household that cooks one mince recipe for several lunches might portion the finished batch into containers of different sizes. Assigning every container the same protein amount would overlook the difference in portion size. Using the recipe total and allocating it in proportion to the portions—or weighing each portion and applying a suitable cooked reference—makes the meal record more meaningful. If the recipe has unevenly distributed ingredients, portioning it evenly before serving can improve the estimate.

When a figure is uncertain, keep the precision modest. A clearly labelled pack and a measured portion give you a better starting point than a generic match to an unknown cut. A database estimate can still be useful for meal planning, but its limitations belong with the number so you do not mistake an approximate entry for a laboratory measurement of your meal.

For Australian Coles shoppers balancing protein targets with grocery costs, the most useful record connects the food, its measured portion and the purchase without treating those as one number. Macronomics is designed to combine macro-target meal planning with Coles product pricing and whole-pack grocery cost estimates. If that approach fits your planning, explore Macronomics.

Authored with NotFair SEO