Telegram RegisterThe public register of Telegram

Channel

QAuxiliary

@QAuxiliary

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Polls · Citations · Cite this entry

44,822subscribers

+31 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001645769141
TypeChannel
Username@QAuxiliary
DescriptionQAuxiliary 频道 CI 构建发布频道 @QAuxiliary_CI 群组 https://t.me/+KyMD8cherUdmOTFl GitHub https://github.com/cinit/QAuxiliary 发布评论消息前请先加入群组。 有问题请先阅读置顶。 #版本发布 #频道通知 #使用指南
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/QAuxiliary

Growth

44,79144,82744,8097 August 2026 — 44,791 subscribers7 August 2026 — 44,803 subscribers8 August 2026 — 44,812 subscribers9 August 2026 — 44,817 subscribers10 August 2026 — 44,827 subscribers11 August 2026 — 44,820 subscribers12 August 2026 — 44,822 subscribers44,8227 August 202612 August 2026
7 measurements spanning 6 days, net +31. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 44,786–44,832 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 19:2444,822+2
11 Aug 2026, 22:2644,820-7
10 Aug 2026, 20:4744,827+10
9 Aug 2026, 20:1144,817+5
8 Aug 2026, 20:0644,812+9
7 Aug 2026, 23:0344,803+12
7 Aug 2026, 04:3144,791first reading

Engagement

10 posts held, back to 20 August 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 17 pagesof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 10 posts for this entry, the most recent from 1 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
11
Links
39

Lifetime counters from Telegram’s own channel header, read 12 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.

Reaction mix

2,136 reactions across 7 posts, in 26 distinct kinds. The most used accounts for 41.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
87941.2%
🥰58227.2%
👍31014.5%
🤯1306.09%
😭602.81%
😱462.15%
👌351.64%
🫡180.843%
🤬150.702%
😢120.562%
🤔100.468%
🌭60.281%
😍60.281%
🥴50.234%
❤‍🔥30.14%
💯30.14%
🔥30.14%
20.094%
👎20.094%
💅20.094%
6 further kinds70.328%

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 7 of the 10 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,136reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 10 most recent posts we hold, published 20 August 2025 to 1 July 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 Stars

Stars received
7
across the posts below
Posts paid on
1
of 7 we hold a reading for · 14%
Most on one post
7
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @QAuxiliary. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 10 most recent posts we hold for this entry, published 20 August 2025 to 1 July 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

1 Jul 2026, 07:55 UTC≈18,100 views236 reactionsread 12 August 2026

#频道通知 #Announcement 提示 QAuxiliary 从 CI 3008 开始移除了 arm32 版本的构建产物。如果您仍然需要使用 32 位版本的 QAuxiliary,请使用 armAll 或 universal 版本(这两个版本仍然包含 armeabi-v7a 的原生库)。 QAuxiliary 2026.07.01

👍189👌2012🥴5🤔3🥰3❤‍🔥2😱2

30 Jun 2026, 12:20 UTC≈19,500 views198 reactionsread 12 August 2026
File

QAuxiliary v1.6.1 更新日志 - 线上问题修复 - 用户体验优化 新增功能 - 篡改预览字体大小 - 禁用QQ秀功能 - 隐藏QQ空间广告 - 篡改上传运动步数 - 禁用子渠道发送通知 - 禁用通知气泡 - 显示空间动态 - 随机气泡 - @列表重新排序 - 禁用左滑回复震动 - 自定义表情面板列数 修复功能 - 防撤回 - 允许上传透明头像和表情 - 隐藏表情表态 - 移除消息表态 - 移除消息列表顶栏横幅广告 - 强制平板模式 - 强制手机模式 - 消息+1 Plus - 禁用特定消息触发的交互式弹窗 - 禁用崩溃日志上报 - 可选使用系统相册 - 修改 DPI - 模块设置入口 - 去除转发9名联系人限制 - 强制使用默认字体 - 移除表情回应限制 - 小程序分享转链接(接收) - 卡片消息文本化 - 自定义启动图 温馨提示 - 目前 QQ 风控严重,仅建议仍在使用模块的用户更新。请用户自行

