Telegram 中文本地化文件分发频道 汉化文件发布:https://t.me/zhsh_cn 子项目: TGCN-群组索引计划(找群和频道): @zh_groups_bot TGCN-群组索引计划频道(实时更新): @zzhcn_zhcn 友情链接: Telegram 种植园: @TelePlanting PSA-安全公告: @TGCNPSA 社区帮助与意见反馈: https://t.me/zzhcn_zhcn *由于我们常常在半夜发布新翻译,您可以通过点击最下方的按键关闭推送通知*
❤1

Channel
@zh_zzc
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
573subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003872911557 |
|---|---|
| Type | Channel |
| Username | @zh_zzc |
| Created | 24 March 2026 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 3 |
| On Telegram | t.me/zh_zzc |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 03:31 | 573 | no change |
| 7 Aug 2026, 20:48 | 573 | -1 |
| 7 Aug 2026, 19:17 | 574 | first reading |
9 posts held, back to 24 March 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 1 pageof 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 9 posts for this entry, the most recent from 24 March 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 8 August 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.
34 reactions across 5 posts, in 5 distinct kinds. The most used accounts for 70.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 24 | 70.6% | |
| 👍 | 4 | 11.8% | |
| 🔥 | 4 | 11.8% | |
| 🎉 | 1 | 2.94% | |
| 🥰 | 1 | 2.94% |
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 5 of the 9 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 34reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 24 March 2026 to 24 March 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 中文本地化文件分发频道 汉化文件发布:https://t.me/zhsh_cn 子项目: TGCN-群组索引计划(找群和频道): @zh_groups_bot TGCN-群组索引计划频道(实时更新): @zzhcn_zhcn 友情链接: Telegram 种植园: @TelePlanting PSA-安全公告: @TGCNPSA 社区帮助与意见反馈: https://t.me/zzhcn_zhcn *由于我们常常在半夜发布新翻译,您可以通过点击最下方的按键关闭推送通知*
❤1
>>> 点击此处安装语言包 <<< https://t.me/setlanguage/classic-zh-cn 对译者:我们在此公开翻译时使用的词汇表,欢迎借鉴。如需修改,请申请编辑权限。 我们采取开放的翻译维护策略,您可以前往相应位置提交翻译建议,我们将会尽快审阅合并。贡献突出的用户将被授予审阅权限。相应的群组仅用于翻译交流,其他有关问题请前往 TG 简中交流(水群) 提出。
❤1🥰1
【社区帮助指南】 >> 进行任何操作前请先阅读《提问的智慧》 << 当前获取社区帮助有两种方式: 1. 通过 TGCN-工单系统 提交工单(仅限问题反馈) 2. 加入 Telegram 简体中文用户交流群 获取来自社区的帮助 无论采用哪种方式,请务必注意自己的言行举止,尊重他人,遵守最基本的社区行为规范。 在求(伸)助(手)前请确保已经仔细阅读频道内的所有说明。 使用工单系统时请确保提供信息完整准确,否则我们将直接关闭工单,不予跟进。 翻译问题、建议,封禁申诉等管理性问题请使用 TGCN-工单系统。 其他问题请使用 Telegram简体中文用户交流群。 * 加入 Telegram简体中文用户交流群 前您需要首先通过一个小小的"视力测试"
❤1
为了您的帐号安全,请及时设置两步验证密码。 设置 -> 隐私和安全 -> 两步验证 该密码只会在新登录 Telegram 时被要求输入,不会带来任何麻烦 否则您的帐户将有很大的风险被盗用 注意: 请避免使用国内免费邮箱作为密码恢复邮箱 详情(英文): https://telegram.org/blog/15million-reuters
随着 Telegram 的快速增长,许多用户表达了支持我们团队的意愿。今天,我们推出了优质的 Telegram Premium – 一项订阅,可让您支持 Telegram 的持续开发并让您访问独家附加功能。
我们将继续基于先前的工作维护最新语言包。 请继续活跃使用与校对人员,该语言包将于此通知发出之时起继续更新与支持服务。已经翻译的部分将无限期保留,其他管理员仍可在自由时间内对语言包进行适度修改。此频道将保留,用于推送更为活跃的语言包项目。 请各位用户选用活跃维护的语言包。我们会对各位用户保障,感谢大家使用。 ⭐️ Telegram OfficialChinese
❤20👍4🔥4🎉1
↑↑电脑用户上方点击安装简体中文语言步骤↑↑↑ 感谢各位一直支持与相伴。
❤1
Channel name was changed to «Telegram中文包»
Channel created
Showing the 9 most recent of 9 posts we hold for @zh_zzc. 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.
Citation-graph rank — 738,582 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
@zh_zzc named 3 handles 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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“Telegram中文包” (@zh_zzc), 573 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/zh_zzc.
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.