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

Bot

Ai搜索 @AiSS 中文搜索

@aiss

2 usernames

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

31,758monthly users

-119,526 since we began measuring on 7 August 2026

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

Register entry

Telegram ID8464663918
TypeBot
Usernames@aiss @sosuo66bot
First recorded13 August 2026
Last confirmed live25 August 2026
Measurements held17
Confirmed unchanged1 time, most recently 25 August 2026
On Telegramt.me/aiss

Growth

31,758151,28491,5217 August 2026 — 151,284 monthly users8 August 2026 — 125,423 monthly users9 August 2026 — 49,327 monthly users10 August 2026 — 35,242 monthly users12 August 2026 — 34,904 monthly users13 August 2026 — 34,904 monthly users14 August 2026 — 34,997 monthly users14 August 2026 — 34,889 monthly users15 August 2026 — 34,889 monthly users16 August 2026 — 34,339 monthly users16 August 2026 — 34,339 monthly users19 August 2026 — 33,131 monthly users19 August 2026 — 33,131 monthly users22 August 2026 — 32,530 monthly users23 August 2026 — 32,530 monthly users24 August 2026 — 31,758 monthly users25 August 2026 — 31,758 monthly users7 August 202625 August 2026
17 measurements spanning 17 days, net -119,526. 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 13,829–169,213 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
25 Aug 2026, 04:0731,758no change
24 Aug 2026, 19:5331,758-772
23 Aug 2026, 08:2332,530no change
22 Aug 2026, 05:2532,530-601
19 Aug 2026, 21:5733,131no change
19 Aug 2026, 17:1833,131-1,208
16 Aug 2026, 22:2834,339no change
16 Aug 2026, 16:0834,339-550
15 Aug 2026, 18:0334,889no change
14 Aug 2026, 23:2734,889-108
14 Aug 2026, 06:1634,997+93
13 Aug 2026, 18:5234,904no change
12 Aug 2026, 12:4734,904-338
10 Aug 2026, 15:3135,242-14,085
9 Aug 2026, 13:2149,327-76,096
8 Aug 2026, 11:25125,423-25,861
7 Aug 2026, 23:01151,284first 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 25 August 2026 — this entry's latest reading, not the date you are reading this.

“Ai搜索 @AiSS 中文搜索” (@aiss), 31,758 monthly users as measured 25 August 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.