Telegram RegisterThe public register of Telegram
Telegram profile photo for zh_cn 中文汉化 中文翻译 简体中文

Channel

zh_cn 中文汉化 中文翻译 简体中文

@zh_cnfpf

2 usernames

On this record: Topic · Growth · Engagement · Citations · Cite this entry

44,493subscribers

-142 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1001210423334
TypeChannel
Usernames@zh_cnfpf @zhpy_cn
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live8 September 2026
Measurements held43
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/zh_cnfpf

Topic

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 9 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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.

Growth

44,49344,63544,56412 August 2026 — 44,635 subscribers12 August 2026 — 44,635 subscribers12 August 2026 — 44,630 subscribers13 August 2026 — 44,627 subscribers14 August 2026 — 44,622 subscribers14 August 2026 — 44,613 subscribers15 August 2026 — 44,609 subscribers16 August 2026 — 44,600 subscribers16 August 2026 — 44,597 subscribers17 August 2026 — 44,595 subscribers18 August 2026 — 44,595 subscribers18 August 2026 — 44,592 subscribers19 August 2026 — 44,587 subscribers19 August 2026 — 44,581 subscribers20 August 2026 — 44,581 subscribers20 August 2026 — 44,578 subscribers21 August 2026 — 44,577 subscribers22 August 2026 — 44,573 subscribers22 August 2026 — 44,570 subscribers23 August 2026 — 44,566 subscribers24 August 2026 — 44,565 subscribers25 August 2026 — 44,563 subscribers25 August 2026 — 44,561 subscribers26 August 2026 — 44,557 subscribers26 August 2026 — 44,556 subscribers26 August 2026 — 44,554 subscribers27 August 2026 — 44,551 subscribers27 August 2026 — 44,551 subscribers28 August 2026 — 44,546 subscribers29 August 2026 — 44,546 subscribers30 August 2026 — 44,544 subscribers31 August 2026 — 44,538 subscribers31 August 2026 — 44,538 subscribers1 September 2026 — 44,536 subscribers1 September 2026 — 44,536 subscribers2 September 2026 — 44,531 subscribers2 September 2026 — 44,531 subscribers3 September 2026 — 44,521 subscribers3 September 2026 — 44,521 subscribers5 September 2026 — 44,509 subscribers5 September 2026 — 44,509 subscribers8 September 2026 — 44,493 subscribers8 September 2026 — 44,493 subscribers12 August 20268 September 2026
43 measurements spanning 27 days, net -142. 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 44,472–44,656 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 43
Measured (UTC)SubscribersChange
8 Sept 2026, 12:1944,493no change
8 Sept 2026, 10:3744,493-16
5 Sept 2026, 09:1744,509no change
5 Sept 2026, 05:1944,509-12
3 Sept 2026, 10:1344,521no change
3 Sept 2026, 09:5644,521-10
2 Sept 2026, 03:5544,531no change
2 Sept 2026, 01:5644,531-5
1 Sept 2026, 05:1344,536no change
1 Sept 2026, 00:5744,536-2
31 Aug 2026, 02:5444,538no change
31 Aug 2026, 02:2244,538-6
30 Aug 2026, 01:3444,544-2
29 Aug 2026, 02:1344,546no change
28 Aug 2026, 20:3544,546-5
27 Aug 2026, 23:0444,551no change
27 Aug 2026, 18:1744,551-3
26 Aug 2026, 22:1444,554-2
26 Aug 2026, 16:2344,556-1
26 Aug 2026, 00:4244,557first reading

Engagement

No public post preview. We read this entry on 12 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

Mentions

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.

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

“zh_cn 中文汉化 中文翻译 简体中文” (@zh_cnfpf), 44,493 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/zh_cnfpf.

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.