Telegram RegisterThe public register of Telegram
Telegram profile photo for FunProject

Channel

FunProject

@QToolCI

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

49,485subscribers

+773 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001722417051
TypeChannel
Username@QToolCI
Description此为版本更新频道 聊天群组: @QToolC 表情包转换机器人: @QToolHelperBot
Created5 May 2022 — measured — dated from the channel’s first post
First recorded6 August 2026
Last confirmed live26 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/QToolCI

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 21 August 2026 and assigned it the closest of 31 fixed categories, at 46% 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 why it has no browse page of its own yet.

Growth

48,71249,48549,098.56 August 2026 — 48,712 subscribers7 August 2026 — 48,748 subscribers8 August 2026 — 48,757 subscribers9 August 2026 — 48,768 subscribers10 August 2026 — 48,809 subscribers11 August 2026 — 48,811 subscribers12 August 2026 — 48,825 subscribers14 August 2026 — 48,844 subscribers15 August 2026 — 48,881 subscribers16 August 2026 — 48,910 subscribers18 August 2026 — 49,025 subscribers19 August 2026 — 49,097 subscribers20 August 2026 — 49,134 subscribers21 August 2026 — 49,163 subscribers22 August 2026 — 49,210 subscribers24 August 2026 — 49,265 subscribers25 August 2026 — 49,278 subscribers26 August 2026 — 49,306 subscribers27 August 2026 — 49,324 subscribers28 August 2026 — 49,341 subscribers29 August 2026 — 49,351 subscribers30 August 2026 — 49,366 subscribers31 August 2026 — 49,363 subscribers1 September 2026 — 49,371 subscribers2 September 2026 — 49,369 subscribers3 September 2026 — 49,390 subscribers6 September 2026 — 49,406 subscribers9 September 2026 — 49,418 subscribers11 September 2026 — 49,430 subscribers13 September 2026 — 49,451 subscribers15 September 2026 — 49,454 subscribers17 September 2026 — 49,469 subscribers19 September 2026 — 49,454 subscribers26 September 2026 — 49,485 subscribers6 August 202626 September 2026
34 measurements spanning 51 days, net +773. 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 48,596–49,601 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
26 Sept 2026, 15:0049,485+31
19 Sept 2026, 16:5649,454-15
17 Sept 2026, 05:1949,469+15
15 Sept 2026, 08:3749,454+3
13 Sept 2026, 16:5949,451+21
11 Sept 2026, 19:1649,430+12
9 Sept 2026, 09:5649,418+12
6 Sept 2026, 01:5549,406+16
3 Sept 2026, 19:1649,390+21
2 Sept 2026, 12:1449,369-2
1 Sept 2026, 09:3549,371+8
31 Aug 2026, 08:5549,363-3
30 Aug 2026, 06:1849,366+15
29 Aug 2026, 09:1649,351+10
28 Aug 2026, 09:4249,341+17
27 Aug 2026, 06:3849,324+18
26 Aug 2026, 08:1949,306+28
25 Aug 2026, 05:0549,278+13
24 Aug 2026, 02:2449,265+55
22 Aug 2026, 08:5849,210first reading

Engagement

25 posts held, back to 5 May 2022 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 107 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
27.4%
avg views ÷ 49,485 subscribers
Avg views / post
13,600
8 posts measured
Reaction rate
0.388%
reactions ÷ views · ER floor
Posts in window
8
of 25 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 24 September 2026
Posts held25 (5 May 2022 – 24 September 2026)
Views total108,640
Reactions total421
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Sept 2026, 18:26 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

Links
1

Lifetime counters from Telegram’s own channel header, read 27 September 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,756 reactions across 23 posts, in 25 distinct kinds. The most used accounts for 31.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤85531.0%
👍78728.6%
🥰45616.5%
🎉1846.68%
😁1154.17%
😱812.94%
😭632.29%
🤪431.56%
🫡411.49%
🤔341.23%
👏250.907%
🔥210.762%
🐳100.363%
😇80.29%
🗿70.254%
😘70.254%
🆒40.145%
🤬40.145%
⚡30.109%
❤‍🔥20.073%
5 further kinds60.218%

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

