Telegram RegisterThe public register of Telegram

Channel

勤劳的发片小熊

@zhy301301

On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

3,895subscribers

+98 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002139733779
TypeChannel
Username@zhy301301
Created14 May 2024measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/zhy301301

Growth

3,7973,8953,8467 August 2026 — 3,797 subscribers7 August 2026 — 3,797 subscribers7 August 2026 — 3,802 subscribers11 August 2026 — 3,848 subscribers14 August 2026 — 3,895 subscribers7 August 202614 August 2026
5 measurements spanning 7 days, net +98. 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 3,782–3,910 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 18:073,895+47
11 Aug 2026, 04:213,848+46
7 Aug 2026, 22:133,802+5
7 Aug 2026, 18:023,797no change
7 Aug 2026, 17:523,797first reading

Engagement

4 posts held, back to 14 May 2024the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 3 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
42.9%
avg views ÷ 3,895 subscribers
Avg views / post
1,670
1 post measured
Reaction rate
0.299%
reactions ÷ views · ER floor
Posts in window
1
of 4 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 31 July 2026
Posts held4 (14 May 202431 July 2026)
Views total1,670
Reactions total5
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 06:12 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

208 reactions across 3 posts, in 7 distinct kinds. The most used accounts for 75.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
15675.0%
👍3516.8%
😁94.33%
👏31.44%
🔥31.44%
🤓10.481%
🥰10.481%

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

Measured over the 4 most recent posts we hold, published 14 May 2024 to 31 July 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

31 Jul 2026, 16:19 UTC≈1,670 views5 reactionsread 8 August 2026

合集总结 点击这里 合集现在更新在这里👇 1. 涩涩不起来~ 2.一起涩涩吧 涩涩的秘密花园 频道可在下方进行投稿~ ✏️️️投稿点击此处 (欢迎投稿~) 《群主的工具箱》 点击👇链接 发送关键词搜索就行啦 💖【涩涩搜索】💖💝【涩涩找片】💝 🍉【涩涩吃瓜】🍉 ❤️爱心发电 支持一下群主的搜索群吧 都可以搜的到的😘 涩涩家族pikpak的资源箱 一定要关注防丢失频道呀 【防丢失频道】

2👍1🤓1🥰1

7 Feb 2025, 05:55 UTC≈43,200 views81 reactionsread 8 August 2026

❤️涩涩家族群组合集 合集总结 点击这里 🌹【涩涩不起来】 🌈【一起涩涩吧】 🖼【图片赏析】 🎀【PikPak】 🎀【美女鉴赏】 🍉【吃瓜群众】 🌼【秘密花园】 🐽【涩涩吃瓜】 💖【涩涩搜索】 💝【涩涩找片】 🍭点击此处一键关注 🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀

50👍18😁8🔥3👏2

7 Feb 2025, 05:55 UTC≈42,000 views122 reactionsread 8 August 2026

IOS苹果用户无法查看成人(色情)频道/群组 如果你进入某个频道/群组遇到如下提示: This channel can't displayed because it was used to spread pornographic content 原因:有人在频道/群组发布成人(色情)内容,被Telegram官方限制了。 解决方法: 登录官方Telegram Web网页版: https://web.telegram.org 打不开请登录旧版: https://web.telegram.org/?legacy=1 注意:必须复制到浏览器打开,验证码是优先发送到之前已登录的Telegram设备/客户端/APP上。如果你在Telegram直接打开链接,就无法看到Telegram上的验证码了。 ➊点击「Settings/设置」 ➋点击「Privacy and Security/隐私和安全」 ➌找到「Sensitive cont

104👍16👏1😁1

Showing the 4 most recent of 4 posts we hold for @zhy301301. 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.

Mentions

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.

“勤劳的发片小熊” (@zhy301301), 3,895 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/zhy301301.

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.