秋实正在discord英语角直播~ https://discord.gg/JxmTnUkv8g
❤8👍7

Channel
@qiushichen404
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
1,405subscribers
-45 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001701486574 |
|---|---|
| Type | Channel |
| Username | @qiushichen404 |
| Created | Between 1 December 2021 and 6 May 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 6 October 2026 |
| On Telegram | t.me/qiushichen404 |
Politics & activism — 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 43% 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 |
|---|---|---|
| 6 Oct 2026, 19:36 | 1,405 | -5 |
| 29 Sept 2026, 23:41 | 1,410 | -7 |
| 19 Sept 2026, 17:01 | 1,417 | -3 |
| 15 Sept 2026, 10:19 | 1,420 | +1 |
| 12 Sept 2026, 03:57 | 1,419 | -4 |
| 8 Sept 2026, 07:17 | 1,423 | -5 |
| 2 Sept 2026, 17:56 | 1,428 | -6 |
| 30 Aug 2026, 21:14 | 1,434 | -3 |
| 27 Aug 2026, 17:17 | 1,437 | -1 |
| 20 Aug 2026, 12:43 | 1,438 | -4 |
| 17 Aug 2026, 19:14 | 1,442 | -2 |
| 14 Aug 2026, 16:08 | 1,444 | -4 |
| 10 Aug 2026, 23:21 | 1,448 | -2 |
| 8 Aug 2026, 05:01 | 1,450 | no change |
| 7 Aug 2026, 05:16 | 1,450 | first reading |
19 posts held, back to 6 May 2022 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 19 posts for this entry, the most recent from 1 June 2022. An engagement rate over an empty window would be a number about nothing.
152 reactions across 19 posts, in 9 distinct kinds. The most used accounts for 45.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 69 | 45.4% | |
| ❤ | 31 | 20.4% | |
| 👏 | 29 | 19.1% | |
| 🔥 | 15 | 9.87% | |
| 🥰 | 3 | 1.97% | |
| 😢 | 2 | 1.32% | |
| 😁 | 1 | 0.658% | |
| 😱 | 1 | 0.658% | |
| 🤔 | 1 | 0.658% |
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 19 of the 19 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 152 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 6 May 2022 to 1 June 2022, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
秋实正在discord英语角直播~ https://discord.gg/JxmTnUkv8g
❤8👍7
今晚21:00【秋实英语角】直播间 马丁老师读高华《红太阳是怎样升起的:延安整风始末》英文版 https://youtu.be/Kf8LJVaa7cs 🗣秋实英语角 Telegram群 https://t.me/QiushiEnglishCorner 🤖纳税人的无界城 Discord社群 https://discord.gg/rT6j5a2H5u
👍4❤2
今晚21:00【秋实想歪拉】直播间 是什么让著名律二代选择移居日本? https://youtu.be/usl8Ygh0YoI
👍4👏2
秋实和他妈妈的母亲节 完整版在会员频道 https://youtu.be/aps6ePm7AHI
👏8❤7👍2🔥1
来青岛 跟秋实一起学帆船呀! 🗣秋实英语角 YouTube频道 https://youtube.com/channel/UCWz2hX1SZdSl_HMfnqrDzfg 🗣秋实英语角 Telegram群 https://t.me/QiushiEnglishCorner
🔥4❤3👍1
https://youtu.be/e8k1oSAjOkk
👍3❤1
今晚21:00【秋实英语角】直播 马丁老师读《毛泽东最后的革命》英文原版: 我们现在处在什么样的时代? https://youtu.be/lInfsYYur6g 秋实基本每天早上都会在Discord语音频道和世界各地的网友用英语聊天! https://discord.gg/rT6j5a2H5u 🗣秋实英语角 Telegram群 https://t.me/QiushiEnglishCorner
👍2🔥2
【秋实英语角】英语新闻评论 加州台湾教会枪击案:被挑唆的仇恨 https://youtube.com/shorts/e2FfcESA3zA?feature=share 秋实基本每天早上都会在Discord语音频道和世界各地的网友用英语聊天! https://discord.gg/rT6j5a2H5u 🗣秋实英语角 Telegram群 https://t.me/QiushiEnglishCorner
👍5
终于,我决定为她开启YouTube频道会员! 【完整视频】 https://youtu.be/-BoJwtFlNLs 【片花试听】https://youtu.be/Vfu8L3yTih8 【秋实朋友圈】会员频道有声书《禁书令》,作者是年轻的脑瘫患者小沙,由视障工作者组成的黑乐有声工作室播讲。 感谢频道会员仿生纳税人们对他们的支持!
👍13🥰3
欢迎加入纳税人的无界城 Discord社群! https://discord.gg/rT6j5a2H5u 在这里,每天都会有英语口语训练的机会,来自美、加、澳、新的朋友跟你对话! 🗣此刻,秋实正在秋实英语角视频直播。
👍8❤1👏1🔥1😁1
秋实和他的朋友们,直播中! 即将开始吃好吃的…… https://youtu.be/Eg5jiWF-eG8 🤖纳税人的无界城 Discord社群 https://discord.gg/rT6j5a2H5u
👍3
生在中国偷着乐~你不想乐都不行 完整版视频请点击👇陈秋实油管频道 https://youtu.be/kyNV43d0UpU
👏5😢2🤔1
Showing the 12 most recent of 19 posts we hold for @qiushichen404. 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 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.
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.
@qiushichen404 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 6 October 2026 — this entry's latest reading, not the date you are reading this.
“🎬 陈秋实官方频道” (@qiushichen404), 1,405 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/qiushichen404.
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.