Telegram RegisterThe public register of Telegram
Telegram profile photo for 贝贝的公开福利频道

Channel

贝贝的公开福利频道

@beibei0987

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

1,949subscribers

+24 since we began measuring on 27 August 2026

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

Register entry

Telegram ID-1002325222280
TypeChannel
Username@beibei0987
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded27 August 2026
Last confirmed live3 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 3 September 2026
On Telegramt.me/beibei0987

Growth

1,9251,9491,93727 August 2026 — 1,925 subscribers28 August 2026 — 1,933 subscribers31 August 2026 — 1,937 subscribers3 September 2026 — 1,949 subscribers27 August 20263 September 2026
4 measurements spanning 7 days, net +24. 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 1,921–1,953 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Sept 2026, 19:171,949+12
31 Aug 2026, 11:161,937+4
28 Aug 2026, 01:421,933+8
27 Aug 2026, 09:151,925first reading

Engagement

20 posts held, back to 30 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
30.3%
avg views ÷ 1,949 subscribers
Avg views / post
590
5 posts measured
Reaction rate
0.166%
reactions ÷ views · ER floor
Posts in window
6
of 20 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 2 of 5 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 27 August 2026
Posts held20 (30 July 202627 August 2026)
Views total2,949
Reactions total3
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Aug 2026, 09:15 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

7 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 85.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
685.7%
👍114.3%

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

Measured over the 20 most recent posts we hold, published 30 July 2026 to 27 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

27 Aug 2026, 06:15 UTC70 viewsread 27 August 2026

深圳出击风向(繁花)群 验证榜单:@fanhuax 群组:https://t.me/+M2PRHBINX_hjMGMx 优质老师,真实狼友邀请制,与你分享真实的出击见闻

27 Aug 2026, 06:12 UTC77 viewsread 27 August 2026
Photo

🎰 宝安贝贝半价 📮 参与条件: 🎫 加入-深圳修车军团【轮播群】 🎫 加入-深圳修车军团【验证榜单】 🎫 加入-深圳修车军团【修车报告】 🎫 加入-深圳修车军团【免费上榜】 🎫 加入-贝贝的公开福利频道 🎁 奖品内容: 💰️ P半价优惠券 × 1 ⚠️ 抽奖说明: 三天后开奖 需要填写出击报告 半价有效期5天 中奖者请尽快兑奖 🔋 人品加成:⚡️× 9 规则 📅 开奖日期:(北京时间) 2026年08月30日 12时11分00秒

14 Aug 2026, 08:50 UTCviews —

贝贝的公开福利频道 pinned «个人私密频道,哥哥可以去看咯⬇️。 https://t.me/+YMAJWT0bBoIwOWU1»

14 Aug 2026, 08:50 UTC719 views1 reactionsread 27 August 2026

个人私密频道,哥哥可以去看咯⬇️。 https://t.me/+YMAJWT0bBoIwOWU1

1

9 Aug 2026, 07:43 UTC≈1,090 views2 reactionsread 27 August 2026
Photo

🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H178594435148 🎰 深圳西乡贝贝半价出击优惠卷 ⚠️ 抽奖说明: 优惠卷有效期为7天、预约可延期 兑奖联系:@beibei06789 (需要提供出击报告:@duobaopuis) 💁 参与情况:65达标 / 100报名 🎅 联系领奖:多情(起群拉人引流/... 1. 文化 大学生 奖品:p半价优惠卷 祝大家心想事成好运连连!

2

8 Aug 2026, 08:35 UTC993 viewsread 27 August 2026
Photo

🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H178594397875 🎰 宝安贝贝 @beibei06789 半价优惠券 ⚠️ 抽奖说明: 1:中奖者24小时内私聊老师兑奖; 2:开奖3天内没有兑奖的,则过期无效; 3:兑奖需要出击完提交详细报告:@Szqiaojiarenbg_bot 4:不去私聊管理 @bingmeishijiabing 回收 💁 参与情况:11达标 / 15报名 🔋 人品加成:9票 ⚡️× 9 🎅 联系领奖:@beibei06789 1. ❤️飞 羽(糖果)❤️⚡️× 9 奖品:宝安贝贝 @beibei06789 半价优惠券 限p 祝大家心想事成好运连连!

5 Aug 2026, 15:44 UTC≈1,170 views0 reactionsread 27 August 2026
Photo

🎰 深圳西乡贝贝半价出击优惠卷 📮 参与条件: 🎫 加入-贝贝的公开福利频道 🎫 加入-深圳快乐屋(约课认准轮播和榜单) └ 🎟️ 发言数大于 3 条 🎁 奖品内容: 💰️ p半价优惠卷 × 1 ⚠️ 抽奖说明: 优惠卷有效期为7天、预约可延期 兑奖联系:@beibei06789 (需要提供出击报告:@duobaopuis) 📅 开奖日期:(北京时间) 2026年08月09日 15时43分00秒

5 Aug 2026, 15:35 UTC≈1,120 viewsread 27 August 2026
Photo

🎰 宝安贝贝 @beibei06789 半价优惠券 📮 参与条件: 🌏️ 归属地 广东 🪪 必须设置用户名 🎫 加入-深圳·乱世俏佳人(备用群) 🎫 加入-深圳·乱世俏佳人 └ 🎟️ 发言数大于 66 条 🎫 加入-贝贝的公开福利频道 🎁 奖品内容: 💰️ 宝安贝贝 @beibei06789 半价优惠券 限p × 1 ⚠️ 抽奖说明: 1:中奖者24小时内私聊老师兑奖; 2:开奖3天内没有兑奖的,则过期无效; 3:兑奖需要出击完提交详细报告:@Szqiaojiarenbg_bot 4:不去私聊管理 @bingmeishijiabing 回收 🔋 人品加成:⚡️× 9 规则 📅 开奖日期:(北京时间) 2026年08月08日 16时35分00秒

5 Aug 2026, 15:30 UTCviews —

贝贝的公开福利频道 pinned «个人私密频道,哥哥可以去看咯⬇️。 https://t.me/+YMAJWT0bBoIwOWU1»

5 Aug 2026, 15:30 UTC≈1,020 viewsread 27 August 2026

个人私密频道,哥哥可以去看咯⬇️。 https://t.me/+YMAJWT0bBoIwOWU1

5 Aug 2026, 05:33 UTC≈1,070 views2 reactionsread 27 August 2026

#宝安贝贝 8月5日荣登深圳学院名师榜👑 ❤️名师榜: @sz520 ❤️聊天群: @sz1314 👩‍🎓郑重承诺: 高质量/真老师/真学生/活跃社区,若您在【深圳学院】联系的老师货不对板,被骗定金,群主: @sz333 担保赔付!每月赞助万元出击费🧧 立即加入 👆

1👍1

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

Named by 3 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.

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

“贝贝的公开福利频道” (@beibei0987), 1,949 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/beibei0987.

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.