Telegram RegisterThe public register of Telegram
Telegram profile photo for Grocery Loot Deals

Channel

Grocery Loot Deals

@grocery_loot_deal

On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Cite this entry

11,521subscribers

-143 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001609906042
TypeChannel
Username@grocery_loot_deal
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live18 September 2026
Measurements held31
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/grocery_loot_deal

Topic

Ecommerce storefront — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 99% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

11,52111,67611,598.57 August 2026 — 11,664 subscribers7 August 2026 — 11,664 subscribers8 August 2026 — 11,673 subscribers9 August 2026 — 11,676 subscribers10 August 2026 — 11,668 subscribers11 August 2026 — 11,671 subscribers12 August 2026 — 11,669 subscribers15 August 2026 — 11,666 subscribers16 August 2026 — 11,652 subscribers17 August 2026 — 11,643 subscribers18 August 2026 — 11,638 subscribers19 August 2026 — 11,633 subscribers20 August 2026 — 11,628 subscribers22 August 2026 — 11,625 subscribers23 August 2026 — 11,620 subscribers25 August 2026 — 11,618 subscribers26 August 2026 — 11,621 subscribers27 August 2026 — 11,615 subscribers28 August 2026 — 11,610 subscribers29 August 2026 — 11,604 subscribers30 August 2026 — 11,595 subscribers1 September 2026 — 11,596 subscribers2 September 2026 — 11,590 subscribers3 September 2026 — 11,584 subscribers4 September 2026 — 11,587 subscribers7 September 2026 — 11,565 subscribers10 September 2026 — 11,545 subscribers12 September 2026 — 11,535 subscribers14 September 2026 — 11,533 subscribers15 September 2026 — 11,530 subscribers18 September 2026 — 11,521 subscribers7 August 202618 September 2026
31 measurements spanning 42 days, net -143. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 11,498–11,699 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 31
Measured (UTC)SubscribersChange
18 Sept 2026, 06:2111,521-9
15 Sept 2026, 22:1711,530-3
14 Sept 2026, 07:2211,533-2
12 Sept 2026, 18:5611,535-10
10 Sept 2026, 16:3811,545-20
7 Sept 2026, 13:1711,565-22
4 Sept 2026, 14:1511,587+3
3 Sept 2026, 02:3711,584-6
2 Sept 2026, 03:3211,590-6
1 Sept 2026, 05:0811,596+1
30 Aug 2026, 05:0411,595-9
29 Aug 2026, 01:4811,604-6
28 Aug 2026, 03:2511,610-5
27 Aug 2026, 00:3511,615-6
26 Aug 2026, 00:4811,621+3
25 Aug 2026, 03:2811,618-2
23 Aug 2026, 23:2511,620-5
22 Aug 2026, 07:5911,625-3
20 Aug 2026, 23:0611,628-5
19 Aug 2026, 19:5211,633first reading

Engagement

447 posts held, back to 7 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 53 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
2.94%
avg views ÷ 11,521 subscribers
Avg views / post
338
96 posts measured
Reaction rate
0.295%
reactions ÷ views · ER floor
Posts in window
96
of 447 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 8 of 96 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 September 2026
Posts held447 (7 August 2026 – 3 September 2026)
Views total32,482
Reactions total12
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 01:32 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

13 reactions across 9 posts, in 3 distinct kinds. The most used accounts for 69.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤‍🔥969.2%
😱215.4%
🤯215.4%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 10 of the 447 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 13 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 447 most recent posts we hold, published 7 August 2026 to 3 September 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

3 Sept 2026, 01:31 UTC5 viewsread 3 September 2026

Vega Bolt Bunny Helmet at 1311 L : https://amzn.to/4x0uswB L : https://amzn.to/462Syf8

2 Sept 2026, 19:15 UTC69 viewsread 3 September 2026

Jaldi 💥 ₹96 (final) | Regular: 299 - Apply 50% coupon https://amzn.to/3UScuPe Edit : Over ❌

2 Sept 2026, 18:48 UTC129 viewsread 3 September 2026

₹192 | Regular: 599 https://amzn.to/4iJe9R2 Edit : Over ❌

2 Sept 2026, 17:42 UTC184 viewsread 3 September 2026

Jaldi 💥 ₹209 | Regular: 344 https://amzn.to/4qQWgSl Edit : Over ❌

2 Sept 2026, 17:15 UTC211 viewsread 3 September 2026

₹85 (final) - Apply 50% coupon https://amzn.to/4xyOMWG Edit : Over ❌

Showing the 12 most recent of 447 posts we hold for @grocery_loot_deal. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Posts edited after publishing

@grocery_loot_deal edited 12 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
18 August 2026
Most recent edit
31 August 2026

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 18 September 2026 — this entry's latest reading, not the date you are reading this.

“Grocery Loot Deals” (@grocery_loot_deal), 11,521 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/grocery_loot_deal.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.