Telegram RegisterThe public register of Telegram
Telegram profile photo for 耀沐寒频道

Channel

耀沐寒频道

@yaomuhan2

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

1,192subscribers

+67 since we began measuring on 14 November 2026

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

Register entry

Telegram ID-1001850733569
TypeChannel
Username@yaomuhan2
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 November 2026
Last confirmed live17 November 2026
Measurements held3
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/yaomuhan2

Growth

1,1251,1921,158.514 November 2026 — 1,125 subscribers14 November 2026 — 1,125 subscribers17 November 2026 — 1,192 subscribers14 November 202617 November 2026
3 measurements spanning 3 days, net +67. 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 1,115–1,202 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Nov 2026, 07:371,192+67
14 Nov 2026, 16:221,125no change
14 Nov 2026, 15:471,125first reading

Engagement

16 posts held, back to 24 September 2026 — 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.

ERR · 30 days
136.2%
avg views ÷ 1,192 subscribers
Avg views / post
1,620
13 posts measured
Reaction rate
0.569%
reactions ÷ views · ER floor
Posts in window
14
of 16 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 14 November 2026
Posts held16 (24 September 2026 – 14 November 2026)
Views total21,107
Reactions total120
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Nov 2026, 16:22 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
29s
Average length
15s

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

158 reactions across 15 posts, in 5 distinct kinds. The most used accounts for 75.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍11975.3%
❤1811.4%
🤮127.59%
🤔74.43%
🥰21.27%

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

Measured over the 16 most recent posts we hold, published 24 September 2026 to 14 November 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

Telegram’s own ‘edited’ marker: 2 of 14 posts held from the last 30 days (14.3%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

14 Nov 2026, 10:01 UTC341 views12 reactionsread 14 November 2026

开挂直播装逼的时候: 你们知道什么叫实力吗 开挂被封了之后: 我没有开挂你为什么要封我号,我要去你们大楼跳楼

👍9❤3

12 Nov 2026, 18:32 UTC593 views7 reactionsread 14 November 2026

补Physx模型数据: 模块头 + 0xfc5d178 模块头 + 0xfcf47c0 别问用哪个,两个随便哪个都能用

👍6❤1

12 Nov 2026, 13:34 UTC≈1,260 views6 reactionsread 14 November 2026
File

输出结果.h 4.7数据 刚出炉没测试

👍6

9 Nov 2026, 11:17 UTCviews —

耀沐寒频道 pinned «网盘地址 https://1815757074.share.123pan.cn/123pan/YMSzVv-WqMsd 点击这里加入新频道 免责声明 源码分享免责声明 本声明适用于本人在各平台发布、分享的全部源码、示例代码、配置文件、技术文档及相关内容(以下统称“分享内容”)。 1. 学习交流用途 本人分享的源码仅供学习、交流、技术研究和个人参考使用,不构成任何形式的商业授权、技术承诺或法律意见。未经相关权利人许可,不得将分享内容用于商业用途、非法用途或侵犯他人合法权益的用途。 2.…»

7 Nov 2026, 20:12 UTC≈1,680 views13 reactionsread 14 November 2026
File

TG可验证码登录.zip

👍7🤔4❤2

3 Nov 2026, 14:58 UTC≈2,230 views8 reactionsread 14 November 2026
Video

大哥手感能不能别这么好 有烟你也准星对着我

👍8

31 Oct 2026, 04:20 UTC≈2,660 views8 reactionsread 14 November 2026

发点源码来更新 @yaomuhan 正常一点的

👍7🤔1

30 Oct 2026, 16:33 UTC≈2,690 views12 reactionsread 14 November 2026
Photo

Photo, posted without a caption

👍10❤2

30 Oct 2026, 16:33 UTC≈2,400 views9 reactionsread 14 November 2026
File

葫芦娃_Vulkan_gt_qx驱动.zip

👍8❤1

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

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

“耀沐寒频道” (@yaomuhan2), 1,192 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/yaomuhan2.

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.