Telegram RegisterThe public register of Telegram
Telegram profile photo for 百事通-知识问答频道🌾

Channel

百事通-知识问答频道🌾

@zhishidashen

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

23,964subscribers

+2,638 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002760930757
TypeChannel
Username@zhishidashen
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live19 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/zhishidashen

Topic

Education — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 77% 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

21,32623,96422,6456 August 2026 — 21,326 subscribers7 August 2026 — 21,337 subscribers8 August 2026 — 21,370 subscribers8 August 2026 — 21,409 subscribers10 August 2026 — 21,465 subscribers10 August 2026 — 21,503 subscribers11 August 2026 — 21,564 subscribers13 August 2026 — 21,618 subscribers14 August 2026 — 21,674 subscribers15 August 2026 — 21,744 subscribers17 August 2026 — 22,194 subscribers18 August 2026 — 22,315 subscribers19 August 2026 — 22,392 subscribers20 August 2026 — 22,504 subscribers21 August 2026 — 22,596 subscribers22 August 2026 — 22,720 subscribers24 August 2026 — 22,822 subscribers25 August 2026 — 22,872 subscribers26 August 2026 — 22,956 subscribers27 August 2026 — 23,016 subscribers28 August 2026 — 23,060 subscribers29 August 2026 — 23,122 subscribers30 August 2026 — 23,173 subscribers31 August 2026 — 23,239 subscribers1 September 2026 — 23,274 subscribers2 September 2026 — 23,315 subscribers3 September 2026 — 23,376 subscribers5 September 2026 — 23,460 subscribers7 September 2026 — 23,561 subscribers10 September 2026 — 23,640 subscribers13 September 2026 — 23,716 subscribers14 September 2026 — 23,796 subscribers16 September 2026 — 23,893 subscribers19 September 2026 — 23,964 subscribers6 August 202619 September 2026
34 measurements spanning 43 days, net +2,638. 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 20,930–24,360 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
19 Sept 2026, 01:2123,964+71
16 Sept 2026, 15:2023,893+97
14 Sept 2026, 18:1523,796+80
13 Sept 2026, 01:2023,716+76
10 Sept 2026, 23:4023,640+79
7 Sept 2026, 21:5723,561+101
5 Sept 2026, 00:2023,460+84
3 Sept 2026, 10:5823,376+61
2 Sept 2026, 04:2523,315+41
1 Sept 2026, 02:3423,274+35
31 Aug 2026, 01:0523,239+66
30 Aug 2026, 03:2523,173+51
29 Aug 2026, 02:5323,122+62
28 Aug 2026, 03:1223,060+44
27 Aug 2026, 06:3223,016+60
26 Aug 2026, 08:4322,956+84
25 Aug 2026, 06:4822,872+50
24 Aug 2026, 06:3922,822+102
22 Aug 2026, 17:4222,720+124
21 Aug 2026, 07:1922,596first reading

Engagement

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

ERR · 30 days
14.6%
avg views ÷ 23,964 subscribers
Avg views / post
3,510
25 posts measured
Reaction rate
0.073%
reactions ÷ views · ER floor
Posts in window
25
of 81 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. It is computed over the 18 of 25 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 September 2026
Posts held81 (28 July 20263 September 2026)
Views total87,635
Reactions total50
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 11:07 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.

What this channel posts

Video runtime
21s
Average length
21s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

141 reactions across 39 posts, in 8 distinct kinds. The most used accounts for 44.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
6244.0%
🤡2719.1%
👍1913.5%
🤣128.51%
💩117.80%
😁74.96%
👏21.42%
🔥10.709%

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 53 of the 81 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 141 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 81 most recent posts we hold, published 28 July 2026 to 3 September 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.

Recent posts

3 Sept 2026, 02:10 UTC735 views13 reactionsread 3 September 2026
Photo

本人是文盲一名,想通过tg过个科目四,可以从这上面购买一个吗?

🤣12👍1

3 Sept 2026, 02:09 UTC732 views1 reactionsread 3 September 2026
Photo

本人是文盲一名,想通过tg过个科目四,可以从这上面购买一个吗?

👍1

3 Sept 2026, 02:08 UTC718 views1 reactionsread 3 September 2026

飞机上那种大群里面的抓龙筋是真的吗

👍1

2 Sept 2026, 14:34 UTC≈1,250 viewsread 3 September 2026

问个事,我在飞机上下载了些数据文件,由于飞机限制文件大小,群主发了多个联合人文件,从001、002...013。我全部下完之后到7.zip解压时显示【无法作为 [7z] 压缩包打开该文件、文件末端错误】我重新下载也没用,是我操作失误吗

2 Sept 2026, 10:35 UTC≈1,470 viewsread 3 September 2026

有没有资深懂承兑的兄弟,目前怎么做能长期稳定买u,除了线下那种,支付宝从交易所买u怎么稳住支付宝端和交易所不被封 via 飞鱼

1 Sept 2026, 12:36 UTC≈1,980 viewsread 3 September 2026

我想去罗马尼亚这个国家留学,但是又很少关于那个国家的资料信息,问中介,因为说这是个小国家,留学的人特别少,所以也没开展业务,有谁知道关于这方面信息的哥哥姐姐们,想去读医学方面的。还请告诉一下,谢谢了

31 Aug 2026, 11:30 UTC≈2,590 viewsread 3 September 2026
Photo

水军举报一个千粉的抖音是这个价吗,不会是骗子吧

31 Aug 2026, 11:28 UTC≈2,400 viewsread 3 September 2026

最近遇到了一些说可以跑美团卡密还有 CK 号的,交易的时候他们说公群交易,有大哥知道这些担保公群是真的还是假的呀?靠谱嘛,会不会群里几千人全是猪仔,有没有懂行的大哥 交易这些的时候是怎么交易的呀,求解答🥺

30 Aug 2026, 05:53 UTC≈3,150 views4 reactionsread 3 September 2026
Video

兄弟们问一下这个效果是要全息投影仪才能做出来吗 via 陈总 香港

4

29 Aug 2026, 13:08 UTC≈3,620 views13 reactionsread 3 September 2026

花钱买教训了,其他群里广告找了技师,让我交预约费,又提前交服务费,最后还来个安全押金,这里我觉得不对劲了就让他们退钱。后面又让我联系什么财务,开屏幕共享。我不开,对方说把我的记录移交给帽子叔叔。钱是要不回来了,请问有后续风险吗?

🤡10💩2👍1

29 Aug 2026, 08:23 UTC≈3,620 views4 reactionsread 3 September 2026

我爸提公积金好像被骗了,问他也不说,好像是对方买房子再退回来之类的,银行卡和身份证信息都给对面了,从开始到现在有快三个月了,怎么办,还有办法弄回来吗

2👍2

28 Aug 2026, 08:42 UTC≈4,090 views0 reactionsread 3 September 2026

有没有好心人教我怎么下载推特呀?我现在用的推特要更新了,但是我下载不了谷歌商店有没有好心人让我加一下你,我下载完推特请你喝奶茶,而且推特为什么现在还要验证年龄了 via 我活着玩的

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

Mentions

Named by 3 registered channels — 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.

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.

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

“百事通-知识问答频道🌾” (@zhishidashen), 23,964 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/zhishidashen.

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.