Channel
@zhongwen963
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
226subscribers
-6 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001782008566 |
|---|---|
| Type | Channel |
| Username | @zhongwen963 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 11 September 2026 |
| On Telegram | t.me/zhongwen963 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 06:39 | 226 | -1 |
| 2 Sept 2026, 15:29 | 227 | -3 |
| 25 Aug 2026, 21:03 | 230 | -3 |
| 18 Aug 2026, 12:54 | 233 | +1 |
| 11 Aug 2026, 11:06 | 232 | no change |
| 10 Aug 2026, 14:46 | 232 | first reading |
18 posts held, back to 13 June 2023 — 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 18 posts for this entry, the most recent from 26 January 2026. An engagement rate over an empty window would be a number about nothing.
23 reactions across 11 posts, in 3 distinct kinds. The most used accounts for 65.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 15 | 65.2% | |
| 👍 | 7 | 30.4% | |
| 🥰 | 1 | 4.35% |
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 11 of the 18 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 23 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 13 June 2023 to 26 January 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.
#Telegram 账号冻结自救指南：亲测有效的高通过率话术与流程 近期许多朋友的Telegram账号（尤其是有余额的）频繁被冻结，严重影响联系。经多次亲测，我总结出一套有效的申诉流程和话术，已帮助多人成功解封。 核心原则：第一次申诉决定成败，必须认真对待。 操作流程： 第一步：申诉前准备 心态：保持冷静，准备好英文申诉内容。 话术：内容必须真实、合理，完全符合你的个人使用情况。切勿复制不相关模板。 第二步：申诉中操作 全程使用英文回答所有问题。 仔细阅读每个问题，思考后谨慎作答，杜绝敷衍。 第三步：申诉后验证（最关键） 必须使用手机操作，切勿在电脑端进行。 在手机端点击确认 “我是真人”。 耐心等待，通常一小时内会出结果。不要反复刷新或重复提交。 总结：成败关键在于 “第一次真实、合理的英文申诉” + “最后一步用手机完成真人验证” 。祝大家顺利解封！
🐍 蛇年吉祥，福气满满！ 🎊 蛇年大吉，步步高升！ 🌟 蛇年如意，万事顺心！ 🏡 合家团圆，共享美满！ 🎉 除夕快乐，阖家幸福！ 🐍 蛇年如意，喜乐安康！
模板一 I am sorry if there is any violence in the Telegram terms and conditions, I am loyal to Telegram. My Account is my link to friends, family and business associates. As you know, I am currently abroad, so this account means a lot to me. So please unban my account. I would appreciate it if you could tell me what not to do in the future. thank you very much! 模板二 I didn't post any advertising content, but my account w…
❤2👍2
😏飞机重大更新 1.飞机会员用户可以设置聊天框内自己名字的颜色，目前共有21款颜色组合，目测后期应该可以开放自定义。 2.消息气泡背景可以设置，目前可供选择的背景不多，目测后期会开放！ 设置方式： 设置-界面-your name color 其他更新的功能感觉也就那样。此消息评论区放操作视频 PS 飞机越来越像某鹅，不知道是不是真的被收购/注资了……
❤1
https://t.me/addlist/B2zXmrtsPYE0ZmE1
#Telegram解封，快速解封的方法，解除this phone number is banned提醒 1.用手机或者电脑浏览器打开链接: https://telegram.org/support 2.在此页面填写以下内容，大家可以进行复制，或者自己组织语言，都可以的。 MY number +63 填写你的手机号码 been banned and i am not able to figure out the reason for supension,please help me to recover my account. Thank you.
❤1
电报解除群组屏蔽敏感内容 iOS被限制进入色情频道/群组的解决方法 登录TG网页版 https://web.telegram.org - ➊ 点击【Settings/设置】 ➋ 点击【Privacy and Security/隐私安全】 ➌ 点击【Sensitive content/敏感内容】 ➍ 打开【Disable filtering/停止过滤】选项 ❺ 重启APP（后台划走）即可。 Telegram Web Welcome to the Web application of Telegram messenger. See https://github.com/zhukov/webogram for more info.
❤3
纸飞机TG小助手中文版 pinned Deleted message
正式版本 点击👇即可切换中文 简体中文（未知作者）： tg://setlanguage?lang=classic-zh 简体中文（zh-cn）已停更： tg://setlanguage?lang=classic-zh-cn 简体中文（未知）： tg://setlanguage?lang=zh-hans-raw 简体中文（瓜体）： tg://setlanguage?lang=duang-zh-cn 简体中文（聪聪）： tg://setlanguage?lang=zhcncc 繁體中文（香港）： tg://setlanguage?lang=zh-hant-raw 繁體中文（廣東話） tg://setlanguage?lang=cantonese 繁體中文（香港）： tg://setlanguage?lang=hongkong 繁體中文（香港人口語）非全設備 tg://setlanguage?lang=hongkonger 繁體中…
❤2🥰1
- 解除iOS敏感内容屏蔽 - iOS客户端被限制看色情频道与群组的解决方法 - 登录TG网页版或windows客户端 - TG网页版（官网版）： https://web.telegram.org TG网页版（github版） https://zhukov.github.io/webogram - 验证码登录选择 LOG IN BY PHONE NUMBER - 操作： ➊点击「Settings/设置」 ➋点击「Privacy and Security/隐私安全」 ➌点击「Sensitive content/敏感内容」 ➍打开「Disable filtering/停止过滤」选项 ❺ 重启 iOS 客户端即可。 整个过程就是桌面端或网页版开启显示, 手机端就可以了, 不是也不需要在手机端设置中操作. 要求: * Telegram iOS 客户端版本 ≥ 5.13 备注: Windows, macOS, Linux …
❤1
- Telegram 官网及下载地址 Telegram 有官方版和第三方版本，但出于安全和隐私的考虑，推荐大家使用 Telegram 官方客户端。 一 ，Telegram 官网：[https://telegram.org] 二，Telegram Desktop 桌面客户端： Windows 客户端 [https://desktop.telegram.org/] macOS 客户端 [https://macos.telegram.org/] 三，Telegram iOS 苹果客户端： 请自行在 iPhone/iPad 设备的应用商店 App Store 搜索 Telegram 下载即可。 注：从 Telegram iOS v5.0 版本开始，Telegram 和 Telegram X 已经合并为一个项目，此后不再有 iOS 版本的 Telelgram X。 四，Telegram Android 安卓客户端： Google…
🌐 设定语言方法：只需点击中文所需链接，便可以更新界面语言；将来有新翻译会自动更新，不用手动更新。 ╍ TG语言包，点击即可使用。 ╍ 简体中文 版本一（@Zh_CN 版） https://t.me/setlanguage/classic-zh-cn 版本二（聪聪版） https://t.me/setlanguage/zhcncc 版本三 （官方 beta 版） https://t.me/setlanguage/zh-hans-beta 繁体中文 (台湾) 版本一：https://t.me/setlanguage/zh-hant-beta 版本二：https://t.me/setlanguage/taiwan 繁体中文 (香港) 版本一：https://t.me/setlanguage/hongkong 注： 打开 Telegram 客户端，然后点击以下链接，再点击确认按钮即可转换为中文界面。 这里提供简体中文和繁体…
❤1👍1
Showing the 12 most recent of 18 posts we hold for @zhongwen963. 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.
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 11 September 2026 — this entry's latest reading, not the date you are reading this.
“纸飞机TG小助手中文版” (@zhongwen963), 226 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/zhongwen963.
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.