Telegram RegisterThe public register of Telegram
Telegram profile photo for 南方周末 / Southern Weekly

Channel

南方周末 / Southern Weekly

@infzm

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

3,005subscribers

+14 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001298780077
TypeChannel
Username@infzm
CreatedBetween 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live24 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 24 August 2026
On Telegramt.me/infzm

Growth

2,9913,0052,9986 August 2026 — 2,991 subscribers6 August 2026 — 2,991 subscribers6 August 2026 — 2,996 subscribers9 August 2026 — 2,995 subscribers12 August 2026 — 2,997 subscribers15 August 2026 — 3,002 subscribers18 August 2026 — 3,005 subscribers21 August 2026 — 3,002 subscribers24 August 2026 — 3,005 subscribers6 August 202624 August 2026
9 measurements spanning 19 days, net +14. 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 2,989–3,007 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 23:343,005+3
21 Aug 2026, 02:483,002-3
18 Aug 2026, 10:133,005+3
15 Aug 2026, 08:073,002+5
12 Aug 2026, 08:072,997+2
9 Aug 2026, 13:112,995-1
6 Aug 2026, 22:202,996+5
6 Aug 2026, 05:022,991no change
6 Aug 2026, 04:062,991first reading

Engagement

28 posts held, back to 3 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
2.54%
avg views ÷ 3,005 subscribers
Avg views / post
76.5
28 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
28
of 28 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held28 (3 August 20267 August 2026)
Views total2,141
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 00:13 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.

Recent posts

7 Aug 2026, 13:56 UTC30 viewsread 8 August 2026

南方周末 一边狂卖500万份,一边48小时极限撤档:2026(上)文娱Z信号盘点 两起儿童死亡事件背后,基因编辑如何走向未来?

7 Aug 2026, 07:56 UTC44 viewsread 8 August 2026

南方周末 从内调室升格为国家情报局,看战败国日本的对外情报野心

7 Aug 2026, 05:54 UTC48 viewsread 8 August 2026

南方周末 多家期刊招募上百青年编委,被一群骗子盯上了 昆明晋宁黄磷泄漏追踪:刺鼻烟雾扩散超40公里,涉事企业曾受环保处罚 “荷兰弟”意外带火森马,网友:步行街三巨头都爱过 抗生素超标5倍还含禁药,“喂药”牛蛙何以难禁?

6 Aug 2026, 17:56 UTC65 viewsread 8 August 2026

南方周末 沈奕斐谈理想男友变迁:过去长得帅又很穷,现在钱在哪爱在哪

6 Aug 2026, 07:56 UTC73 viewsread 8 August 2026

南方周末 伪造结婚证、辅助生殖,婚外胚胎处置惹争议 退休司法官当律师,“约束网”更严密

6 Aug 2026, 05:56 UTC74 viewsread 8 August 2026

南方周末 河南“三支一扶”舞弊案:全链条追责才能守住公平

6 Aug 2026, 03:56 UTC74 viewsread 8 August 2026

南方周末 蜜源地之断翅的蜂王——故乡絮语(九)

5 Aug 2026, 17:41 UTC77 viewsread 8 August 2026

南方周末 曾经动辄上万,如今低至几百:婚纱生意咋越来越难做了

5 Aug 2026, 15:41 UTC73 viewsread 8 August 2026

南方周末 范世涛 | 孙冶方与佐尔格的一面之缘

5 Aug 2026, 13:41 UTC73 viewsread 8 August 2026

南方周末 供应链、中企出海、人工智能等入选“2026年企业社会责任十大关键词” 奔向西班牙飞地:7万摩洛哥人跳海,只为游向“另一个世界” 海外小众IP收割全网共情,国产文艺也应突破“舒适区” 各地均低于100%?被误解的财政自给率

Showing the 12 most recent of 28 posts we hold for @infzm. 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

Citation-graph rank — 1,423,025 of 1,603,893entries 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.

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

“南方周末 / Southern Weekly” (@infzm), 3,005 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/infzm.

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.