24小时在线接扫码 隔夜也在👍

Channel
大大怪假粉通知
@chenbo67
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,437subscribers
+381 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002583101037 |
|---|---|
| Type | Channel |
| Username | @chenbo67 |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 5 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 5 October 2026 |
| On Telegram | t.me/chenbo67 |
Topic
Other / unclassifiable — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 62% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Oct 2026, 18:56 | 1,437 | +69 |
| 28 Sept 2026, 10:00 | 1,368 | +91 |
| 18 Sept 2026, 18:01 | 1,277 | +43 |
| 14 Sept 2026, 01:39 | 1,234 | +30 |
| 10 Sept 2026, 15:37 | 1,204 | +46 |
| 5 Sept 2026, 18:00 | 1,158 | +35 |
| 2 Sept 2026, 01:06 | 1,123 | +30 |
| 30 Aug 2026, 06:08 | 1,093 | +15 |
| 27 Aug 2026, 12:05 | 1,078 | +5 |
| 24 Aug 2026, 15:26 | 1,073 | +28 |
| 21 Aug 2026, 01:38 | 1,045 | -1 |
| 17 Aug 2026, 17:26 | 1,046 | +4 |
| 14 Aug 2026, 19:49 | 1,042 | -13 |
| 11 Aug 2026, 10:55 | 1,055 | -2 |
| 8 Aug 2026, 13:11 | 1,057 | +1 |
| 8 Aug 2026, 00:18 | 1,056 | no change |
| 7 Aug 2026, 18:56 | 1,056 | first reading |
Engagement
19 posts held, back to 7 January 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 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 19 posts for this entry, the most recent from 27 July 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
4 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 50.0% | |
| 👎 | 2 | 50.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 4 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 4 reactions 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 7 January 2026 to 27 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
跑路跑路 多注意 还有个id @yyy111145
❤1
找大大怪上粉补量 三网可控 安卓苹果比例可控 什么扫码都能接👍 全真人真机进 可留活码IP 全网 无黑料无跑路记录 @cbjfw
扫码界的神,抖音,QQ,微信,浏览器,微博,快手全系列扫码,全国真人真机,拒绝垃圾协议云机 @cbjfw
👎2
主攻上粉扫码 微信扫码1.5💰 QQ扫码1.8💰 浏览器2💰 抖音2.5💰 有验证码的全部加1 Q群上人1.5💰 真人真机 全程自带防爆上粉 只接先款 预付 能接受在聊🥰
日出万粉 全真人真机🥥
🥥要假粉的来找我,品质稳得一批,靠谱得很🥰👍
上粉无忧💓🥰 三网可控|安卓苹果比例可控 多次扫码|真人真机全程操作 0协议无脚本 真实优质流量,长效机制 全程0协议 0重复日出万粉 全程真人真机扫码😀
防爆 活码 防洪系统出售 @cbjfw
同行注意 跑路 @haonan123888
上班上班 上粉自带IP 通过率拉满🥰🥥🥥🥥 @cbjfw
防爆码代做,补量上粉,全包不过不要钱开工开工
Showing the 12 most recent of 19 posts we hold for @chenbo67. 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
Names
Channels on the register whose handles appear in this channel's posts.
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 5 October 2026 — this entry's latest reading, not the date you are reading this.
“大大怪假粉通知” (@chenbo67), 1,437 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/chenbo67.
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.