Measured over the 25 most recent posts we hold, published 5 May 2022 to 24 September 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

24 Sept 2026, 16:26 UTC≈5,540 views69 reactionsread 27 September 2026
File

模块架构修改,尝试修复一些存在的BUG,可能新增更多存在的BUG

👍47😁10❤7🤔4💋1

19 Sept 2026, 14:45 UTC≈11,400 views62 reactionsread 27 September 2026
File

修复一些存在的BUG

👍47🤔8❤7

18 Sept 2026, 15:31 UTC≈12,900 views54 reactionsread 27 September 2026
File

修复一些存在的问题

👍33❤12🤔9

17 Sept 2026, 16:46 UTC≈14,000 views35 reactionsread 27 September 2026
File

1.适配微信8076+在表情面板发送消息的时候支持带上引用消息 2.修复微信聊天聚合丢失预览的问题

👍33❤2

16 Sept 2026, 15:15 UTC≈15,000 views44 reactionsread 27 September 2026
File

1.修复SAF 的IO问题 2.优化UI 3.修复反混淆的版本判断问题

👍29❤7🥰4😁3🔥1

15 Sept 2026, 16:01 UTC≈16,300 views57 reactionsread 27 September 2026
File

1.修复特定情况下的闪退问题 2.优化部分界面的显示效果 3.尝试修复发送消息时Session错误的问题

👍46🆒4❤3🐳2🤔1😁1

14 Sept 2026, 16:35 UTC≈17,100 views22 reactionsread 27 September 2026

该版本的反馈意见/BUG在这条消息评论区回复

👍19❤2🥰1

14 Sept 2026, 16:27 UTC≈16,400 views78 reactionsread 27 September 2026
File

[测试版本] 1.修复一些存在的问题,添加更多存在的问题 2.修改UI,使其变得更丑 3.优化模块性能,降低模块使用的流畅度

👍47😁11❤8😱8🔥3🤩1

19 Aug 2026, 07:39 UTC≈34,000 views200 reactionsread 27 September 2026

由于FunBox服务器访问量增大,导致晚高峰网络严重卡顿,国内价格适当的机器已无法满足目前网络需求,已重新将所有服务迁移到海外 经线路调整后大部分用户应该没啥问题,如果少部分用户遇到地区屏蔽无法访问的问题,请自行搭建梯子使用,如果需要分流,分流如下地址 https://opt.dtproj.top

👍96🫡41❤34😭21👏3🤔3👌2

17 Aug 2026, 11:00 UTC≈54,400 views79 reactionsread 27 September 2026
File

SSAID查看和修改小工具,需要root,修改后重启手机生效,最好清除App数据

👍59❤19😁1

17 Aug 2026, 03:25 UTC≈33,200 views67 reactionsread 27 September 2026

对于风险设备,即清除数据后登录时验证码提示的是风险设备需要验证,然后容易掉线的,修改App的SSAID后再清除数据可能有奇效

👍47❤8😇8👏4

17 Aug 2026, 02:52 UTC≈32,600 views104 reactionsread 27 September 2026
File

适配抖音390900,4000000,修复其他的一些BUGGGGGGGGGGG

😱73👍15❤8🎉4🔥4

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

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

