学生党们是不是开学了
👍21❤3😢1

Channel
@TwT_kihan
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Polls · Citations · Cite this entry
10,231subscribers
+3,334 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003716856959 |
|---|---|
| Type | Channel |
| Username | @TwT_kihan |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/TwT_kihan |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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 |
|---|---|---|
| 18 Sept 2026, 14:22 | 10,231 | +100 |
| 16 Sept 2026, 06:15 | 10,131 | +84 |
| 14 Sept 2026, 11:59 | 10,047 | +186 |
| 10 Sept 2026, 23:19 | 9,861 | +208 |
| 5 Sept 2026, 21:22 | 9,653 | +281 |
| 1 Sept 2026, 17:03 | 9,372 | +198 |
| 30 Aug 2026, 03:25 | 9,174 | +170 |
| 27 Aug 2026, 11:12 | 9,004 | +406 |
| 24 Aug 2026, 07:12 | 8,598 | +358 |
| 20 Aug 2026, 17:57 | 8,240 | +280 |
| 17 Aug 2026, 17:06 | 7,960 | +317 |
| 14 Aug 2026, 10:37 | 7,643 | +251 |
| 11 Aug 2026, 00:24 | 7,392 | +460 |
| 7 Aug 2026, 19:05 | 6,932 | +35 |
| 7 Aug 2026, 13:03 | 6,897 | first reading |
98 posts held, back to 3 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 23 pages 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 15 of 17 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 28 August 2026 |
|---|---|
| Posts held | 98 (3 August 2026 – 28 August 2026) |
| Views total | 28,770 |
| Reactions total | 197 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 15:40 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.
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.
685 reactions across 75 posts, in 15 distinct kinds. The most used accounts for 65.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 449 | 65.5% | |
| ❤ | 142 | 20.7% | |
| 😭 | 26 | 3.80% | |
| 🍌 | 15 | 2.19% | |
| 🤯 | 14 | 2.04% | |
| 🔥 | 8 | 1.17% | |
| 😡 | 8 | 1.17% | |
| 😁 | 7 | 1.02% | |
| 🤔 | 6 | 0.876% | |
| 🤓 | 3 | 0.438% | |
| 👏 | 2 | 0.292% | |
| 😍 | 2 | 0.292% | |
| 👎 | 1 | 0.146% | |
| 😢 | 1 | 0.146% | |
| 🤪 | 1 | 0.146% |
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 75 of the 98 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 685 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 98 most recent posts we hold, published 3 August 2026 to 28 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.
学生党们是不是开学了
👍21❤3😢1
频道接广 @TwT_driver @TwT_kihan 来点广告商吧饿死了😭😭😭
👍7😍2❤1
修罗炮的主人 pinned «ps:有多人反馈上号3天,也有一些反馈10年,还有部分没封号,现在不知道具体原因。或者你们试一下把配置文件删掉或者重置。。 本项目本来就是公益发着玩的,前面玩的人应该知道,我从发布第一版就一直跟你们说是不裸奔的,虽然手上还有更好的办法但是我感觉没必要上最近一直在忙别的,并且闲鱼还有人拿去倒卖的,我自己爱发电的赞赏都没收到多少块钱结果让别人嘎嘎圈。就这样吧,稳定性问题大概率不会管了,也好让倒卖的消停消停。我本来就没有义务让你稳定,也没强迫你们使用吧。 有问题希望你们能详细的反馈而不是简单的几个字 最后还是感谢使用感谢支持我的家人们…»
修罗炮的主人 pinned a file
ps:有多人反馈上号3天,也有一些反馈10年,还有部分没封号,现在不知道具体原因。或者你们试一下把配置文件删掉或者重置。。 本项目本来就是公益发着玩的,前面玩的人应该知道,我从发布第一版就一直跟你们说是不裸奔的,虽然手上还有更好的办法但是我感觉没必要上最近一直在忙别的,并且闲鱼还有人拿去倒卖的,我自己爱发电的赞赏都没收到多少块钱结果让别人嘎嘎圈。就这样吧,稳定性问题大概率不会管了,也好让倒卖的消停消停。我本来就没有义务让你稳定,也没强迫你们使用吧。 有问题希望你们能详细的反馈而不是简单的几个字 最后还是感谢使用感谢支持我的家人们 最新消息:好像知道问题了,下可能版本回溯一下一些东西
👍27❤7😭6
TwT 火影忍者注入1.6fix lsposed 作用域选择火影忍者 如果选完作用域后上游戏就闪退的多试几次,黑屏的话尝试把游戏移出游戏空间,再不行我也不知道了😋 v1.6fix 优化mumu模拟器启动大概率闪退的问题 优化边缘预警效果 修复模拟器绘制没效果 本人测试机已阵亡后续有问题可能围绕着模拟器修或者不会再更新了,问题先反馈吧... 增加了更多bug 本辅助不裸奔不要拿充钱的号开,要这样还不如请我吃辣条 此辅助完全免费,辅助本身不自带过检测 稳定性自测 稳定性自测 稳定性自测 请我吃辣条: https://www.ifdian.net/a/Lilimao 反馈: @CGT4M 频道: @TwT_driver & @TwT_update
👍13❤7😭3
庆祝频道人数8k 给大家发一个红包
👍6
🎁 邀请永久奖励: 该用户(💰ANT Coin收益*15%) = 888u 点击下方按钮签到免费领取 🧧 23.89 USDT 🧧 @zhipay 👇快来领取你的专属红包!
👍6❤2
三角洲库洛米公益udp解密+多套解密方案 多种功能可使用 是目前全网唯一一个还在检查公益解密的良心项目! 🌟🙃🌟➡️ @kuluomi886
👍4
庆祝频道人数8k 给大家发一个红包
👍6
🧧红包发送成功🧧 🔥蚂蚁MaYi 发送了 一个红包! 💵总金额: 1888 U🪙 🚦剩余: 68/88 🥇 88.88 USDT - 小小心意…. 🥈 78.26 USDT - 国王 🥉 68.61 USDT - 好你哦
👍6
正在使用lsp模块版本以及稳定性
Shares as published. No per-option vote count is published by Telegram, so none is shown.
👍16❤6😁3
Showing the 12 most recent of 98 posts we hold for @TwT_kihan. 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.
@TwT_kihan edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
正在使用lsp模块版本以及稳定性
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 98 most recent posts we hold, published 3 August 2026 to 28 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 4 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“修罗炮的主人” (@TwT_kihan), 10,231 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/TwT_kihan.
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.