【🔔系统】叮!!! S4 赛季,赛前预热!点击下方按钮解锁赛季通行证。 @ymtgtgbot @ym_ass
😭238🤡91👍32❤6🕊6👀3🔥3
Channel
@ym_ass
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
58,676subscribers
+691 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002283172640 |
|---|---|
| Type | Channel |
| Username | @ym_ass |
| Description | 本群是一个致力于研究网络亚文化、迷因(Meme)演化和当代俚语的语言学兴趣小组。 研究对象: 解构、模仿并记录各种网络流行语、讽刺文学、抽象符号及“梗”的形成与传播。 交流方式: 成员间常使用夸张、反讽、戏仿、双关等修辞手法进行交流,这本身就是我们研究的一部分。言论可能看似无逻辑或包含歧义,但其本质是对于语言边界的探索。 免责声明: 本群所有内容均不代表成员真实观点,仅为语言学和社会学观察样本。我们坚决反对并禁止任何形式的仇恨言论和违法信息。请以分析和解构的视角看待本群对话。 |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 25 August 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 25 August 2026 |
| On Telegram | t.me/ym_ass |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Aug 2026, 19:18 | 58,676 | +25 |
| 24 Aug 2026, 21:27 | 58,651 | +61 |
| 23 Aug 2026, 06:03 | 58,590 | +46 |
| 21 Aug 2026, 14:26 | 58,544 | +15 |
| 20 Aug 2026, 17:03 | 58,529 | +41 |
| 19 Aug 2026, 17:21 | 58,488 | +52 |
| 18 Aug 2026, 18:53 | 58,436 | +58 |
| 17 Aug 2026, 19:56 | 58,378 | +64 |
| 16 Aug 2026, 18:23 | 58,314 | +156 |
| 15 Aug 2026, 03:44 | 58,158 | +97 |
| 13 Aug 2026, 23:17 | 58,061 | +66 |
| 12 Aug 2026, 20:17 | 57,995 | +20 |
| 11 Aug 2026, 17:56 | 57,975 | -2 |
| 10 Aug 2026, 16:03 | 57,977 | +2 |
| 9 Aug 2026, 17:42 | 57,975 | -16 |
| 8 Aug 2026, 18:01 | 57,991 | -4 |
| 7 Aug 2026, 17:02 | 57,995 | +10 |
| 7 Aug 2026, 15:15 | 57,985 | first reading |
22 posts held, back to 8 September 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 41 pagesof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 22 August 2026 |
|---|---|
| Posts held | 22 (8 September 2025 – 22 August 2026) |
| Views total | 58,500 |
| Reactions total | 1,469 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 26 Aug 2026, 01:58 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.
Lifetime counters from Telegram’s own channel header, read 26 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
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.
5,349 reactions across 22 posts, in 26 distinct kinds. The most used accounts for 72.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😭 | 3,901 | 72.9% | |
| ❤ | 587 | 11.0% | |
| 🫡 | 332 | 6.21% | |
| 🤡 | 91 | 1.70% | |
| 🥰 | 71 | 1.33% | |
| 😢 | 60 | 1.12% | |
| 👍 | 59 | 1.10% | |
| 🤣 | 49 | 0.916% | |
| 🤗 | 35 | 0.654% | |
| 🤬 | 31 | 0.58% | |
| 😁 | 29 | 0.542% | |
| 🕊 | 28 | 0.523% | |
| 🔥 | 21 | 0.393% | |
| 👏 | 16 | 0.299% | |
| 🖕 | 6 | 0.112% | |
| 🌭 | 5 | 0.093% | |
| 🗿 | 5 | 0.093% | |
| 🙏 | 5 | 0.093% | |
| 🤮 | 5 | 0.093% | |
| ✍ | 3 | 0.056% | |
| 6 further kinds | 10 | 0.187% |
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 22 of the 22 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 5,349reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 22 most recent posts we hold, published 8 September 2025 to 22 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.
【🔔系统】叮!!! S4 赛季,赛前预热!点击下方按钮解锁赛季通行证。 @ymtgtgbot @ym_ass
😭238🤡91👍32❤6🕊6👀3🔥3
嗯,轰轰烈烈的银梦大S3赛季结束辣! S4筹备中🤓👆 [银梦日报(表)] @ymrbrbrb 里面有历史投稿 [树洞频道] @ymsd8 接受纯文本投稿 [夜聊群] 话题聊天群 [闪图机器人] 每日热榜超火爆 [回家频道] @ym_ass
😭1,030❤25👍14🕊7🌭5🗿5💊2🔥1
🛜长时间没通过的,重新点击按钮可以重新再验证。(刚刚有点bug可能卡了。
❤55😭22😁5
🔔系统:叮!S3 赛季预热中... @ymtgtgbot @ym_ass
❤145🫡24👍6
S2赛季一周时间直接光速结束...S3筹备中 [树洞频道] @ymsd8 接受纯文本投稿 [夜聊群] 话题聊天群 [闪图机器人] 每日热榜超火爆
😭931🫡110🤬31🤣19❤13😢12🕊9😁7
YM银梦日报:叮!现已开启全新 S2 赛季! @ymtgtgbot @ym_ass
😭256🥰70❤23🤣15🔥12😁3🥱1
@ymtgtgbot (投稿bot) 叮!恭喜宿主觉醒了"银梦投稿系统"! 叮!现已开启全新 S2 赛季!
❤41👏9
是的,又又又又炸了... 大频道可能得缓几天了🥹 这里是 [树洞频道] @ymsd8 可以接受纯文本投稿 还有 [夜聊群] 现在有托管机器人,几乎完全自治化了,欢迎到夜聊玩
😭423🤣14😢10❤9🖕6🕊5👏2
⛩ YM 夜聊 ⛩ 里区 v3 *一般情况会直接通过,如果卡了稍等管理处理。 回家: @ym_ass 管理: @ymg_rp_bot
😭92❤40🫡19👏5😁4✍3👎2🔥2
里区又又又升级了。🫥
😭122❤5
【YM 银梦日推】 美女帅哥,新频道了解一下~ 回家: @ym_ass | 管理: @ymg_rp_bot
🫡179🤗35❤23🔥2
是的,频道也炸了…… 想聊天的到夜聊群吧,频道重建的事得琢磨下怎么搞。 😞
😭687😢38❤22💔1🤣1
Showing the 12 most recent of 22 posts we hold for @ym_ass. 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 — 99,571 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.
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.
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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 25 August 2026 — this entry's latest reading, not the date you are reading this.
“🍑 YM 夏夜 の 淫梦 🍑 中转” (@ym_ass), 58,676 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/ym_ass.
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.