橘橘橘子汁 & 🍊
@microblock_pub · 15,261
#1
QAuxiliary CI Builds
@QAuxiliary_CI · 19,541
#2
NPatch
@NPatch · 19,080
#3
QQ Updates
@QQUpdates · 10,203
#4
QQ/TIM Update Log
@qq_updatelog · 6,797
#5
5ec1cff
@real5ec1cff · 37,318
#6
HyperCeiler | Canary Test
@cemiuiler_canary · 19,046
#7
Voyager HyperOS Update
@VoyagerMIUIUpdate · 21,528
#8
Real Nullptr
@nullptr_dev · 20,269
#9
TSBattery CI Builds
@TSBattery_CI · 3,599
#10
YuKongA | Channel
@YuKongA13579 · 8,899
#11
AdClose Official
@AdClose · 12,205
#12
Freedom+
@FreedomPlugin · 9,007
#13
WeChat Update Log
@wechat_updatelog · 5,953
#14
InstallerX
@InstallerX · 8,756
#15
FlClash Channel
@FlClash · 47,123
#16
在花🎗️科技圈
@zaihuapd · 283,183
#17
YunJava
@YunJava · 4,562
#18
QAuxiliary
@QAuxiliary · 44,820
#19
Kimmy's 公开备忘录
@KimmyXYC_Soliloquize · 1,535
#20
𝐄𝟓 𝟖𝟔 𝟗𝟓
@e58695 · 3,449
#21
HyperCeiler | Release & Notice
@cemiuiler_release · 26,729
#22
Thanox Release
@thanoxrel · 3,101
#23
盐酸乙酰胆碱
@teb1e · 525
#24
AWAvenue Ads Rule
@AWAvenueAdsRule · 3,891
#25
2.5次元日常 🍉
@acgdaily · 16,665
#26
ONPatch
@onpatch · 4,608
#27
Zzz Backup
@Genshin_Backup · 341
#28
Serendipity
@lei_Serendipity · 7,067
#29
爱玩机工具箱(文件/通知)
@aiwanji · 8,491
#30
ColorOS Pro
@colorospro · 2,675
#31
RandomFree
@c001apk · 6,704
#32
LSPosed
@LSPosed · 194,124
#33
康娜酱酱酱
@K0bayashi_Kanna · 3,271 (as read 12 September 2026)
#34
企业级欢乐花园
@MaterialDesign3 · 9,185
#35
Sakion Team
@Sakion_Team · 1,966
#36
XiReiki
@xiayinlily · 2,863
#37
LibChecker CI
@libchecker_ci · 3,525
#38
akashaProxy ci channel
@akashaProxy · 1,760
#39
柒柒的鱼骨头
@Sandrone0721 · 1,102
#40
炸虾🍤
@zhaxia_cn · 12,550
#41
哔哩哔哩 表情/装扮 存档
@Bilibili_skin · 12,949
#42
风向旗参考快讯
@xhqcankao · 163,238
#43
Bilibili Android Apk w/ HD
@bilibili_apk · 4,074
#44
蓝点网订阅频道
@landiansub · 45,199
#45
不要糖醋放椒盐
@saltplayerupdate · 17,286
#46
Nagram Tips
@NagramTips · 46,239
#47
Yummy 😋
@GodlyNews1 · 69,298
#48
LuckyTool
@LuckyTool · 28,572
#49
Nagram
@nagram_channel · 68,755
#50
Nullgram
@NullgramClient · 8,450
#51

Read from Telegram’s recommendation API, most recently 12 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

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.

QAuxiliary
@QAuxiliary · 44,820
Telegram ranks this channel #8 of 58 here — alongside 57 others — read 12 September 2026
哔哩漫游
@biliroaming · 56,222
Telegram ranks this channel #20 of 50 here — alongside 49 others — read 12 September 2026
HyperCeiler | Release & Notice
@cemiuiler_release · 26,729
Telegram ranks this channel #20 of 51 here — alongside 50 others — read 12 September 2026
LuckyTool
@LuckyTool · 28,572
Telegram ranks this channel #35 of 56 here — alongside 55 others — read 12 September 2026

This channel appears in 4 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 26 September 2026 — this entry's latest reading, not the date you are reading this.

“FunProject” (@QToolCI), 49,485 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/QToolCI.

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.