Telegram RegisterThe public register of Telegram
Telegram profile photo for 子清 通知

Channel

子清 通知

@ksqxszq

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

1,931subscribers

-38 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1001874492940
TypeChannel
Username@ksqxszq
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live18 September 2026
Measurements held13
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/ksqxszq

Topic

Giveaways & airdrops — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 49% 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

1,9311,9691,9509 August 2026 — 1,969 subscribers9 August 2026 — 1,968 subscribers12 August 2026 — 1,964 subscribers15 August 2026 — 1,961 subscribers18 August 2026 — 1,959 subscribers22 August 2026 — 1,954 subscribers25 August 2026 — 1,952 subscribers29 August 2026 — 1,948 subscribers1 September 2026 — 1,946 subscribers4 September 2026 — 1,945 subscribers10 September 2026 — 1,936 subscribers14 September 2026 — 1,939 subscribers18 September 2026 — 1,931 subscribers9 August 202618 September 2026
13 measurements spanning 40 days, net -38. 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 1,925–1,975 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 19:561,931-8
14 Sept 2026, 08:561,939+3
10 Sept 2026, 10:391,936-9
4 Sept 2026, 21:401,945-1
1 Sept 2026, 06:031,946-2
29 Aug 2026, 02:561,948-4
25 Aug 2026, 18:061,952-2
22 Aug 2026, 15:531,954-5
18 Aug 2026, 23:321,959-2
15 Aug 2026, 13:271,961-3
12 Aug 2026, 06:561,964-4
9 Aug 2026, 15:311,968-1
9 Aug 2026, 08:311,969first reading

Engagement

20 posts held, back to 12 September 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 20 posts for this entry, the most recent from 23 November 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

80 reactions across 18 posts, in 7 distinct kinds. The most used accounts for 36.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍2936.3%
2126.3%
👎1417.5%
👌911.3%
🌚33.75%
🤮33.75%
😭11.25%

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 18 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 80 reactions 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 12 September 2025 to 23 November 2025, 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

23 Nov 2025, 03:19 UTC≈1,580 views6 reactionsread 9 August 2026

早期项目分享!~(速做) 项目 @PlayBabylon4 由知名创始人(ai16z 和 ElizaOS 创始人 Shaw)发起 目前可以申请白名单位置!~ 访问:https://babylon.market/?ref=ziqing 使用 farcaster 或 gmail 登录

5👎1

16 Nov 2025, 07:56 UTC≈1,690 views1 reactionsread 9 August 2026

https://x.com/qklxsqf/status/1989965322728976475?s=20

👎1

30 Oct 2025, 03:35 UTC≈1,710 views3 reactionsread 9 August 2026

这个也不知道会不会给测试网,不是钱包登陆的就绑定一下吧

👌2👎1

30 Oct 2025, 03:34 UTC≈1,540 views4 reactionsread 9 August 2026
Photo

KITE AI 绑定 EOA 钱包 这是资格的强制要求 正在工作的人务必设置 EOA 钱包! 点击 EOA 后,您将看到钱包连接选项!

👌3👎1

29 Oct 2025, 12:24 UTC≈1,210 views4 reactionsread 9 August 2026

Tea-fi 方糖空投资格检查,我没资格 https://app.tea-fi.com/eligibility

🌚3👎1

28 Oct 2025, 14:45 UTC≈1,180 views4 reactionsread 9 August 2026

手机小狐狸更新到最新版本,然后把链接放浏览器里再打开,下一步下一步下一步,就可以填验证码啦 小狐狸邀请链接🔗 https://link.metamask.io/rewards?referral=8HRE98邀请码 8HRE98 填码直接领500积分 小狐狸手续费极高,0.9%,而且要速刷,慢的话就亏了,24小时积分翻倍,超时就没有了,所以要刷,就要一次刷到7级

2👎2

24 Oct 2025, 00:11 UTC≈1,170 views5 reactionsread 9 August 2026

375ai 可以检查空投了 查看你的 $EAT 分配,准备主网启动: http://eat.375ai.foundation

👌4👎1

26 Sept 2025, 11:26 UTC≈1,380 views7 reactionsread 9 August 2026
Photo

没激励搞什么测试网排名

👍4👎2😭1

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

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.

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

“子清 通知” (@ksqxszq), 1,931 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/ksqxszq.

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.