🎉 【快】产品发布公告|【群管机器人】正式上线 快搜正式推出【群管机器人】👀。 该机器人智能管理 Telegram 群组,支持自动审核、防广告、防刷屏、关键词过滤、欢迎新成员等功能,让群管理更轻松、更高效。 机器人支持 个人或多人协作使用,功能完善、操作简单,并提供多项 多数同类产品没有或需要付费才能使用的功能,且完全免费开放使用,欢迎体验。 完全免费!完全免费!完全免费! 🔥 前往官方频道 🔥 🔥 使用群管机器人 🔥
❤4

Channel
@kuaipd
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
12,538subscribers
+5 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002705755940 |
|---|---|
| Type | Channel |
| Usernames | @kuaiaaa @kuaiaaaa @kuaiaaaaa @kuaiaaaaaa @kuaiaaaaaaa @kuaiaaaaaaaa @kuaipd |
| Created | 26 June 2025 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 47 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/kuaipd |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 18:07 | 12,538 | no change |
| 13 Aug 2026, 16:36 | 12,538 | +2 |
| 13 Aug 2026, 15:46 | 12,536 | -13 |
| 13 Aug 2026, 12:07 | 12,549 | -41 |
| 13 Aug 2026, 00:17 | 12,590 | no change |
| 12 Aug 2026, 22:04 | 12,590 | no change |
| 12 Aug 2026, 21:29 | 12,590 | no change |
| 12 Aug 2026, 19:13 | 12,590 | no change |
| 12 Aug 2026, 16:55 | 12,590 | -2 |
| 12 Aug 2026, 14:06 | 12,592 | -3 |
| 12 Aug 2026, 12:53 | 12,595 | -3 |
| 12 Aug 2026, 00:55 | 12,598 | no change |
| 12 Aug 2026, 00:42 | 12,598 | no change |
| 11 Aug 2026, 22:13 | 12,598 | no change |
| 11 Aug 2026, 22:13 | 12,598 | +14 |
| 11 Aug 2026, 16:03 | 12,584 | no change |
| 11 Aug 2026, 14:28 | 12,584 | +5 |
| 11 Aug 2026, 11:22 | 12,579 | -5 |
| 11 Aug 2026, 03:01 | 12,584 | no change |
| 11 Aug 2026, 01:51 | 12,584 | first reading |
13 posts held, back to 26 June 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 22 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 6 August 2026 |
|---|---|
| Posts held | 13 (26 June 2025 – 6 August 2026) |
| Views total | 3,900 |
| Reactions total | 4 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 03:14 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.
1,250 reactions across 11 posts, in 19 distinct kinds. The most used accounts for 45.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 562 | 45.0% | |
| 👎 | 136 | 10.9% | |
| 💩 | 116 | 9.28% | |
| 👍 | 83 | 6.64% | |
| 😁 | 67 | 5.36% | |
| 💯 | 61 | 4.88% | |
| 🤮 | 56 | 4.48% | |
| 🤡 | 28 | 2.24% | |
| 🔥 | 26 | 2.08% | |
| 🖕 | 24 | 1.92% | |
| 🎉 | 23 | 1.84% | |
| 🤣 | 17 | 1.36% | |
| 🤯 | 16 | 1.28% | |
| 🥰 | 9 | 0.72% | |
| 🤪 | 7 | 0.56% | |
| 😴 | 6 | 0.48% | |
| 👏 | 5 | 0.4% | |
| 🤗 | 5 | 0.4% | |
| 🌚 | 3 | 0.24% |
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 11 of the 13 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 1,250reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 26 June 2025 to 6 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.
🎉 【快】产品发布公告|【群管机器人】正式上线 快搜正式推出【群管机器人】👀。 该机器人智能管理 Telegram 群组,支持自动审核、防广告、防刷屏、关键词过滤、欢迎新成员等功能,让群管理更轻松、更高效。 机器人支持 个人或多人协作使用,功能完善、操作简单,并提供多项 多数同类产品没有或需要付费才能使用的功能,且完全免费开放使用,欢迎体验。 完全免费!完全免费!完全免费! 🔥 前往官方频道 🔥 🔥 使用群管机器人 🔥
❤4
🎉 【快】产品发布公告|【双向机器人】正式上线 快搜正式推出【双向机器人】👀。 该机器人用于在用户与客服之间进行消息转发,能够帮助 被限制私聊的用户顺利联系你,同时也为团队提供 高效的营销与客服管理工具。 机器人支持 个人或多人协作使用,功能完善、操作简单,并提供多项 多数同类产品没有或需要付费才能使用的功能,且完全免费开放使用,欢迎体验。 核心优势: 1️⃣ 完全免费 所有核心功能均免费开放使用。 2️⃣ 消息支持编辑 已发送消息仍可编辑,方便修正内容或补充信息。 3️⃣ 多客服支持 支持多客服协作,并可在 话题群内实现一对一回复,提高客服效率。 4️⃣ 多模式自动回复 支持关键词、规则匹配及 正则表达式自动回复,灵活满足不同场景。 5️⃣ 图文广播功能 支持向所有用户 一键发送图文消息广播,方便营销推广。 6️⃣ 超时未回复告警 当用户消息 长时间未得到回复 时,可通过邮件提醒,避免漏单。 7️⃣ 快捷用…
❤160💩29👎8😁7🖕5🥰4👏2
该频道为 【快】团队官方公告,后续 【快】系列产品信息将在此同步发布: @kuaipd
❤120💯61😁56👍45🎉23💩19🤣14👎13
Channel name was changed to «【快】官方公告»
🎉官方公告|快搜主号恢复使用 各位快搜用户: 感谢大家一直以来的支持与等待! 目前主机器人 @kuai 已全面恢复使用✔️ 与 @kuaiaa 可同时使用,实现数据互通、内容同步,搜索体验不受影响。 我们将陆续把以下账号全部上链,确保服务稳定、安全、可持续: 官方账号矩阵 @kuai @kuaia @kuaiaa @kuaiaaa @kuaiaaaa @kuaiaaaaa @kuaiaaaaaa @kuaiaaaaaaa @kuaiaaaaaaaa 请认准以上唯一官方账号矩阵,防止仿冒。 快搜团队将持续优化,为你带来更快、更准、更全面的搜索体验。 🗣️ 即将发布 全新拉新活动/引擎功能即将上线,敬请期待~
❤116👎36🤮32👍23💩22🖕19🔥17🤯16
7
👎9💩6❤3🤮2👍1
6
👎15💩8❤6👍4🤮2
5
👎10💩4🤮2❤1
4
👎13💩10❤5🤮4👍2
3
❤13👎8💩5🤮4
2
🤡28👎10❤8💩8🤮5🌚3
❗️官方公告|快搜服务不中断 各位快搜用户: 感谢大家一直以来的支持与信任! 官方四字 ID @kuai 被短暂误封。目前申诉已成功,14 天后恢复启用。为确保检索服务连续稳定,请按以下渠道使用: 临时使用 @kuaiaa(已上链,搜索群请临时拉入使用) 搜索机器人(后续全部上链) @kuai @kuaia @kuaiaa @kuaiaaa @kuaiaaaa @kuaiaaaaa @kuaiaaaaaa @kuaiaaaaaaa @kuaiaaaaaaaa 请认准以上唯一官方账号矩阵,谨防仿冒。感谢理解与支持! ❗️针对本次影响: 1. 所有关键词+专页广告加赠半个月,顶部链接底部按钮加赠300万次。 2. 今日拉新+搜索群收益按昨日计算。 3. 全新拉新活动待后续公布。
❤126👎14🔥9👍8💩5🤮5🤗4👏3
Showing the 12 most recent of 13 posts we hold for @kuaipd. 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 — 434,490 of 1,183,361entries 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.
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 2 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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“【快】官方公告” (@kuaipd), 12,538 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/kuaipd.
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.