360 g source amount Direct name match
Tea, hot, chamomile
- Source serving
- 4 kcal
- Per 100 g
- 1 kcal
- Protein
- 0 g
Focused USDA meal guide
Tea, hot calories and nutrition: 9 USDA records compared
The 9 exact records in this guide report 0–184 calories in the records' own listed source servings and 0–51 calories per 100 grams. Those are observations from named database records—not a universal range or an estimate of an unseen plate.
Part of the Tea nutrition guide.
What this page compares
Named source records, not one universal meal
This page includes every selected Feast nutrition record whose normalized USDA description begins with “Tea, hot” under the documented two-segment variant rule. The records fall within Tea. 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
Start with the description closest to what you ate
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.
360 g source amount Direct name match
Tea, hot, herbal
- Source serving
- 4 kcal
- Per 100 g
- 1 kcal
- Protein
- 0 g
360 g source amount Direct name match
Tea, hot, hibiscus
- Source serving
- 0 kcal
- Per 100 g
- 0 kcal
- Protein
- 0 g
360 g source amount Direct name match
Tea, hot, leaf, black
- Source serving
- 4 kcal
- Per 100 g
- 1 kcal
- Protein
- 0 g
360 g source amount Direct name match
Tea, hot, leaf, black, decaffeinated
- Source serving
- 4 kcal
- Per 100 g
- 1 kcal
- Protein
- 0 g
360 g source amount Direct name match
Tea, hot, leaf, green
- Source serving
- 4 kcal
- Per 100 g
- 1 kcal
- Protein
- 0.8 g
360 g source amount Direct name match
Tea, hot, leaf, green, decaffeinated
- Source serving
- 0 kcal
- Per 100 g
- 0 kcal
- Protein
- 0 g
360 g source amount Direct name match
Tea, hot, leaf, oolong
- Source serving
- 4 kcal
- Per 100 g
- 1 kcal
- Protein
- 0 g
360 g source amount Direct name match
Tea, hot, with milk
- Source serving
- 184 kcal
- Per 100 g
- 51 kcal
- Protein
- 5.7 g
Observed source examples
Lower, middle, and higher within this selected set
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 tea, hot and should not be used as a personalized estimate.
Lower observed Direct name match
0kcal
Tea, hot, hibiscus
360 g source amount · 0 kcal per 100 g
Inspect this exact record Middle observed Direct name match
4kcal
Tea, hot, leaf, black
360 g source amount · 1 kcal per 100 g
Inspect this exact record Higher observed Direct name match
184kcal
Tea, hot, with milk
360 g source amount · 51 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
Compare every selected FNDDS record
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 |
|---|---|---|---|---|---|---|---|---|
| Tea, hot, chamomile | Direct name match | 360 gQuantity not specified | 4 kcal | 1 | 0 g | 0 g | 4 mg | FDC 2710505 ↗ |
| Tea, hot, herbal | Direct name match | 360 gQuantity not specified | 4 kcal | 1 | 0 g | 0 g | 4 mg | FDC 2710502 ↗ |
| Tea, hot, hibiscus | Direct name match | 360 gQuantity not specified | 0 kcal | 0 | 0 g | 0 g | 14 mg | FDC 2710503 ↗ |
| Tea, hot, leaf, black | Direct name match | 360 gQuantity not specified | 4 kcal | 1 | 0 g | 0 g | 11 mg | FDC 2710488 ↗ |
| Tea, hot, leaf, black, decaffeinated | Direct name match | 360 gQuantity not specified | 4 kcal | 1 | 0 g | 0 g | 11 mg | FDC 2710489 ↗ |
| Tea, hot, leaf, green | Direct name match | 360 gQuantity not specified | 4 kcal | 1 | 0.8 g | 0 g | 4 mg | FDC 2710490 ↗ |
| Tea, hot, leaf, green, decaffeinated | Direct name match | 360 gQuantity not specified | 0 kcal | 0 | 0 g | 0 g | 0 mg | FDC 2710491 ↗ |
| Tea, hot, leaf, oolong | Direct name match | 360 gQuantity not specified | 4 kcal | 1 | 0 g | 0 g | 11 mg | FDC 2710492 ↗ |
| Tea, hot, with milk | Direct name match | 360 gQuantity not specified | 184 kcal | 51 | 5.7 g | 0.4 g | 72 mg | FDC 2710506 ↗ |
Portion analysis
Serving total and calorie density answer different questions
Every record uses a 360-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 0–184 calories in the records' own listed source servings; the fixed-weight view reports 0–51 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 dish name leaves ingredients unresolved
The record names distinguish leaf, chamomile, herbal, hibiscus, and with milk. USDA formulation rows also identify 12 distinct source-input codes across the set, including beverages, tea, black, brewed, prepared with tap water, beverages, tea, black, brewed, prepared with tap water, decaffeinated, beverages, tea, green, brewed, decaffeinated, and beverages, tea, green, brewed, regular. 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
Four drivers worth checking before choosing a record
The visible dish name is a starting point. These details usually explain more of the variation in the selected source records.
- 01
Source-serving weight
The exact records list 360–360 grams, so serving totals can move even before composition is compared.
- 02
Named source variant
The set explicitly distinguishes leaf, chamomile, herbal, hibiscus, and with milk; those words identify different records rather than optional SEO phrasing.
- 03
Nutrient profile
Across each record's own source serving, the displayed data span protein 0.0–5.7 g, fiber 0.0–0.4 g, sodium 0–72 mg. Different serving weights remain visible beside those values.
- 04
Formulation evidence
The source rows include 12 distinct input codes across this set. Input presence and weight describe standardized source formulations, not final plated proportions.
Record matching
How to find the closest description
Begin with the full source description rather than the shortest dish name. Check whether the named form—such as leaf, chamomile, herbal, hibiscus, and with milk—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.
A practical matching checklist
- Read the complete tea, hot source description, including preparation and additions.
- Compare the listed source weight with the amount actually eaten.
- Prefer a current package or restaurant source when a specific branded item is known.
- Record toppings, sauces, cooking fat, sides, and substitutions that the selected description does not name.