The official channel of the Cherrygram.
Support and discussion: @CherrygramSupport
APKs: @CherrygramAPKs
Beta APKs: @CherrygramBetaAPKs
List of features and the source code: https://github.com/arsLan4k1390/Cherrygram#readme
Created
Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
Technology — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 89% 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
69 measurements spanning 51 days, net +628. 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 40,739–41,587 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 69
Measured (UTC)
Subscribers
Change
26 Sept 2026, 10:15
41,467
-22
25 Sept 2026, 02:59
41,489
+61
19 Sept 2026, 12:00
41,428
+12
18 Sept 2026, 18:40
41,416
+28
17 Sept 2026, 03:21
41,388
+12
16 Sept 2026, 10:58
41,376
+36
15 Sept 2026, 06:58
41,340
+8
14 Sept 2026, 16:20
41,332
+19
13 Sept 2026, 13:15
41,313
+14
13 Sept 2026, 00:17
41,299
+46
11 Sept 2026, 19:58
41,253
+1
11 Sept 2026, 02:39
41,252
+8
9 Sept 2026, 07:18
41,244
+14
8 Sept 2026, 03:40
41,230
-7
6 Sept 2026, 02:00
41,237
+20
5 Sept 2026, 00:37
41,217
+21
3 Sept 2026, 19:57
41,196
+2
3 Sept 2026, 10:03
41,194
no change
2 Sept 2026, 08:35
41,194
-4
2 Sept 2026, 04:55
41,198
first reading
Engagement
24 posts held, back to 24 March 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 97 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
45.6%
avg views ÷ 41,467 subscribers
Avg views / post
18,900
3 posts measured
Reaction rate
1.25%
reactions ÷ views · ER floor
Posts in window
3
of 24 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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 7 September 2026
Posts held
24 (24 March 2026 – 7 September 2026)
Views total
56,700
Reactions total
706
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
27 Sept 2026, 04:34 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.
What this channel posts
Photos
126
Videos
6
Links
117
Lifetime counters from Telegram’s own channel header, read 27 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Reaction mix
3,762 reactions across 24 posts, in 34 distinct kinds. The most used accounts for 45.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
1,695
45.1%
👍
420
11.2%
😁
371
9.86%
🥰
297
7.89%
🔥
229
6.09%
🤔
134
3.56%
🤯
122
3.24%
🐳
85
2.26%
❤🔥
78
2.07%
👏
44
1.17%
🌭
41
1.09%
☃
32
0.851%
😎
21
0.558%
💘
20
0.532%
🌚
18
0.478%
💅
17
0.452%
✍
16
0.425%
👾
15
0.399%
💯
15
0.399%
💋
14
0.372%
14 further kinds
78
2.07%
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 24 of the 24 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 3,762 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 24 most recent posts we hold, published 24 March 2026 to 7 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.
Telegram Stars
Stars received
15
across the posts below
Posts paid on
9
of 24 we hold a reading for · 38%
Most on one post
4
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @cherrygram. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 24 most recent posts we hold for this entry, published 24 March 2026 to 7 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Cherrygram is open source once again.
There was a time when I made the source code private. The reason was simple and frustrating: people were shamelessly copying the code, claiming it as their own, and profiting off it. Emotions got the better of me, so I pulled the development behind closed doors.
But keeping the code hidden goes against the core spirit of building great products. Open source means rapid developm…
Hey everyone!
You asked for it — I finally made it. The new iOS-style message input field is now available for testing.
Beta APK: https://t.me/CherrygramBetaAPKs/2565
Note: it will only install if you’re using Cherrygram outside of the Play Store.
You can enable the feature in tg://cg_chats.
More screenshots: https://t.me/CherrygramBetaAPKs/2556
If you find any bugs or weird behavior, please report them in the …
⭐ Reminder: Cherrygram still lets you buy Telegram Stars with no KYC, no limits, and full multichain support.
The service was temporarily unavailable for about a week, but it’s fully up and running again in the latest Cherrygram update! 💫
How to access:
⚙️ Settings → My Stars → Top Up/Buy more Stars → Buy Stars (Multi-chain & No KYC). Direct link: tg://cg_stars
🍒☀️🍒☀️🍒☀️🍒
⭐ Напоминаем: в Cherrygram всё еще доступн…
Verified Google Play Developer ✅
https://android-developers.googleblog.com/2025/08/elevating-android-security.html
❤175☃32🔥18👍13🤔8🌚4🐳4💘4
Showing the 12 most recent of 24 posts we hold for @cherrygram. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Posts edited after publishing
@cherrygram edited 1 post 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
14 August 2026
Most recent edit
14 August 2026
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 38 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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 26 September 2026 — this
entry's latest reading, not the date you are reading this.
“Cherrygram 🍒” (@cherrygram), 41,467 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/cherrygram.
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.
