庆祝频道人数10k 给大家发一个红包
Signed 实名 八弟

Channel
@TigerCN_BY
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
10,220subscribers
-152 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001819424762 |
|---|---|
| Type | Channel |
| Username | @TigerCN_BY |
| Description | 此频道主是一位热爱编程的小白 频道主 @TG_702 双向联系 @TG_702_bot 我的私人反馈频道 @TigerCN_FK 通知群①:516892317 通知群②:954446419 交流群①:765032500 交流群②:465992821 氛哥于2023年10月28日退网,并转让频道给他的看门徒弟北遇 铭记氛哥,永驻心中! |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/TigerCN_BY |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 09:36 | 10,220 | -27 |
| 13 Aug 2026, 22:38 | 10,247 | -13 |
| 12 Aug 2026, 17:28 | 10,260 | -16 |
| 11 Aug 2026, 20:14 | 10,276 | -22 |
| 10 Aug 2026, 22:42 | 10,298 | -8 |
| 10 Aug 2026, 00:30 | 10,306 | -36 |
| 8 Aug 2026, 21:57 | 10,342 | -26 |
| 7 Aug 2026, 23:18 | 10,368 | -4 |
| 7 Aug 2026, 09:15 | 10,372 | first reading |
67 posts held, back to 30 May 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 20 pagesof 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 34 of 61 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 15 August 2026 |
|---|---|
| Posts held | 67 (30 May 2026 – 15 August 2026) |
| Views total | 10,160 |
| Reactions total | 103 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Aug 2026, 19: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.
Lifetime counters from Telegram’s own channel header, read 15 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
135 reactions across 36 posts, in 11 distinct kinds. The most used accounts for 44.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 60 | 44.4% | |
| ❤ | 26 | 19.3% | |
| 👎 | 10 | 7.41% | |
| 😁 | 10 | 7.41% | |
| 🤔 | 9 | 6.67% | |
| 🔥 | 6 | 4.44% | |
| 🥰 | 5 | 3.70% | |
| 😢 | 4 | 2.96% | |
| ⚡ | 2 | 1.48% | |
| 🍌 | 2 | 1.48% | |
| 🤗 | 1 | 0.741% |
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 39 of the 67 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 135reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 67 most recent posts we hold, published 30 May 2026 to 15 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.
庆祝频道人数10k 给大家发一个红包
Signed 实名 八弟
起点担保 祝您马年快乐🐴 🧧 起点客服-小马 发送了一个红包 💵总金额:10000 USDT💰 剩余:298/500 🥇 33.78 USDT🪙 - 小黄 🥈 33.77 USDT🪙 - X趣趣天 🥉 33.30 USDT🪙 - 七彩铁 钱包选起点,靠谱有担当 !😃 新年到来 ,2026百万红包!⭐
Signed 实名 八弟
三角洲公益◆算法解密,不嘿嘿内核 更新日志: 1.修复最新闪框加密 2.修复内核绘图字体清晰度 3.修复物资,绘图UI界面功能无法保存 Unicorn纯算法解密,不动内存,通过密钥安全解密 physx模型掩体自瞄漏打,漏那打那,WiFi局域网页雷达共享视野 公益三角洲解密项目,卡密随便输入,已更新至8.14日最新解密,内核级驱动,不协议,不十年,不三十天,稳定得吃,安全性拉满 真正可以稳定的三角洲公益解密内核 不嘿嘿频道: @enennba
👍3
Signed 实名 八弟
【手机口课结记录】昌盛国际集团 ❤️❤️❤️❤️❤️❤️❤️❤️ ❤️❤️❤️❤️❤️❤️❤️❤️ 【工作时间:9:00-23:00】 手机口无线价格:❤️❤️❤️❤️ 💵📩人民币结算:❤️❤️❤️❤️➕❤️❤️❤️➕❤️❤️ 手机口赚钱联系😀@shangkou8 😃😃😃😃 @shangkou8 不能私信发信息的联系 ⬇️ ⬇️ ⬇️ @shangkouo_bot 【双向联系客服机器人】 【频道入口】
👍4
Signed 昌盛集团 诺诺
【手机口账单结清】 💲昌盛国际集团 全网投资千万 你的第一选择 ❤️❤️❤️❤️❤️❤️❤️❤️ ❤️❤️❤️❤️❤️❤️❤️❤️ 【工作时间:8:30-22:30】 无线手机口价格:❤️❤️❤️❤️ 💵📩人民币结算:❤️❤️❤️❤️➕❤️❤️❤️➕❤️❤️ (点击下方蓝色按钮自助导航) 👇👇👇👇👇👇👇👇 赚钱联系😀 @shangkou8 😃😃😃😃 @shangkou8 不能私信发信息的联系 ⬇️ ⬇️ ⬇️ @shangkouo_bot 【每日实时结算记录频道】 公群链接:@shoujikouchangdio
Signed 昌盛集团 诺诺
老虎已经死了🤓 北遇因为打官司输了 坐牢了 没有两年出不来🤓 已经把频道转让给我了
👍3🔥2
Signed 三军统帅 七崽
庆祝频道人数10k 给大家发一个红包
👍1
Signed 实名 八弟
起点担保 祝您马年快乐🐴 🧧 起点客服-小马 发送了一个红包 💵总金额:10000 USDT💰 剩余:298/500 🥇 33.78 USDT🪙 - 小黄 🥈 33.77 USDT🪙 - X趣趣天 🥉 33.30 USDT🪙 - 七彩铁 钱包选起点,靠谱有担当 !😃 新年到来 ,2026百万红包!⭐
👍1
Signed 实名 八弟
🐶15岁少萝在别墅被7位金主爸爸內射到sao穴 轮奸再一个个粗壮的肉棒的蹂躏下小穴被干的通红 曾多次高潮尿失禁 避孕套都用光了几盒视频
👍1🤔1
Signed 实名 八弟
爽玩了
👍5
Signed LD
说实话,PUBGM我也弄不下去了,现实生活也过得不如意,就这样吧,再见了各位,下辈子有缘再见!
⚡2🤗1
Signed 北遇 [实名上网吴扬]
🐶15岁少萝在别墅被7位金主爸爸內射到sao穴 轮奸再一个个粗壮的肉棒的蹂躏下小穴被干的通红 曾多次高潮尿失禁 避孕套都用光了几盒视频
Signed 实名 八弟
Showing the 12 most recent of 67 posts we hold for @TigerCN_BY. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
@TigerCN_BY named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“𝙏𝙞𝙜𝙚𝙧 - 𝘾𝙉官方频道🇨🇳” (@TigerCN_BY), 10,220 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/TigerCN_BY.
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.