Telegram RegisterThe public register of Telegram
Telegram profile photo for TwT无广更新频道

Channel

TwT无广更新频道

@TwT_update

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry

22,622subscribers

+7,016 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1003634257219
TypeChannel
Username@TwT_update
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live25 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/TwT_update

Topic

Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 90% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Views per post sit far above this size band

11,700 average views per post against 22,622 subscribers — an engagement rate of 51.8%. Across the 1,320 registered channels in the same cohort — 10,026–31,615 subscribers, posting mainly in Chinese — the middle half sit between 1.50% and 7.82%, with a median of 3.40%.

What this was computed from
Window30 days (28 August 2026 – 27 September 2026)
Posts measured21 of 21 published in the window (2 exact, 19 rounded by Telegram)
Views totalled246,242
Mature posts only57.0% over 19 posts read at least 24h after publication
Subscribers22,622 measured 25 September 2026
Cohortb10000:zho · 1,320 channels · p10 0.453% · p25 1.50% · p50 3.40% · p75 7.82% · p90 14.7%
Position in cohort99.014th percentile · 15.2× the cohort median
Uncertainty±0.037% of the figure, from Telegram’s rounding
Post languageChinese · 100.0% of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the key err_high, last confirmed 27 September 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

15,60622,62219,1147 August 2026 — 15,606 subscribers8 August 2026 — 15,685 subscribers8 August 2026 — 15,857 subscribers9 August 2026 — 16,203 subscribers11 August 2026 — 16,398 subscribers12 August 2026 — 16,587 subscribers13 August 2026 — 16,821 subscribers14 August 2026 — 17,056 subscribers15 August 2026 — 17,269 subscribers17 August 2026 — 17,529 subscribers18 August 2026 — 17,633 subscribers19 August 2026 — 17,790 subscribers20 August 2026 — 17,997 subscribers21 August 2026 — 18,164 subscribers22 August 2026 — 18,360 subscribers24 August 2026 — 18,555 subscribers25 August 2026 — 18,738 subscribers26 August 2026 — 18,854 subscribers27 August 2026 — 19,036 subscribers28 August 2026 — 19,179 subscribers29 August 2026 — 19,322 subscribers30 August 2026 — 19,453 subscribers31 August 2026 — 19,563 subscribers1 September 2026 — 19,655 subscribers2 September 2026 — 19,770 subscribers3 September 2026 — 19,914 subscribers5 September 2026 — 20,223 subscribers9 September 2026 — 20,577 subscribers11 September 2026 — 20,822 subscribers13 September 2026 — 21,096 subscribers15 September 2026 — 21,208 subscribers17 September 2026 — 21,426 subscribers25 September 2026 — 22,622 subscribers7 August 202625 September 2026
33 measurements spanning 49 days, net +7,016. 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 14,554–23,674 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
25 Sept 2026, 19:4122,622+1,196
17 Sept 2026, 08:0121,426+218
15 Sept 2026, 06:0121,208+112
13 Sept 2026, 15:1921,096+274
11 Sept 2026, 18:3920,822+245
9 Sept 2026, 03:5720,577+354
5 Sept 2026, 21:3820,223+309
3 Sept 2026, 22:1819,914+144
2 Sept 2026, 16:2419,770+115
1 Sept 2026, 15:2819,655+92
31 Aug 2026, 12:3719,563+110
30 Aug 2026, 12:3919,453+131
29 Aug 2026, 10:2619,322+143
28 Aug 2026, 07:3219,179+143
27 Aug 2026, 04:4719,036+182
26 Aug 2026, 07:0218,854+116
25 Aug 2026, 06:5218,738+183
24 Aug 2026, 03:3318,555+195
22 Aug 2026, 14:0218,360+196
21 Aug 2026, 06:0818,164first reading

Engagement

62 posts held, back to 12 July 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 59 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
51.8%
avg views ÷ 22,622 subscribers
Avg views / post
11,700
21 posts measured
Reaction rate
0.309%
reactions ÷ views · ER floor
Posts in window
21
of 62 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 26 September 2026
Posts held62 (12 July 2026 – 26 September 2026)
Views total246,242
Reactions total762
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Sept 2026, 03:38 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.

What this channel posts

Photos
19
Videos
8
Links
67

Lifetime counters from Telegram’s own channel header, read 27 September 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.

Video runtime
1m 24s
Average length
42s

Measured directly from 2 videos 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.

Reaction mix

1,836 reactions across 61 posts, in 22 distinct kinds. The most used accounts for 69.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1,26669.0%
❤48226.3%
🔥140.763%
🥰100.545%
😨60.327%
🤓60.327%
🍌50.272%
🍾50.272%
👏50.272%
😁50.272%
😱50.272%
👎40.218%
😍40.218%
😈30.163%
🤔30.163%
🤪30.163%
🤯30.163%
🐳20.109%
🙏20.109%
💅10.054%
2 further kinds20.109%

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

Measured over the 62 most recent posts we hold, published 12 July 2026 to 26 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.

Recent posts

26 Sept 2026, 19:45 UTC437 views13 reactionsread 27 September 2026
Forwarded from @luoyenb521File

