Lime juice, 100%, canned or bottled
- Source serving
- 2 kcal
- Per 100 g
- 21 kcal
- Protein
- 0 g
USDA record comparison
The 2 exact records in this guide report 2–2 calories in the records' own listed source servings and 21–25 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 “Lime juice” under the documented one-segment family rule. The records fall within Mustard and other condiments. 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 2 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 lime juice 100 and should not be used as a personalized estimate.
2kcal
8 g source amount · 21 kcal per 100 g
Inspect this exact record2kcal
8 g source amount · 25 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 |
|---|---|---|---|---|---|---|---|---|
| Lime juice, 100%, canned or bottled | Direct name match | 8 gQuantity not specified | 2 kcal | 21 | 0 g | 0 g | 1 mg | FDC 2709185 ↗ |
| Lime juice, 100%, freshly squeezed | Direct name match | 8 gQuantity not specified | 2 kcal | 25 | 0 g | 0 g | 0 mg | FDC 2709184 ↗ |
Portion analysis
Every record uses a 8-gram source amount, which removes serving-weight differences inside this set but does not establish the size of your portion. Within the selected set, the source servings report 2–2 calories in the records' own listed source servings; the fixed-weight view reports 21–25 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 100%. USDA formulation rows also identify 2 distinct source-input codes across the set, including lime juice, canned or bottled, unsweetened and lime juice, raw. 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 8–8 grams, so serving totals can move even before composition is compared.
The set explicitly distinguishes 100%; those words identify different records rather than optional SEO phrasing.
Across each record's own source serving, the displayed data span protein 0.0–0.0 g, fiber 0.0–0.0 g, sodium 0–1 mg. Different serving weights remain visible beside those values.
The source rows include 2 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 100%—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.