🤯94👍5046🥰7🐳1

18 Mar 2026, 04:29 UTC≈47,300 views61 reactionsread 12 August 2026
Poll

是否去除 arm32 二进制构建? 如题,从 CI 和 release 去除 arm32 artifact, 仅保留 arm64、armAll 和 universal 构建产物. 对于 arm32 用户请使用 armAll 或 universal 构建。

  1. 支持66%
  2. 反对4%
  3. 30%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

57👍4

16 Mar 2026, 16:00 UTC≈44,200 views253 reactionsread 12 August 2026

#频道通知 #Announcement 提示 QAuxiliary 从 CI 8330 开始支持 libxposed API 101, 目前 QAuxiliary 对 API 101 的支持是实验性的,仍然处于测试阶段。 本模块仍然保留对经典 Xposed API 51+ 及 libxposed API 100 的支持,您仍然可以在任何支持经典 Xposed API 51+ 或 libxposed API 100 的框架上正常使用 QAuxiliary。 QAuxiliary 2026.03.16

🥰19440🫡11💯3🔥3🎉1👎1

15 Feb 2026, 12:08 UTC≈59,500 views331 reactionsread 12 August 2026
File

QAuxiliary v1.6.0 祝大家新年快乐! 更新日志 - 线上问题修复 用户体验优化 新增功能 - 设备类型修改 - 通知渠道管理 - 聊天照片分享增强 - AlertDialog 使用 QQ toast 同款模糊背景 - 令卡片分享消息可点击并进入 - 隐藏QQ空间VIP - TIM 我的添加频道入口 - 允许发送收藏的语音 - 语音消息自动转文本 - 强制显示资料卡内所有设置 - 输入框长按切换加号菜单 - 伪装权限 - 快捷回拍 - 隐藏表情表态 - 移除引用图片预览限制 - 启用聊天总结 温馨提示 - 目前 QQ 风控严重,仅建议仍在使用模块的用户更新。请用户自行评估使用模块的对自己账号可能造成风控或冻结的风险。 #QAuxiliary #版本发布

283👍18🥰15😍62😱2❤‍🔥1👎1

11 Nov 2025, 10:09 UTC≈70,300 views483 reactionsread 12 August 2026

#频道通知 #Announcement 提示 QAuxiliary 尚未兼容 QQ 9.2.30, 建议大家暂时先不要升级 QQ 9.2.30 QAuxiliary 2025.11.11

315😱42👍35😭32👌15🤬15🥰15🫡7

20 Aug 2025, 15:20 UTC≈112,000 views574 reactions7 Starsread 12 August 2026
File

QAuxiliary v1.5.9 新增功能 - 显示被折叠的消息 - 隐藏群聊风险提醒 - 新版侧滑栏精简 - 提示 NoSeq 消息 - 统一 QQ dialog 样式 - 显示已退群用户的信息 - 屏蔽社交功能限制提醒 - 长按异常功能列表可直接定位功能开关 修复功能 - 表情面板 - 隐藏下拉小程序 - 精简设置菜单 - 修复模块在 QQ 9.2.5 上随机失效的 bug 温馨提示 - 目前 QQ 风控严重,仅建议仍在使用模块的用户更新。请用户自行评估使用模块的对自己账号可能造成风控或冻结的风险。 #QAuxiliary #版本发布

🥰348126🤯35😭28👍14😢9🌭6🤔3

Showing the 10 most recent of 10 posts we hold for @QAuxiliary. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Polls

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.

18 Mar 2026, 04:29 UTCFinal Results6,890 voters approx.

是否去除 arm32 二进制构建? 如题,从 CI 和 release 去除 arm32 artifact, 仅保留 arm64、armAll 和 universal 构建产物. 对于 arm32 用户请使用 armAll 或 universal 构建。

  1. 支持66%
  2. 反对4%
  3. 30%

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 10 most recent posts we hold, published 20 August 2025 to 1 July 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.

Citation-graph rank

Citation-graph rank — 205,698 of 1,160,990entries 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.

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 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.

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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“QAuxiliary” (@QAuxiliary), 44,822 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/QAuxiliary.

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.