Telegram RegisterThe public register of Telegram

Channel

XAutoDaily

@XAutoDaily

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

17,013subscribers

-11 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001474461149
TypeChannel
Username@XAutoDaily
Description「XAutoDaily」公告版 发布模块正式版及模块相关信息 ────── 群组 @XAutoDailyChat
CreatedBetween 1 April 2019 and 31 August 2021— 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/XAutoDaily

Growth

17,01317,02417,018.57 August 2026 — 17,024 subscribers7 August 2026 — 17,024 subscribers8 August 2026 — 17,021 subscribers9 August 2026 — 17,016 subscribers10 August 2026 — 17,015 subscribers11 August 2026 — 17,016 subscribers12 August 2026 — 17,013 subscribers7 August 202612 August 2026
7 measurements spanning 5 days, net -11. 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 17,011–17,026 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 10:2517,013-3
11 Aug 2026, 10:3217,016+1
10 Aug 2026, 09:5517,015-1
9 Aug 2026, 13:1117,016-5
8 Aug 2026, 14:3317,021-3
7 Aug 2026, 18:0017,024no change
7 Aug 2026, 17:5117,024first reading

Engagement

20 posts held, back to 22 December 2023the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 15 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 20 posts for this entry, the most recent from 3 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
3
Links
7

Lifetime counters from Telegram’s own channel header, read 13 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,806 reactions across 20 posts, in 28 distinct kinds. The most used accounts for 29.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍83829.9%
67424.0%
😢40914.6%
🥰32611.6%
😭2639.37%
🔥712.53%
😱521.85%
👏321.14%
🤯311.10%
😁180.641%
💯140.499%
🤔120.428%
🫡100.356%
🎉90.321%
🌚60.214%
🤡60.214%
👎50.178%
🤩50.178%
💊40.143%
🤮40.143%
8 further kinds170.606%

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 20 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,806reactions 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 22 December 2023 to 3 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.

Recent posts

3 Jul 2026, 15:35 UTC≈7,690 views106 reactionsread 13 August 2026
File

XAutoDaily v3.0.37 更新日志 【功能】 - 修复 a16+ 插件加载失败的问题 - 修复 旧版 QQ cookie 获取兼容问题

91🫡10👍2😁2😍1

27 May 2026, 09:26 UTC≈15,300 views87 reactionsread 13 August 2026
File

XAutoDaily v3.0.36 更新日志 【功能】 - 新增 亲密空间任务 - 修复 旧版cookie获取失败的问题 —— by HD。

68🥰11👍4😁2😐2

7 Apr 2026, 10:11 UTC≈24,000 views96 reactionsread 13 August 2026
File

XAutoDaily v3.0.35 更新日志 【功能】 - 新增 王者营地每日任务 - 新增 福利社领卷 - 新增 QQ运动步数 —— by HD。

83👍12🥰1

6 Apr 2026, 17:11 UTC≈21,100 views68 reactionsread 13 August 2026
File

XAutoDaily v3.0.34 更新日志 【功能】 - 新增 频道签到 【体验】 - 适配 新版配置 【问题修复】 - 修复 好友弹窗UI —— by HD。

🥰5312👍2🤗1

11 Mar 2026, 07:38 UTC≈25,600 views100 reactionsread 13 August 2026
File

XAutoDaily v3.0.33 更新日志 【问题修复】 - 修复 v9.2.70 部分功能初始化失败的问题; —— pr by HD。

79🔥10😁4👎3🎃2🤡2

24 Nov 2025, 01:59 UTC≈35,800 views134 reactionsread 13 August 2026
File

XAutoDaily v3.0.32-fix 更新日志 【问题修复】 - 修复 QQ 9.2.30+ 版本模块入口创建失败; - 修复 QQ 9.2.30+ 版本好友列表获取; - 修复 v3.0.32 存在的一个问题; —— pr by HD。

101🥰17💯7👍5🤔4

27 Jul 2025, 07:31 UTC≈41,900 views261 reactionsread 13 August 2026
File

XAutoDaily v3.0.31 更新日志 【问题修复】 - 修复 QQ 9.1.90 及以上版本模块入口创建失败; - 修复 QQ 9.1.95 及以上版本好友列表获取。 PS: 作者已经好久没用模块了,感谢 fusumayuki 的 pr。 #XAutoDaily #版本发布

😭21122🔥15😢5🤮3😁3🥰2

1 Apr 2025, 05:42 UTC≈39,300 views246 reactionsread 13 August 2026
Forwarded from @QAuxiliary

#频道通知 #Announcement 我们有注意到,QQ 在 9.1.65(测试版)加入了更多环境检测,为了您的账号安全,qa 开发组建议您在缓解措施出来之前,非必要不升级此(更高)版本。 QAuxiliary 2025.04.01

😢153😭42👍1816😁7🤯5😱4🔥1

19 Mar 2025, 08:39 UTC≈43,200 views100 reactionsread 13 August 2026
File

XAutoDaily v3.0.30-fix 更新日志 【问题修复】 - 修复 在 QQ v9.1.55 及以上版本中获取 cookie 失败的问题; - 修复 v3.0.30 存在的一个问题; - 其它修复与优化。 #XAutoDaily #版本发布

👍8812

23 Feb 2025, 11:44 UTC≈43,200 views330 reactionsread 13 August 2026

公告 我们注意到,QQ 官方近期为部分签到打卡任务添加了滑块验证,XAutoDaily 在自动执行这些任务时出现报错是正常现象。未来添加滑块验证的签到打卡任务的数量可能会进一步增加,为保障您的签到体验,我们建议您手动执行这些签到打卡任务。 XAutoDaily 2025.02.23

😢251😱33👍31💊4🤡4🤬32🔥2

27 Nov 2024, 15:51 UTC≈48,600 views185 reactionsread 13 August 2026
File

XAutoDaily v3.0.29 更新日志 【问题修复】 - 修复 在 QQ v9.1.20 (8198) 及更高版本中灰度设置界面无法显示模块入口的问题。 #XAutoDaily #版本发布

🥰128👍309😱9🤩5👏4

11 Nov 2024, 16:07 UTC≈45,800 views130 reactionsread 13 August 2026
File

XAutoDaily v3.0.28 更新日志 【问题修复】 - 修复 在 TIM 4.0.95.4001 中入口创建失败的问题。 #XAutoDaily #版本发布

🥰90👍13🤯13😱6👏52🔥1

Showing the 12 most recent of 20 posts we hold for @XAutoDaily. 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

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.

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.

“XAutoDaily” (@XAutoDaily), 17,013 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/XAutoDaily.

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.