Telegram RegisterThe public register of Telegram
Telegram profile photo for QNotified

Channel

QNotified

@QNotified

On this record: Topic · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

6,761subscribers

-90 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001488713790
TypeChannel
Username@QNotified
Created27 July 2020measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live11 September 2026
Measurements held13
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/QNotified

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 71% 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

6,7616,8516,8067 August 2026 — 6,851 subscribers7 August 2026 — 6,851 subscribers8 August 2026 — 6,848 subscribers11 August 2026 — 6,842 subscribers14 August 2026 — 6,833 subscribers18 August 2026 — 6,825 subscribers20 August 2026 — 6,817 subscribers24 August 2026 — 6,805 subscribers27 August 2026 — 6,799 subscribers30 August 2026 — 6,789 subscribers2 September 2026 — 6,777 subscribers6 September 2026 — 6,769 subscribers11 September 2026 — 6,761 subscribers7 August 202611 September 2026
13 measurements spanning 35 days, net -90. 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 6,748–6,865 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 10:016,761-8
6 Sept 2026, 08:186,769-8
2 Sept 2026, 10:086,777-12
30 Aug 2026, 13:236,789-10
27 Aug 2026, 19:256,799-6
24 Aug 2026, 19:046,805-12
20 Aug 2026, 23:056,817-8
18 Aug 2026, 08:446,825-8
14 Aug 2026, 23:366,833-9
11 Aug 2026, 06:536,842-6
8 Aug 2026, 04:136,848-3
7 Aug 2026, 04:306,851no change
7 Aug 2026, 04:266,851first reading

Engagement

12 posts held, back to 27 July 2020the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 12 pages of 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 12 posts for this entry, the most recent from 21 April 2024. An engagement rate over an empty window would be a number about nothing.

Recent posts

21 Apr 2024, 04:31 UTC≈12,900 viewsread 20 August 2026

https://t.me/QAuxiliary/273 强烈谴责,严正抗议,勿谓言之不预! 任何邪恶的咕咕华终将被 QNotified 开发组绳之以法。 震惊!QAuxilixy 紧急闭源的原因竟然是......

10 Apr 2024, 12:07 UTC≈11,600 viewsread 20 August 2026
Forwarded from @QAuxiliaryPhoto

不知不觉距离 QNotified 的第一个正式版本发布已经过去五年了 而当初让我如此上头以至于需要 "notify" 的那个人到现在也早已淡出记忆了

1 Apr 2024, 11:07 UTC≈14,700 viewsread 20 August 2026

https://t.me/QAuxiliary/263 致所有 QNotified 用户: 相信大家已经知道了,QAuxilixy 即将改为闭源并停止公开发布这个沉痛的消息。 不要悲伤,不要心急,我去帮你们把他们的源码偷出来,后续会在 QNotified 仓库继续发布。 QNotified 项目组 2024.4.1

9 Jan 2024, 03:09 UTC≈23,100 viewsread 20 August 2026

通知 经 QNotified 开发组全体会议讨论,中央委员会审阅通过,主席团签署。QNotified 中央决定强烈建议 QAuxiliary 继续更新。 附件1: https://t.me/QAuxiliary/237 QNotified 2024.01

1 Sept 2022, 10:44 UTC≈38,700 viewsread 20 August 2026
Forwarded from @MaiTungTM_Notes

你应该时不时往 QN 频道发点东西

28 Jan 2022, 17:43 UTC≈53,800 viewsread 20 August 2026
Forwarded from @QNotified_CIBuildsFile

QNotified (nil.nadph.qnotified) New Version 1.0.1.40e313e(1643390479) available Build ID: 477 Time: 2022-01-28T17:27:17.361Z 稳定性优化,修复大量可能导致闪退的问题 #QNotified更新 #unstable

11 Nov 2021, 16:03 UTC≈51,200 viewsread 20 August 2026

针对 Telegram 投放广告的声明 Telegram 已于近日开始投放广告,作为频道的一条推送消息存在,暂时无法关闭或隐藏。 如果您读到包含”toncoin“等内容,且右下角为 sponsored 、赞助、广告 内容的信息,皆为 Telegram 投放,与本频道无关。目前频道管理员无法关闭,请仔细甄别,谨防上当受骗。

19 Oct 2021, 08:38 UTC≈53,300 viewsread 20 August 2026

提示 Virtual Xposed / Taichi 官方群组已于近日解散,原群组 ID @vxp_group 目前已被身份不明人士抢注。 新群组非 Virtual Xposed / Taichi 官方人士运营,请勿相信该群组以「太极官方」名义发布的任何信息。 #慢讯 #太极 #公告

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

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.

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,822
Telegram ranks this channel #20 of 58 here — alongside 57 others — read 12 September 2026
哔哩漫游
@biliroaming · 56,179
Telegram ranks this channel #31 of 50 here — alongside 49 others — read 12 September 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 11 September 2026 — this entry's latest reading, not the date you are reading this.

“QNotified” (@QNotified), 6,761 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/QNotified.

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.