Telegram RegisterThe public register of Telegram
Telegram profile photo for 新币搜索 xbss🔍中文搜索

Bot

新币搜索 xbss🔍中文搜索

@xbss_bot

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

67,458monthly users

-153,985 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 ID8260682861
TypeBot
Username@xbss_bot
First recorded7 August 2026
Last confirmed live2 September 2026
Measurements held7
Confirmed unchanged2 times, most recently 2 September 2026
On Telegramt.me/xbss_bot

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

67,458231,049149,253.57 August 2026 — 221,443 monthly users7 August 2026 — 221,443 monthly users11 August 2026 — 230,972 monthly users17 August 2026 — 231,049 monthly users24 August 2026 — 231,002 monthly users27 August 2026 — 87,278 monthly users1 September 2026 — 67,458 monthly users7 August 20261 September 2026
7 measurements spanning 25 days, net -153,985. 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 42,919–255,588 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
1 Sept 2026, 11:1767,458-19,820
27 Aug 2026, 14:1787,278-143,724
24 Aug 2026, 16:56231,002-47
17 Aug 2026, 15:45231,049+77
11 Aug 2026, 01:52230,972+9,529
7 Aug 2026, 18:45221,443no change
7 Aug 2026, 03:15221,443first 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 4 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 1 September 2026 — this entry's latest reading, not the date you are reading this.

“新币搜索 xbss🔍中文搜索” (@xbss_bot), 67,458 monthly users as measured 1 September 2026. Telegram Register, tgregister.com/channel/xbss_bot.

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.