cock a leekie

Name: cock a leekie
Brand: Baxters

Baxters

5012427142404

Processing

Ultra-processed

Group 4 of 4 on the NOVA scale

Additives listed

None we have assessed

Counted from the label, not by quantity

Salt per 100g

0.65g

Medium

UK FSA front of pack threshold

Three separate readings, kept apart on purpose. This is not a score, and none of it says this product is harmful.

Additives

No additives listed in the source data for this product. That can mean it genuinely has none, or that the entry is incomplete. The pack itself is the authority.

Ingredients

Water, Leeks (11%), Cooked Rice (9%) (Water, Rice), Cornflour, Carrot, Chicken (2%), Flavouring, Chicken Fat, Roast Chicken Stock Paste (Water, Roast Chicken Stock, Yeast Extract, Sugar, Cornflour, Tomato Purée, Vegetable Juice Concentrates [Carrot, Leek]), Onions, Sugar, Yeast Extract, Salt, Sea Salt, Spices.

As printed on the pack, in the producer's own order: ingredients are listed by weight, so what comes first is most of what is in it. E numbers link to their assessment where we have one.

Processing level

NOVA group 4: Ultra-processed

Industrial formulations with additives, isolates and ingredients you would not cook with at home. The strongest modern evidence links high intake of these to poorer health outcomes.

Nutrients per 100g

Fat

Low

Saturates

0.30g

Low

Sugars

0.80g

Low

Salt

0.65g

Medium

Judged on the UK FSA front of pack thresholds for solid foods. A dash means the source has no figure, which is not the same as a low one.

Other packs of this product

Open Food Facts keeps a record for every barcode, so one product can appear several times. Each of these carries its own data, and may be fuller or thinner than this one.

Cock A Leekie
5012427676107 no processing data

Where this came from

Product data from Open Food Facts, which is crowd sourced and can be incomplete or out of date. Photograph from the same source, under the Creative Commons Attribution ShareAlike licence. Open Food Facts last changed this record on 27 March 2026, and our copy is from 20 August 2026. The source is checked every night, and a product is rewritten here only when its record there changes. Something wrong? Correcting it at the source fixes it here and everywhere else that uses the same data. If the problem is one of our additive assessments, tell us.

Scan another barcode Search