Telegram RegisterThe public register of Telegram
Telegram profile photo for BullX Bot

Bot

BullX Bot

@BullXBetaBot

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

12,224monthly users

-2,613 since we began measuring on 6 August 2026

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

Register entry

Telegram ID6932970071
TypeBot
Username@BullXBetaBot
First recorded18 August 2026
Last confirmed live17 November 2026
Measurements held39
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/BullXBetaBot

Topic

Other / unclassifiable — 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 82% 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

12,22417,40714,815.56 August 2026 — 14,837 monthly users8 August 2026 — 15,797 monthly users11 August 2026 — 15,425 monthly users14 August 2026 — 15,854 monthly users16 August 2026 — 15,841 monthly users18 August 2026 — 15,841 monthly users18 August 2026 — 15,833 monthly users20 August 2026 — 15,916 monthly users22 August 2026 — 16,042 monthly users24 August 2026 — 16,122 monthly users25 August 2026 — 16,299 monthly users26 August 2026 — 16,191 monthly users29 August 2026 — 16,833 monthly users30 August 2026 — 16,930 monthly users31 August 2026 — 16,953 monthly users1 September 2026 — 17,036 monthly users4 September 2026 — 17,129 monthly users6 September 2026 — 17,118 monthly users9 September 2026 — 17,079 monthly users12 September 2026 — 17,392 monthly users14 September 2026 — 17,379 monthly users17 September 2026 — 17,407 monthly users28 September 2026 — 16,659 monthly users5 October 2026 — 16,011 monthly users9 October 2026 — 15,921 monthly users13 October 2026 — 14,753 monthly users15 October 2026 — 14,807 monthly users18 October 2026 — 14,510 monthly users20 October 2026 — 14,461 monthly users23 October 2026 — 14,325 monthly users25 October 2026 — 14,111 monthly users28 October 2026 — 13,783 monthly users31 October 2026 — 13,537 monthly users3 November 2026 — 13,195 monthly users5 November 2026 — 13,004 monthly users6 November 2026 — 12,920 monthly users8 November 2026 — 12,718 monthly users14 November 2026 — 12,518 monthly users17 November 2026 — 12,224 monthly users6 August 202617 November 2026
39 measurements spanning 104 days, net -2,613. 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 11,447–18,184 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 39
Measured (UTC)Monthly usersChange
17 Nov 2026, 22:4412,224-294
14 Nov 2026, 18:0112,518-200
8 Nov 2026, 18:0112,718-202
6 Nov 2026, 11:1912,920-84
5 Nov 2026, 11:2613,004-191
3 Nov 2026, 10:1713,195-342
31 Oct 2026, 09:2813,537-246
28 Oct 2026, 00:1813,783-328
25 Oct 2026, 00:4614,111-214
23 Oct 2026, 03:3714,325-136
20 Oct 2026, 22:3014,461-49
18 Oct 2026, 19:3914,510-297
15 Oct 2026, 19:0014,807+54
13 Oct 2026, 12:0914,753-1,168
9 Oct 2026, 09:5715,921-90
5 Oct 2026, 02:2016,011-648
28 Sept 2026, 07:5716,659-748
17 Sept 2026, 20:1717,407+28
14 Sept 2026, 02:2017,379-13
12 Sept 2026, 06:0017,392first 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 158 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 17 November 2026 — this entry's latest reading, not the date you are reading this.

“BullX Bot” (@BullXBetaBot), 12,224 monthly users as measured 17 November 2026. Telegram Register, tgregister.com/channel/BullXBetaBot.

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.