Telegram RegisterThe public register of Telegram

Channel

糖果

@qqppcb

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

305subscribers

+18 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004253714884
TypeChannel
Username@qqppcb
CreatedBetween 1 May 2026 and 1 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/qqppcb

Growth

2873052966 August 2026 — 287 subscribers6 August 2026 — 287 subscribers7 August 2026 — 292 subscribers14 August 2026 — 305 subscribers6 August 202614 August 2026
4 measurements spanning 8 days, net +18. 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 284–308 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 18:49305+13
7 Aug 2026, 09:57292+5
6 Aug 2026, 23:03287no change
6 Aug 2026, 20:48287first reading

Engagement

19 posts held, back to 1 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
155.6%
avg views ÷ 305 subscribers
Avg views / post
475
7 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
7
of 19 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
WindowRolling 30 days · latest post in window 6 August 2026
Posts held19 (1 July 20266 August 2026)
Views total3,322
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 23:03 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

19 reactions across 5 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
19100.0%

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 5 of the 19 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 19reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 1 July 2026 to 6 August 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

5 Aug 2026, 14:41 UTC170 viewsread 6 August 2026

#杭州肯德基 https://t.me/kdjqjt #好评 91 【出击时间】:8.4 【出击老师】:#糖果 【联系方式】:@apc136 【出击留名】:肯德基不加基 【开课位置】:拱墅 【修车水费】:10p 【人照评分满分10】:8(本人比照片好看) 【颜值评分满分20】:18(高颜值) 【身材评分满分10】:8(皮肤黄白皮/身材很不错/罩杯B)9 【吊感评分满分20】:18(户型蝴蝶/紧度很紧/水量很多一碰就湿/包裹感老虎钳一样) 【服务评分满分10】:10(女友感) 【态度评分满分20】:20(主动询问/) 【环境评分满分10】:10(小区) 【综合评分满分100】:91(以上相加) 情绪价值描述: 【过程描述】:有的打✅ 舌吻 ✅ 口活 ✅ 69舔穴 有 毒龙 【过程描述】:群里上新一个妹妹,听说很紧,果断约课,到达课室,开门一看,卧草,人比照片漂亮,有点呆萌的感觉,进门点烟付水费,聊了一会,妹妹刚

31 Jul 2026, 05:59 UTC608 viewsread 6 August 2026

⭐新人嫩妹糖果⭐美美的来【集美师范大学】当老师啦! 🪄发现美、集中美、传播美🪄

15 Jul 2026, 16:11 UTC≈1,090 views2 reactionsread 6 August 2026
Forwarded from @xdrj002Photo

🚩敏感&清纯&反差&好玩——#糖果 🌟🌟🌟🌟🌟 传送门:@apc136 位置:#杭州 #上城区 水费:1000 颜值:人照9分 硬件:白瘦幼、皮肤嫩、三点粉,🐻B,小处纹身,身体是亮点,跳跳虾,敏感点巨多 屌感:进入阻尼感超强,水量足 情绪价值:青春感青涩感难得,过程中看的出来努力想做好细节 ———————————————— Age :07. Height :162. Weight :42. Bust :B Tips: “你怎么不喊停?” 台风警报刚刚解除,之前和糖果聊天得知妹妹刚来杭州下海,客人不多,还确认了自聊,勾起了我尝鲜素人的兴趣。 小区科室,见面老师一身朴素的运动装,只有胸部的曲线隐隐若现,人照一致,画了美美的妆微笑相迎。简单沟通的过程中看出来妹子很紧张,细心的给我准备拖鞋、一次性浴巾和牙刷,共浴时妹身材属于细枝小硕果,🐻型挺乳晕小没有发育开,微微内陷。腹部没有一丝赘肉,皮肤也没有疤痕

2

15 Jul 2026, 16:10 UTC986 viewsread 6 August 2026
Forwarded from @HZMTBG

杭州美团报告模板 https://t.me/HZMTLYQ 【综合评价】:#超级好评 【验证留名】:@h27dylanys 【验证时间】:2026-07-15 【妹子艺名】:#糖果 【联系方式】:@apc136 【报告类型】:原价 【上课花费】:1000 【包含服务】:舌吻 ✅ | 69 ✅ | 情绪价值 ✅ | 花样服务 ❌ 【人照相似】:9分 【身材评分】:10分 【颜值评分】:9分 【紧度评分】:10分 【态度/服务评分】:9分 【环境卫生评分】:9分 【综合评分】:9.33 【流程小文】: 糖果老师看了照片就觉得清纯有气质,一眼相中果断约了。来到小区门口停好车,直接上楼,老师留了门。进屋第一眼非常满意,人比照片还甜,1米6白瘦幼S身材,大长腿,皮肤特别嫩,气质干净青涩,说话声音软软的。 付完水费直接进入主题,老师放水一起洗澡。全身沐浴露滑滑的,我主动和老师摩擦起来,随后抓住我的jj温柔清洗很快就硬了,小眼神水汪

Showing the 12 most recent of 19 posts we hold for @qqppcb. 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.

Citation-graph rank

Citation-graph rank — 1,209,231 of 1,478,351entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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 1 registered channel — 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.

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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“糖果” (@qqppcb), 305 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/qqppcb.

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.