Sticker, posted without a caption
🥰9😍8😁2

Channel
@Twining520
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
16,186subscribers
+1,153 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003521128769 |
|---|---|
| Type | Channel |
| Username | @Twining520 |
| Created | 15 December 2025 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 29 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/Twining520 |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 40% 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 |
|---|---|---|
| 9 Sept 2026, 16:01 | 16,186 | -66 |
| 6 Sept 2026, 05:57 | 16,252 | -18 |
| 3 Sept 2026, 23:59 | 16,270 | -1 |
| 2 Sept 2026, 16:48 | 16,271 | +8 |
| 1 Sept 2026, 18:38 | 16,263 | -3 |
| 31 Aug 2026, 21:23 | 16,266 | +9 |
| 30 Aug 2026, 22:07 | 16,257 | +22 |
| 30 Aug 2026, 01:36 | 16,235 | +14 |
| 29 Aug 2026, 05:05 | 16,221 | +50 |
| 28 Aug 2026, 08:32 | 16,171 | +15 |
| 27 Aug 2026, 05:07 | 16,156 | +51 |
| 26 Aug 2026, 05:34 | 16,105 | +79 |
| 25 Aug 2026, 02:04 | 16,026 | +56 |
| 23 Aug 2026, 12:26 | 15,970 | +34 |
| 22 Aug 2026, 01:27 | 15,936 | +34 |
| 20 Aug 2026, 18:38 | 15,902 | +47 |
| 19 Aug 2026, 15:46 | 15,855 | +60 |
| 18 Aug 2026, 19:13 | 15,795 | +15 |
| 17 Aug 2026, 18:58 | 15,780 | +87 |
| 16 Aug 2026, 13:56 | 15,693 | first reading |
82 posts held, back to 15 December 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 57 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 44 of 45 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 31 August 2026 |
|---|---|
| Posts held | 82 (15 December 2025 – 31 August 2026) |
| Views total | 190,978 |
| Reactions total | 667 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 10:00 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.
20,569 reactions across 79 posts, in 10 distinct kinds. The most used accounts for 88.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😱 | 18,126 | 88.1% | |
| ❤ | 688 | 3.34% | |
| 😭 | 681 | 3.31% | |
| 🫡 | 518 | 2.52% | |
| 😁 | 284 | 1.38% | |
| 🥰 | 76 | 0.369% | |
| 🎉 | 64 | 0.311% | |
| 🔥 | 63 | 0.306% | |
| 😍 | 35 | 0.17% | |
| 😘 | 34 | 0.165% |
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 80 of the 82 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 20,569 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 82 most recent posts we hold, published 15 December 2025 to 31 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.
Sticker, posted without a caption
🥰9😍8😁2
Photo, posted without a caption
😱31❤3
😃😀😃广告位☑️ ⭐ @Twiningnb666 😊这个频道我朋友运营着的 我返校了告辞 🌟 我不会再介入所谓项目的更新也没空搞这些没用的东西
❤1
😊TWN失控进化内核 🔥公益使用🔥 ✅适配多个驱动方案。 ✅检测较高所以未来都将为单透版本。 ✅拥有人物相关绘制和物资相关绘制,其他内容还在优化中。 🔹🔹🔹🔹🔹🔹🔹🔹🔹 ✈️官方频道 @Twining520
😱6❤1
Signed 六花g
也劝诫同行好自为之,浪子回头,为时不晚
🔥11🫡6
我是川宁,TWN创始人也是一直以来的负责人 TWN自寒假爆火之后,自四月份左右,就没所谓的团队了,自我入圈以来,卑躬屈膝,那个时候肘子很多,大佬也多,为了在这个圈子混下去我不断的讨好他们,直到后来我起来了,有了如今的地位,但是身边的老作者隐退的隐退,淡圈的淡圈,TWN的团队成员,有的去面对生活了,有的忙于学业,我苦苦支撑到今,TWN没有你想象的那么强,只是身边强的人走了,我如今的成就也是你们带给我的,咱们昧着良心说,我什么时候圈过用户,内核自四月份发布以来一直在大规模优化,即使是两个版本,都在尽力做到最好,而且即使是两个版本我依旧一分钱不挣你们的。 暑假期间在线人数几乎飙升至300多人,为了压热度,我自导自演了两次,把项目名气搞下去,把我本人的口碑搞臭,有人说我炒作让我赶紧滚,我这是炒作,但也是自保。 我从来不给自己扣帽子,慈善家的名号也是你们带给我的,我深知来时的不易,我也是一路被全过来的,所以没开收费,我不赚你们的钱,我…
❤36😭23😱5🎉3🔥3🫡1
跟你们说一下orange实际上就是小米做的换了一个名字因为栀子花已经圈不到钱了已经跑路了作者还是同一个。劝你们还是别买卡,因为说不定他下次圈不到钱了,又换了一个名字,跑路了😂😂😂我们的小米叔叔也是个做人王
❤7
好久没更新了呀,有啥bug发一下。我看今晚有没有时间,有的话就修一下
🫡4😘2❤1
进一下,进一下
❤1
更新版本号
❤5
Cpu占用率高的话,你们把骨骼关掉,别开骨骼绘制
🔥7❤5🫡1
预计下个版本更新
❤9
Showing the 12 most recent of 82 posts we hold for @Twining520. 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.
@Twining520 edited 3 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.
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 1 registered channel — 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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“TWN官方频道” (@Twining520), 16,186 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/Twining520.
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.