Telegram RegisterThe public register of Telegram
Telegram profile photo for 延安的互联网茶馆

Channel

延安的互联网茶馆

@yananpy

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

5,925subscribers

-3,379 since we began measuring on 15 August 2026

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

Register entry

Telegram ID-1003706262422
TypeChannel
Username@yananpy
CreatedBetween 1 February 2026 and 30 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded15 August 2026
Last confirmed live9 September 2026
Measurements held9
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/yananpy

Growth

5,9259,3047,614.515 August 2026 — 9,304 subscribers16 August 2026 — 9,263 subscribers19 August 2026 — 9,204 subscribers23 August 2026 — 7,707 subscribers26 August 2026 — 6,152 subscribers29 August 2026 — 6,103 subscribers1 September 2026 — 6,068 subscribers4 September 2026 — 6,017 subscribers9 September 2026 — 5,925 subscribers15 August 20269 September 2026
9 measurements spanning 26 days, net -3,379. 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 5,418–9,811 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 20:215,925-92
4 Sept 2026, 17:176,017-51
1 Sept 2026, 01:456,068-35
29 Aug 2026, 09:586,103-49
26 Aug 2026, 08:266,152-1,555
23 Aug 2026, 11:237,707-1,497
19 Aug 2026, 13:159,204-59
16 Aug 2026, 03:359,263-41
15 Aug 2026, 00:169,304first reading

Engagement

96 posts held, back to 14 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 15 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
2.19%
avg views ÷ 5,925 subscribers
Avg views / post
130
94 posts measured
Reaction rate
1.61%
reactions ÷ views · ER floor
Posts in window
96
of 96 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 42 of 94 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 25 August 2026
Posts held96 (14 August 202625 August 2026)
Views total12,214
Reactions total120
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken25 Aug 2026, 04:42 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
5m 20s
Average length
46s

Measured directly from 7 videos 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

120 reactions across 41 posts, in 4 distinct kinds. The most used accounts for 74.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍8974.2%
1613.3%
🤔97.50%
🤣65.00%

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

Measured over the 96 most recent posts we hold, published 14 August 2026 to 25 August 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

25 Aug 2026, 03:51 UTC23 views3 reactionsread 25 August 2026

免费假地址机器人 https://t.me/xintyyyyybot?start=6BQ5QO

👍3

Signed 延安 @lunbian 厨神6666老板

25 Aug 2026, 01:41 UTC44 viewsread 25 August 2026

#最新资讯 Nekogram 12.5.2 被曝存在后门,静默窃取用户手机号 安全研究人员发现第三方 Telegram 客户端 Nekogram 12.5.2(Google Play 版)内置后门代码,会在用户不知情的情况下收集所有已登录账号的手机号,并通过 Inline Query 外传至开发者控制的 Bot(@nekonotificationbot)。 后门代码位于 Extra.java(混淆后为 uo5),核心逻辑:遍历 8 个账号槽位 → 提取 UserID 与手机号 → 拼接密钥后以 Inline Query 发送。所有关键字符串均经自定义加密混淆。 该后门仅存在于编译发布的 APK 中,GitHub 公开源码中的对应文件为无害占位。经独立反编译对比验证,从源码自行编译的版本不含上述后门组件。 开发者回应称 Bot 仅用于"解析用户名",但代码中明确提取了 phone 字段并使用无痕传输方式,与其说辞不符。

Signed 延安 @lunbian 厨神6666老板

24 Aug 2026, 18:35 UTC68 viewsread 25 August 2026
File

@lunbiamYINGYUEbot | info

Signed 延安 @lunbian 厨神6666老板

24 Aug 2026, 18:29 UTC64 viewsread 25 August 2026

搞了个音乐机器人 🎵 可通过声音、视频、链接或文字识别音乐 🔍 https://t.me/lunbiamYINGYUEbot

Signed 延安 @lunbian 厨神6666老板

24 Aug 2026, 18:17 UTC69 views2 reactionsread 25 August 2026

开了个公群进来🥰😍 https://t.me/+WZ26Hz1QwZ45NWUx

1👍1

Signed 延安 @lunbian 厨神6666老板

24 Aug 2026, 17:49 UTC72 views1 reactionsread 25 August 2026

高价收购各种 频道/群组/api/py 有意向联系 @lunbian

👍1

Signed 延安 @lunbian 厨神6666老板

24 Aug 2026, 17:39 UTC83 viewsread 25 August 2026
Photo

#最新资讯 清风反诈被封禁

Signed 延安 @lunbian 厨神6666老板

24 Aug 2026, 17:30 UTC86 viewsread 25 August 2026
Photo

Photo, posted without a caption

Signed 延安 @lunbian 厨神6666老板

24 Aug 2026, 17:30 UTC85 viewsread 25 August 2026

?我被春江做局了

Signed 延安 @lunbian 厨神6666老板

23 Aug 2026, 20:13 UTC158 views3 reactionsread 25 August 2026

送5u睡觉

3

Signed 延安 @lunbian 厨神6666老板

23 Aug 2026, 05:33 UTC222 views4 reactionsread 25 August 2026

姓名:邱晨阳 身份证:421302200808245233 二要素核验: 实名认证成功! ✅ 国政模糊: 130xxxx3168 ✅

👍4

Signed 延安 @lunbian

22 Aug 2026, 17:54 UTC256 viewsread 25 August 2026

抖音模糊位 抖音模糊位全国前一后一抖音极速版我的客服锁定保护 输入手机号刷脸验证 出身份证前一后一

Signed 延安 @lunbian

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

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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

“延安的互联网茶馆” (@yananpy), 5,925 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/yananpy.

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.