Channel
@youmiQQ2
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
346subscribers
+35 since we began measuring on 24 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004403510740 |
|---|---|
| Type | Channel |
| Username | @youmiQQ2 |
| Created | Between 1 June 2026 and 3 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 24 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 10 September 2026 |
| On Telegram | t.me/youmiQQ2 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Sept 2026, 12:17 | 346 | -11 |
| 31 Aug 2026, 15:35 | 357 | +18 |
| 25 Aug 2026, 05:34 | 339 | +28 |
| 24 Aug 2026, 10:00 | 311 | first reading |
20 posts held, back to 3 August 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 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 1 of 14 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 24 August 2026 |
|---|---|
| Posts held | 20 (3 August 2026 – 24 August 2026) |
| Views total | 3,096 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 24 Aug 2026, 10:00 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.
Measured directly from 3 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.
2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 50.0% | |
| 🔥 | 1 | 50.0% |
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 3 of the 20 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 3 August 2026 to 24 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.
🎉 优米的半价 🎁 奖品清单 • （@youmiQ1）1p半价 × 1 🛡️ 参与条件 • 加入 惠州出击大队3.0群 • 加入 惠州出击大队2.0群 • 加入 惠州出击大队1.0群 • 加入 惠州公开榜1.0 • 加入 优米的🏠🏠🏠 • 需消耗积分：5 • 必须设置用户名 🔮 祝福加持 • 祝福消耗：100积分 • 祝福上限：无上限次 • 祝福一次增加一个抽奖号，提高中奖率 • 幸运值祝福：支持 幸运值说明 ⌛ 抽选时刻 • 2026-08-27 19:54:00 📜 抽奖说明 刷屏、灌水、纯表情、复制粘贴、无意义对话、撤回内容等，一律视为无效发言，不计入统计！ 再次重申：灌水无意义发言都不兑奖！请用心交流。 活动最终解释权归本群管理团队所有。 中奖的12小时内联系管理员领取 @Ajk1233 24小时内预约时间，72小时内出击，过时自动作废 炸号作废放回奖池重新抽奖 用了优惠劵要写报告！ ✨ 愿命运之剑指引…
14.30有位哦😘
👈知道我再想你吗😘😘😘 15.00有位哦
🔥1
14.00开课哟😘
😂😂😂哪个小哥哥可以过来帮我干掉🦟😭😭 14.00开课哟需要的小哥哥可以提前预约
16.00有为哟
七夕快乐😆😆😆 15.00有位哦
现在有位置啦哦
14.00开课哟，昨天没有预约到的小哥哥，今天可以提前预约
13.00开课哟，头课还在滴😘
秋意绵绵，爱在何方 试问你的爱可否有人感应？ 14.00开课哟
15.00有位😘
Showing the 12 most recent of 20 posts we hold for @youmiQQ2. 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.
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.
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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“（备用）优米的🏠🏠🏠” (@youmiQQ2), 346 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/youmiQQ2.
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.