Telegram RegisterThe public register of Telegram

Bot

双向机器人-自定义制作

@sxBot

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

112,582monthly users

+6,192 since we began measuring on 6 August 2026

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

Register entry

Telegram ID1735123423
TypeBot
Username@sxBot
First recorded9 August 2026
Last confirmed live13 August 2026
Measurements held6
Confirmed unchanged2 times, most recently 13 August 2026
On Telegramt.me/sxBot

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 10 August 2026 and assigned it the closest of 31 fixed categories, at 92% 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

106,390112,582109,4866 August 2026 — 106,390 monthly users6 August 2026 — 108,633 monthly users9 August 2026 — 109,670 monthly users9 August 2026 — 109,670 monthly users11 August 2026 — 111,975 monthly users12 August 2026 — 112,582 monthly users6 August 202612 August 2026
6 measurements spanning 5 days, net +6,192. 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 105,461–113,511 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
12 Aug 2026, 00:42112,582+607
11 Aug 2026, 00:54111,975+2,305
9 Aug 2026, 19:23109,670no change
9 Aug 2026, 02:51109,670+1,037
6 Aug 2026, 23:57108,633+2,243
6 Aug 2026, 20:15106,390first 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 34 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“双向机器人-自定义制作” (@sxBot), 112,582 monthly users as measured 12 August 2026. Telegram Register, tgregister.com/channel/sxBot.

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.