Telegram RegisterThe public register of Telegram
Telegram profile photo for 虎嗅网

Channel

虎嗅网

@huxiuwang

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

31subscribers

+2 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001983128101
TypeChannel
Username@huxiuwang
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live3 October 2026
Measurements held4
Confirmed unchanged2 times, most recently 3 October 2026
On Telegramt.me/huxiuwang

Topic

National news — 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 30 September 2026 and assigned it the closest of 31 fixed categories, at 64% 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

2931308 August 2026 — 29 subscribers11 August 2026 — 29 subscribers16 August 2026 — 30 subscribers18 September 2026 — 31 subscribers8 August 202618 September 2026
4 measurements spanning 42 days, net +2. 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 29–31 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 20:1931+1
16 Aug 2026, 22:1330+1
11 Aug 2026, 05:3129no change
8 Aug 2026, 00:1929first reading

Engagement

20 posts held, back to 28 May 2025 — 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 20 posts for this entry, the most recent from 29 May 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

29 May 2025, 01:05 UTC72 viewsread 11 August 2026

快倒闭的老商场,被二次元盘活 #独特视角 #新颖 #二次元 Telegraph | source

29 May 2025, 01:05 UTC75 viewsread 11 August 2026

纯净水战火起,今麦郎代工娃哈哈背后的公关大戏 #大公司情报站 #今麦郎 #代工 #娃哈哈集团 #纯净水 Telegraph | source

29 May 2025, 00:56 UTC55 viewsread 11 August 2026

“爱死机”与炒菜机:我们究竟需要什么样的未来家电? #独特视角 #新颖 #家电 #小家电 #白色家电 #中国 #智能家电 #家用电器 Telegraph | source

29 May 2025, 00:37 UTC37 viewsread 11 August 2026

“0公里二手车”乱象曝光,魏建军:三四千家都在卖,非常乱 #创新 #观点 #二手车 #二手车政策 Telegraph | source

29 May 2025, 00:21 UTC22 viewsread 11 August 2026

第一批追赶AI的人,正在被AI甩开 #独到 #观点 #AI #互联网产品经理 #能力模型 #模型公司 #prompt Telegraph | source

29 May 2025, 00:21 UTC28 viewsread 11 August 2026

欧美奢侈品牌,正在为过度涨价付出代价 #新颖 #观点 #奢侈品 #奢侈品市场 #欧美国家 #香奈儿 Telegraph | source

29 May 2025, 00:01 UTC19 viewsread 11 August 2026

关税战40天:美国经济的极限压力测试 #新颖 #观点 #美国经济 #关税 #特朗普 #奢侈品进口关税 #经济学 Telegraph | source

28 May 2025, 23:52 UTC13 viewsread 11 August 2026

回避痛苦这件事,好像成了普遍的精神状态 #新颖 #独到 #心理学 #原生家庭 #心理创伤 #心理学发展 #社会经验 Telegraph | source

28 May 2025, 23:52 UTC11 viewsread 11 August 2026

为什么中国现代文学喜欢写男人的屈辱感? #独特视角 #新颖 #文学 #中国现代文学 #小说 #为奴隶的母亲 #嫁妆一牛车 #作家 Telegraph | source

28 May 2025, 23:52 UTC9 viewsread 11 August 2026

我在马来西亚做餐饮,亏了一套房 #新颖 #创新 #出海 #中国企业出海 #东南亚 #东南亚市场 Telegraph | source

28 May 2025, 23:41 UTC10 viewsread 11 August 2026

我们和硅谷之间的距离,只是一群纯粹者 #独特视角 #观点 #出海 #硅谷 #硅谷科技公司 #美国硅谷 #深圳 #硅谷创业公司 #人工智能 Telegraph | source

Showing the 12 most recent of 20 posts we hold for @huxiuwang. 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 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 18 September 2026 — this entry's latest reading, not the date you are reading this.

“虎嗅网” (@huxiuwang), 31 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/huxiuwang.

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.