需要消金历史库洗客户的快快来,特别优惠
😁1

Channel
@Baiheshuj
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,916subscribers
-4,501 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003534751658 |
|---|---|
| Type | Channel |
| Username | @Baiheshuj |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 5 September 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/Baiheshuj |
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 17 September 2026 and assigned it the closest of 31 fixed categories, at 46% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 13:57 | 1,916 | +201 |
| 13 Sept 2026, 14:00 | 1,715 | -1,000 |
| 10 Sept 2026, 03:17 | 2,715 | -118 |
| 5 Sept 2026, 20:22 | 2,833 | no change |
| 5 Sept 2026, 07:15 | 2,833 | -265 |
| 1 Sept 2026, 06:47 | 3,098 | -209 |
| 29 Aug 2026, 14:17 | 3,307 | -386 |
| 26 Aug 2026, 12:04 | 3,693 | -4 |
| 23 Aug 2026, 14:14 | 3,697 | -412 |
| 19 Aug 2026, 23:43 | 4,109 | -517 |
| 16 Aug 2026, 16:26 | 4,626 | -637 |
| 12 Aug 2026, 20:16 | 5,263 | -525 |
| 10 Aug 2026, 02:31 | 5,788 | -613 |
| 7 Aug 2026, 04:52 | 6,401 | -16 |
| 6 Aug 2026, 19:31 | 6,417 | first reading |
18 posts held, back to 14 August 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.
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 13 of 17 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 5 September 2026 |
|---|---|
| Posts held | 18 (14 August 2026 – 5 September 2026) |
| Views total | 11,470 |
| Reactions total | 18 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 5 Sept 2026, 20:22 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.
18 reactions across 13 posts, in 8 distinct kinds. The most used accounts for 22.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4 | 22.2% | |
| 👍 | 3 | 16.7% | |
| 👏 | 3 | 16.7% | |
| 👎 | 2 | 11.1% | |
| 🔥 | 2 | 11.1% | |
| 😁 | 2 | 11.1% | |
| ❤🔥 | 1 | 5.56% | |
| 🍾 | 1 | 5.56% |
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 13 of the 18 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 18 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 14 August 2026 to 5 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.
需要消金历史库洗客户的快快来,特别优惠
😁1
周天开工的中介大哥,大姐,代理们,速来报单🍾🍾
👎1
来自速搜推荐 @SSOU 📢包养伴游 全国伴游 金主... 📢全国上门服务【真实靠谱】 📢成都~高端外围(精选) 📢欧博官网|欧博代理|欧博... 📢❥电子女友🔞 📢女神热舞|直播录屏 📢动漫电影|AI剧场 📢电报吃瓜#色情版 📢PornWhite清爽视... 📢马尼拉修车 帕塞修车 玛... 📢3D Porn Dude... 📢皇冠足球 欧博代理 欧博... 📢亚星代理 欧博代理 亚星... 📢欧博百家乐|亚星百家乐|... 📢功夫|硬核解析|另类解读 👉流量互推规则介绍💥 以下是广告推荐 📢东南亚今日头条|新闻|爆料|悬赏|通缉|吃瓜缅甸妙瓦底大揭 📢 X-panel 一站式拉人增粉平台 📢🔥最强平台强势来袭,掀起智能合约新风暴! 🔥 📢 TGFind🚀Telegram最高效的搜索平台! 📢💹567U时代火爆上线!招收玩家/代理,匿名开户,放心娱乐! 🇨🇳 简体中文包 —————————-- 🔥将 @TonGroup…
Signed 速搜流量助手
需要白名单撞的联系,广东省 广西省 海南省,中介反馈撞出来非常好打,有能力的基本可以做到隔天约上门🍾 量大特别优惠
来自速搜推荐 @SSOU 📢南昌修车(精选资源) 📢🎀杏吧||抖阴|麻豆|... 📢青岛/外围兼职精选 📢郑州性感小野猫 📢情侣夫妻原档 自拍 📢抖音 快手走光网红主播 ... 📢功夫|硬核解析|另类解读 📢(欧美|无码|高清) 📢线上百家乐 真人百家乐 ... 📢菲律宾 马尼拉 后花园�... 📢【老毛】贷款实时数据|D... 📢TG超级高速代理/免费代... 📢国模行色私拍素人写真 📢偷拍学生清纯素人中出探花 📢勾引少妇|做爱视频 👉流量互推规则介绍💥 以下是广告推荐 📢 TeleTop 中文索引 📢 全网最全面、最便宜的自助引流服务 🥇西湖娱乐城✅老品牌包出款✅出款超10亿U 📢💎 【8.cc】U投领导者 千万域名 百亿大盘 充值笔笔加赠3% 📢 Ton 中文索引 🇨🇳 简体中文包 —————————-- 🔥将 @TonGroupHelpBot 设置为频道管理员,即可在2000+频道进行互推曝光,实现订阅快速增长。
Signed 速搜流量助手
银行混合申请,好加微信,通过率高,价格便宜,实时出
❤1🔥1
DPI SDK 信息流 消金 网贷 银行 公积金 隔夜公积金 隔夜征信 混合申请被拒 有单的早点报一下 🍾
❤1
DPI SDK 信息流 消金 网贷 银行 公积金 隔夜公积金 隔夜征信 混合申请被拒 贷后内鬼 有单的早点报一下 支持 微信🤣 支付宝🤣 U😀
👏1
助贷产品强势回归, 征信 工行进件 隔夜公积金 有单的早点报一下 实时拆解 支持 微信🤣 支付宝🤣 U😀
👍1
DPI SDK 信息流 消金 网贷 银行 公积金 隔夜公积金 隔夜征信 混合申请被拒 内鬼 有单的早点报一下 实时拆解 支持 微信🤣 支付宝🤣 U😀
👍1
公积金白名单可以混出,可以指定单位,量大代理价格,🍾
👏1😁1
来自速搜推荐 @SSOU 📢约炮高手❤️把妹达人💋... 📢热播短剧|微视频 📢资源导航中心|新闻导航|... 📢AV|女优|高清|热门|... 📢利博代理 利博官网 利博... 📢欧博百家乐|亚星百家乐|... 📢动漫聚宝盆 📢Telegram增长指南 📢币圈新闻|即时快讯 📢欧博开户 亚星开户 皇冠... 📢中文资源整合|热门频道群... 📢【知鸢°】全国外围 处女... 📢🇹🇼台灣外送茶 | ... 📢日综|变态|搞笑|日韩综... 📢高清经典|影院 👉流量互推规则介绍💥 以下是广告推荐 📢🅾️免费试玩✅大客必备✅注册送158🅾️ 📢 TGFind🚀Telegram最高效的搜索平台! 📢球速体育相信品牌的力量、老品牌值得信赖、不限ip、免实名。 ✅东南亚大事件✅柬埔寨大事件✅东南亚新闻 📢 Ton 中文索引 🇨🇳 简体中文包 —————————-- 🔥将 @TonGroupHelpBot 设置为频道管理员,即可在2
Signed 速搜流量助手
Showing the 12 most recent of 18 posts we hold for @Baiheshuj. 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.
Named by 28 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 23 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.
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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“白蛇数据 BANK” (@Baiheshuj), 1,916 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/Baiheshuj.
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.