Telegram RegisterThe public register of Telegram
Telegram profile photo for Ai搜索 @AiSS 中文搜索

Bot

Ai搜索 @AiSS 中文搜索

@aiss

2 usernames

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

17,251monthly users

-134,033 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 ID8464663918
TypeBot
Usernames@aiss @sosuo66bot
First recorded13 August 2026
Last confirmed live30 October 2026
Measurements held62
Confirmed unchanged5 times, most recently 30 October 2026
On Telegramt.me/aiss

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 62% 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 the other topics.

Growth

16,625151,28483,954.517,2517 August 202628 October 2026
62 measurements spanning 82 days, net -134,033. 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”.
Measurement log — every monthly users count we have recorded, most recent 20 of 62
Measured (UTC)Monthly usersChange
28 Oct 2026, 16:0917,251no change
28 Oct 2026, 04:3717,251+442
26 Oct 2026, 12:4016,809no change
26 Oct 2026, 09:1616,809+184
24 Oct 2026, 15:2716,625no change
24 Oct 2026, 08:5116,625-70
23 Oct 2026, 15:0916,695no change
23 Oct 2026, 12:1616,695-105
22 Oct 2026, 13:4416,800no change
21 Oct 2026, 07:3916,800-191
20 Oct 2026, 04:0516,991no change
20 Oct 2026, 02:3116,991-215
18 Oct 2026, 06:1817,206no change
17 Oct 2026, 19:5617,206-387
15 Oct 2026, 00:4917,593no change
14 Oct 2026, 17:1717,593-100
13 Oct 2026, 18:4117,693no change
13 Oct 2026, 09:0817,693-323
10 Oct 2026, 00:4118,016no change
9 Oct 2026, 06:4218,016first reading

Engagement

No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.

Mentions

Named by 3 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.

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

“Ai搜索 @AiSS 中文搜索” (@aiss), 17,251 monthly users as measured 28 October 2026. Telegram Register, tgregister.com/channel/aiss.

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.