❤️三角洲落叶公益算法解密内核 新增算法解密3方案,几乎无任何延迟适配率极高,如果用不了就用方案2 😙使用辅助前先执行驱动 否则解密无效 解密没效果解决办法: 大退游戏重新打开 对局内开解密下飞机之后等人物都刷新出来几秒别多点 解密不要保存配置 遇到卡屏打1-2把就关掉辅助重新打开也行 如果遇到漏人问题点清理缓存即可 公益解密卡密: luoyenb521 ❗️❗️➡️点我加入官方频道 ❗️❗️➡️点我加入官方群组

👍12❤1

26 Sept 2026, 17:33 UTC735 views24 reactionsread 27 September 2026
Forwarded from @time_pd

狗头专业破解频道以下为破解的业务主要范围 ❤️🎮🎮🎮🎮🎮 专业搞破解的一名公益者 如果你觉得市场项目太昂贵了可以跟狗头投稿 投稿发包+一张未使用过的卡密 🌟🙃🌟➡️ @pj7645

👍23🔥1

25 Sept 2026, 16:30 UTC≈6,430 views33 reactionsread 27 September 2026
File

收集一些信息供适配驱动使用 执行完后把生成的kmod_collect_xxx.tar.gz发上来就行了(发评论区)

👍30❤3

25 Sept 2026, 12:35 UTC≈3,340 views37 reactionsread 27 September 2026

卡丘现在是注入什么功能都不开也会十年吗,还是说开特定功能会拉闸

👍34😍3

23 Sept 2026, 10:58 UTC≈12,500 views33 reactionsread 27 September 2026
File

TwT驱动v1.51 更新内容 修复部设备刷入时卡住的问题(部分5.4的设备) 2026/9/23 8:32: 修复强制刷入模式bug导致失败的问题 对接例子同1.50 请我吃辣条:https://www.ifdian.net/a/Lilimao TG: @TwT_driver/@TwT_update

👍29❤4

23 Sept 2026, 05:44 UTC≈4,290 views46 reactionsread 27 September 2026
Forwarded from @TwT_kihanPhoto

有没有人想玩皇游的🤔

👍35❤10😁1

19 Sept 2026, 12:48 UTC≈9,220 views42 reactionsread 27 September 2026
File

卡拉彼丘注入 游戏版本:1.1.9.1 更新内容:适配最新版本游戏 食用方法:打开游戏,然后在大厅界面注入 -频道验证需加入下面三个频道,并点击头像等待加载完成- 最新消息频道:@TwT_update 驱动更新频道:@TwT_driver 火影更新频道:@TwT_kihan 赞赏链接:https://www.ifdian.net/a/Lilimao

👍27❤13💅1😍1

17 Sept 2026, 00:00 UTC≈10,500 views5 reactionsread 27 September 2026

#频道互推 #相似推荐 ------------------------------ 📢 🦙资源整合|线报|羊毛|软件|破解|电影 📢 【你的收藏夹】中文资源频道 📢 资源公社 |CXSNS Resource Hub 📢 资源情报局 | 学习 · 工具 · AI · 副业 📢 沈阳技师 📢 太原资源堂 📢 惠州资源榜 📢 橘子综合资源分享中心 📢 TG信息接收共享 📢 赣州国色录 ------------------------------ 🤝 加入互推 · 获得曝光,赚邀请奖励

👍4👎1

16 Sept 2026, 01:36 UTC≈7,610 views19 reactionsread 27 September 2026
Forwarded from @TwT_kihanFile

TwT 火影忍者注入1.7 lsposed 作用域选择火影忍者 如果选完作用域后上游戏就闪退的多试几次,黑屏的话尝试把游戏移出游戏空间,再不行我也不知道了😋 v1.7 修复使用新版lsposed崩溃 去掉红字功能😭 凭空想象修复部分用户可以裸奔的问题(大家都不允许裸奔) 去掉了一些可能被检测的点...删掉了一些绕过相关的代码😹 增加了更多bug 本辅助不裸奔不要拿充钱的号开,要这样还不如请我吃辣条 此辅助完全免费,辅助本身不自带过检测 稳定性自测 稳定性自测 稳定性自测 请我吃辣条: https://www.ifdian.net/a/Lilimao 反馈: @CGT4M 频道: @TwT_driver & @TwT_update

👍10❤7🥰1😁1

15 Sept 2026, 16:25 UTC≈9,040 views26 reactionsread 27 September 2026
File

分享一份最新版(0.9.97.800)未来之役的SDK 供辅助开发者参考和寻找数据 如果您是辅助用户或者不知道这是啥的话请忽略 请我吃辣条:https://www.ifdian.net/a/Lilimao TG: @TwT_driver / @TwT_update

👍17❤9

15 Sept 2026, 15:47 UTC≈7,970 views26 reactionsread 27 September 2026

emmm概率闪退我也不知道啥原因,能用且用吧😔

👍23❤2🤔1

15 Sept 2026, 12:58 UTC≈8,670 views33 reactionsread 27 September 2026

刚刚传的文件有点问题,如果进对局会绘制自己和队友的话重新下载一下就行了

👍30❤3

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

Posts edited after publishing

@TwT_update edited 1 post 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.

First edit seen
16 August 2026
Most recent edit
16 August 2026

Forward network

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.

Mentions

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

“TwT无广更新频道” (@TwT_update), 22,622 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/TwT_update.

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.