明天上学去了有事周末回 9月2号和平更新 周末更新复活项目
👍13🤡1
Signed 七色花大王(周末回)直奔主题

Channel
@QSHNB88
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Polls · Citations · Cite this entry
10,049subscribers
-1,820 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003250955270 |
|---|---|
| Type | Channel |
| Username | @QSHNB88 |
| Created | Between 1 October 2025 and 31 January 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 5 September 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 5 September 2026 |
| On Telegram | t.me/QSHNB88 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Sept 2026, 08:21 | 10,049 | -71 |
| 3 Sept 2026, 10:44 | 10,120 | -277 |
| 2 Sept 2026, 05:06 | 10,397 | -259 |
| 1 Sept 2026, 05:43 | 10,656 | -236 |
| 31 Aug 2026, 04:07 | 10,892 | -310 |
| 30 Aug 2026, 03:36 | 11,202 | -269 |
| 29 Aug 2026, 05:43 | 11,471 | -284 |
| 28 Aug 2026, 05:13 | 11,755 | -157 |
| 27 Aug 2026, 03:26 | 11,912 | -93 |
| 26 Aug 2026, 06:12 | 12,005 | -95 |
| 25 Aug 2026, 05:28 | 12,100 | -175 |
| 24 Aug 2026, 02:29 | 12,275 | -71 |
| 22 Aug 2026, 08:46 | 12,346 | +27 |
| 20 Aug 2026, 21:06 | 12,319 | +40 |
| 19 Aug 2026, 21:52 | 12,279 | +23 |
| 18 Aug 2026, 22:35 | 12,256 | +30 |
| 18 Aug 2026, 00:22 | 12,226 | +24 |
| 16 Aug 2026, 21:36 | 12,202 | +45 |
| 15 Aug 2026, 13:56 | 12,157 | +87 |
| 14 Aug 2026, 03:45 | 12,070 | first reading |
69 posts held, back to 29 July 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 50 pages 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.
| Window | Rolling 30 days · latest post in window 30 August 2026 |
|---|---|
| Posts held | 69 (29 July 2026 – 30 August 2026) |
| Views total | 77,734 |
| Reactions total | 532 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 1 Sept 2026, 20:36 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 6 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.
683 reactions across 69 posts, in 24 distinct kinds. The most used accounts for 67.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 463 | 67.8% | |
| ❤ | 78 | 11.4% | |
| 🔥 | 30 | 4.39% | |
| 🥰 | 24 | 3.51% | |
| 😍 | 19 | 2.78% | |
| 😘 | 14 | 2.05% | |
| 😭 | 13 | 1.90% | |
| 🤓 | 7 | 1.02% | |
| 👎 | 6 | 0.878% | |
| 👏 | 6 | 0.878% | |
| 😁 | 4 | 0.586% | |
| 🥱 | 3 | 0.439% | |
| 🎃 | 2 | 0.293% | |
| 🕊 | 2 | 0.293% | |
| 😎 | 2 | 0.293% | |
| 🤡 | 2 | 0.293% | |
| 🌭 | 1 | 0.146% | |
| 🎉 | 1 | 0.146% | |
| 👾 | 1 | 0.146% | |
| 😡 | 1 | 0.146% | |
| 4 further kinds | 4 | 0.586% |
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 69 of the 69 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 683 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 69 most recent posts we hold, published 29 July 2026 to 30 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.
明天上学去了有事周末回 9月2号和平更新 周末更新复活项目
👍13🤡1
Signed 七色花大王(周末回)直奔主题
🔥七色花小店🔥 新上架了一大批GZ无限授权号/直登号/飞机号,可以去支持一下🔥🔥🔥🔥 基本都是退游号,只要有全程录屏有问题都包售后 ✔️✔️下单地址 https://mvhije.cn/shop/X8LMU2I9
👍9🤡1
Signed 七色花大王(周末回)直奔主题
白号补了 购买地址 https://mvhije.cn/shop/X8LMU2I9
👍5
Signed 七色花大王(周末回)直奔主题
没招了和平9月2号更新 只能等周末回来再复活😭
👍11
Signed 七色花大王(周末回)直奔主题
🔥七色花小店🔥 新上架了一大批GZ无限授权号/直登号/飞机号,可以去支持一下🔥🔥🔥🔥 基本都是退游号,只要有全程录屏有问题都包售后 ✔️✔️下单地址 https://mvhije.cn/shop/X8LMU2I9
👍20
Signed 七色花大王(挂圈皇帝)
Photo, posted without a caption
👍8❤1
Signed 七色花大王(周末回)直奔主题
卡网买不了显示系统异常已修复 另外刷刀助手将会公益到和平下个版本更新也就是开学
👍13❤1😁1
Signed 七色花大王(周末回)直奔主题
你们老说有啥bug 也没啥问题呀 没效果 下载资源扩展和基础 秃头 如果你玩的是全局美化这是正常的,换脸型就行 或者直接玩套装秒刷这样就不会了,如果你玩的是秒刷也会秃头,说明没下载资源 枪皮没效果 也是下载资源
👍11❤2
Signed 七色花大王(周末回)直奔主题
😃😀😃😃😀😃 每次看片打开Tg都要打开绿茶? 卡的要死还容易连接不上 下个文件看个片都要等一辈子? 🤦♂️推荐我自己用的VPN和外面收费的几十几百的几乎一样,看视频也是非常的快,几乎没有卡顿情况 ✅不好用全额退看个视频卡的要死全额退 ‼️虽然这个是免费的但是也是花了我很长时间找到的仅2.88买不了吃亏,买不了上当 卡网https://mvhije.cn/shop/X8LMU2I9
👍13
Signed 七色花大王(挂圈皇帝)
博尔特天花板,我扛了谁来都不好使
👍12❤2
Signed 七色花大王(周末回)直奔主题
新上架的GZ无限授权号大多都是退游号并且都非常质量小长期玩推荐大家可以支持一下
👍4
Signed 七色花大王(周末回)直奔主题
刷刀助手开启公益 卡密@QSHNB88
👍13😍3
Signed 七色花大王(挂圈皇帝)
Showing the 12 most recent of 69 posts we hold for @QSHNB88. 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.
@QSHNB88 edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
要不要送点数据号?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 69 most recent posts we hold, published 29 July 2026 to 30 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
Named by 4 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 5 September 2026 — this entry's latest reading, not the date you are reading this.
“七色花项目主频道『公益』” (@QSHNB88), 10,049 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/QSHNB88.
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.