尾缀「Q」的白丝粉毛红豆泥接入点将于稍后进行升级,升级后将继续沿用尾缀「Q」,而旧有尾缀「Q」节点将更改为尾缀「QL」,并于2026年11月6日后停止接入。

Channel
prprCloud 公告板
@prprclouds
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
6,642subscribers
+77 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001452433390 |
|---|---|
| Type | Channel |
| Username | @prprclouds |
| Description | 交流群: @prprgroup 网站: prpr.96110.cn.com |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/prprclouds |
Topic
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 83% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Nov 2026, 02:27 | 6,642 | +1 |
| 31 Oct 2026, 03:18 | 6,641 | +2 |
| 27 Oct 2026, 18:09 | 6,639 | +4 |
| 24 Oct 2026, 13:40 | 6,635 | +2 |
| 21 Oct 2026, 23:58 | 6,633 | +1 |
| 18 Oct 2026, 08:28 | 6,632 | -9 |
| 15 Oct 2026, 01:38 | 6,641 | +3 |
| 11 Oct 2026, 22:20 | 6,638 | +2 |
| 26 Sept 2026, 05:20 | 6,636 | +5 |
| 17 Sept 2026, 13:16 | 6,631 | +9 |
| 13 Sept 2026, 06:15 | 6,622 | +11 |
| 9 Sept 2026, 18:19 | 6,611 | +55 |
| 4 Sept 2026, 00:57 | 6,556 | +3 |
| 31 Aug 2026, 16:12 | 6,553 | -1 |
| 28 Aug 2026, 23:54 | 6,554 | -1 |
| 25 Aug 2026, 22:03 | 6,555 | +2 |
| 23 Aug 2026, 03:25 | 6,553 | -3 |
| 20 Aug 2026, 01:48 | 6,556 | -5 |
| 17 Aug 2026, 11:29 | 6,561 | -6 |
| 14 Aug 2026, 09:18 | 6,567 | first reading |
Engagement
41 posts held, back to 15 June 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 11 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 22.7%
- avg views ÷ 6,642 subscribers
- Avg views / post
- 1,510
- 19 posts measured
- Reaction rate
- 0.467%
- reactions ÷ views · ER floor
- Posts in window
- 19
- of 41 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 12 of 19 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 4 November 2026 |
|---|---|
| Posts held | 41 (15 June 2026 – 4 November 2026) |
| Views total | 28,639 |
| Reactions total | 86 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 4 Nov 2026, 10:16 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
- Photos
- 214
- Videos
- 11
- Links
- 90
Lifetime counters from Telegram’s own channel header, read 4 November 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.
Reaction mix
302 reactions across 27 posts, in 22 distinct kinds. The most used accounts for 13.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👏 | 40 | 13.2% | |
| 🤣 | 36 | 11.9% | |
| ❤ | 32 | 10.6% | |
| 😱 | 31 | 10.3% | |
| 👍 | 29 | 9.60% | |
| 🍾 | 27 | 8.94% | |
| 🌚 | 17 | 5.63% | |
| 💩 | 13 | 4.30% | |
| 🤬 | 12 | 3.97% | |
| 🤯 | 12 | 3.97% | |
| 💯 | 10 | 3.31% | |
| 🥰 | 7 | 2.32% | |
| 🤓 | 6 | 1.99% | |
| 👎 | 5 | 1.66% | |
| 😢 | 5 | 1.66% | |
| 🤔 | 5 | 1.66% | |
| 😁 | 3 | 0.993% | |
| 🥱 | 3 | 0.993% | |
| 🥴 | 3 | 0.993% | |
| 🌭 | 2 | 0.662% | |
| 2 further kinds | 4 | 1.32% |
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 31 of the 41 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 302 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 41 most recent posts we hold, published 15 June 2026 to 4 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: 10 of 19 posts held from the last 30 days (52.6%) 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).
目前重新上线之美国节点为延迟考虑,地区为西雅图、洛杉矶等地方,如有其他需求欢迎提出
Photo, posted without a caption
已为流量按月重置的用户统一发放一次性流量重置
🥰6
已更新懒人01、懒人02、香港01、香港02、香港03之节点后端作为实验性质测试效果
目前仍在调整节点策略,预计本日内完成。完成后将为剩余节点升级全旧低性能颠簸服务端
稍微延迟一点再维护(好困)
🥱3
可续费的活动套餐现已恢复续费功能
❤3👍1
哈基米流口水N接入点即将进行短暂维护
👍2
本晚将进行节点维护,进一步扩展哈基米流口水N接入点,并引入白丝粉毛红豆泥Q接入点。 完成后将于同日向全体用户发放流量重置。
已重置所有常规套餐服务流量
【网站维护完成】 本站维护已完成,网站已顺滑迁移至新系统,目前可正常访问和使用。如果遇到页面异常、功能问题或其他 Bug,欢迎向我们反馈,我们会尽快排查和修复。 感谢各位在维护期间的耐心等待与理解。
💯10
Showing the 12 most recent of 41 posts we hold for @prprclouds. 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@XFLTDtop · 19,370
Telegram ranks this channel #18 of 48 here — alongside 47 others — read 5 October 2026
@DuyaoSS · 67,317
Telegram ranks this channel #33 of 45 here — alongside 44 others — read 20 August 2026
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“prprCloud 公告板” (@prprclouds), 6,642 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/prprclouds.
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.