Feast Get Feast
Menu

Portions and preparation · USDA nutrition

Cucumber calories per cup: 19–83 across 2 of 3 named USDA examples

Across 2 of 3 named USDA examples, a cup contains 19–83 calories. Their listed weights span 120–185 g, so each calorie value is calculated from that example's own gram weight and published calories per 100 g. The remaining 1 specifically named example does not list that exact household measure.

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 93 g

42calories

Cucumber, cooked

Protein
0.7 g
Carbs
3.1 g
Fat
3 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 2709928 Full nutrition profile →

Compare all 3 food records, nutrition tables and USDA sources

The 3 exact records in this guide report 2–42 calories in the records' own listed source servings and 16–45 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 Cucumber, begin by separating “Cucumber, cooked” from “Cucumber, raw.” 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 3 linked records.

Equal-weight view

How cucumber records compare at 100 grams

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

  1. Cucumber, for use on a sandwich 16 kcal
    16 kcal
  2. Cucumber, raw 16 kcal
    16 kcal
  3. Cucumber, cooked 45 kcal
    45 kcal

Shared basis: 100 g · kilocalories

What this page compares

Named source records, not one universal meal

This guide keeps 3 named USDA records in view: 3 direct matches. They span 2 source categories, including Other vegetables and combinations and Vegetables on a sandwich. 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 description segment” placed these 3 records together under the exact grouping key “cucumber.” That rule determines membership before any nutrition result is read.

For Cucumber, this page can compare 3 named records from FDC 2709928 through FDC 2709784. 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

10–93 g before composition

The largest source amount is 9.3× the smallest. Read per-serving calorie differences with that mass gap in view.

Composition

29 kcal separates the fixed-weight endpoints

The lower endpoint is “for use on a sandwich”; the higher is “cooked.” This isolates density, not ingredient causation.

Discriminator

143 mg sodium gap per 100 g

Of protein, fiber, and sodium, the strongest normalized contrast is between “for use on a sandwich” (2 mg) and “cooked” (145 mg).

Observed source examples

Three landmarks inside this source set—not universal endpoints

The cards are ordered by calories in each record's listed serving. Serving weights differ, so use per-100-gram values to compare composition. These selected records do not define a calorie range for every cucumber.

Important: “Lower” begins with Cucumber, for use on a sandwich; “higher” ends with Cucumber, cooked, using each record’s own source amount. Those labels order this selected set only—they are not endpoints for every cucumber meal.

Full comparison

Compare every selected FNDDS record

For Cucumber, 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 Cucumber nutrition guide
Exact source record Match Source amount Calories kcal / 100 g Protein Fiber Sodium USDA
Cucumber, cooked Direct name match 93 gUSDA reference amount 42 kcal 45 0.7 g 0.6 g 135 mg FDC 2709928 ↗
Cucumber, for use on a sandwich Direct name match 10 gUSDA reference amount 2 kcal 16 0.1 g 0.1 g 0 mg FDC 2710249 ↗
Cucumber, raw Direct name match 60 gUSDA reference amount 10 kcal 16 0.4 g 0.3 g 1 mg FDC 2709784 ↗

Portion analysis

Serving total and calorie density answer different questions

The listed source amounts run from 10 to 93 grams—a 83-gram gap before composition enters the comparison. Their own source servings run from 2 calories for “for use on a sandwich” to 42 for “cooked.” At a fixed 100 grams, “for use on a sandwich” is 16 calories and “cooked” is 45—a fixed-weight separation of 29 calories. For Cucumber, 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 “cooked”, “for use on a sandwich”, and “raw”. The source formulations contain 4 distinct ingredient codes; examples that appear in only part of the set include cucumber, with peel, raw, cucumber, raw, oil or table fat, nfs, and salt, table. On this Cucumber 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 “Cucumber” cannot resolve the differences between Cucumber, cooked and Cucumber, raw. The four checks below identify the record wording, source weight, and formulation evidence that can.

  1. 01

    Source weight before serving calories

    The source amounts span 10–93 grams. Compare per 100 grams before reading a serving-calorie gap as a composition gap.

  2. 02

    The words that split the family

    Representative record-level distinctions include “cooked”, “for use on a sandwich”, and “raw”. Those phrases are evidence for choosing a record, not decorative subtitle text.

  3. 03

    Formulation evidence, with limits

    4 source-input codes appear across the selected records. Their presence and listed weights describe USDA formulations, not finished plated proportions.

  4. 04

    The unresolved plate

    Even “Cucumber, cooked” leaves the eaten grams and unnamed oils, sauces, toppings, substitutions, or leftovers unresolved. Preserve those Cucumber 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 cucumber is the right meal family. Then resolve the phrases that actually separate this set—“cooked”, “for use on a sandwich”, and “raw”—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 Cucumber 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 3 exact records behind Cucumber 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

Cucumber, cooked is higher in sodium per 100 g

Cucumber, cooked reports 145 mg versus 2 mg for Cucumber, for use on a sandwich: a 143 mg difference when both are normalized to 100 g.

Inspect the underlying evidence

Check the weight before comparing serving totals

Source amounts span 10–93 g

Cucumber, for use on a sandwich uses USDA source amount (10 g), while Cucumber, cooked uses USDA source amount (93 g). Use per 100 g for equal-weight composition; use the serving column only when those named source amounts answer your question.

Choose the record before reading the number

Cucumber, cooked and Cucumber, raw are not interchangeable

The page keeps both records at the same 100 g denominator and makes Preparation wording (No matching controlled term in the source name versus raw) 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 Cucumber 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 Cucumber, cooked vs Cucumber, raw

Both records appear in this page’s evidence set. The explicit record-description contrast is Preparation wording: No matching controlled term in the source name versus raw; it is a selection cue, not evidence of cause.

Follow this evidence path A formulation detail that separates records Cucumber, with peel, raw

USDA input 11205 appears in 2 of 3 context records; its summed listed input weight spans 100–100 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 1 of 3 context records; its summed listed input weight spans 3–3 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 Sodium: density and serving context

In this page’s records, sodium runs from 2 mg in Cucumber, for use on a sandwich to 145 mg in Cucumber, cooked, all per 100 g.

Follow this evidence path 2 context records in this source topic Other vegetables and combinations

Cucumber, cooked and Cucumber, raw 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 Put the observed spread in corpus context Calories: density and serving context

In this page’s records, calories runs from 16 kcal in Cucumber, for use on a sandwich to 45 kcal in Cucumber, cooked, all per 100 g.

Follow this evidence path 1 context record in this source topic Vegetables on a sandwich

Cucumber, for use on a sandwich belongs 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