Telegram RegisterThe public register of Telegram

Bot

๐— ๐—ฎ๐—ท๐—ผ๐—ฟ ๐—›๐—ฒ๐—น๐—ฝ ๐—•๐—ผ๐˜ - (๐—”๐—ฑ๐˜€ ๐—ฎ๐—ป๐—ฑ ๐—ฆ๐˜‚๐—ฝ๐—ฝ๐—ผ๐—ฟ๐˜)

@MajorHelpBot

On this record: Topic ยท Growth ยท Engagement ยท Citations ยท Cite this entry

139,937monthly users

-20,477 since we began measuring on 7 August 2026

Risers and fallers across the register ยท movement among entries of 100,000โ€“316,228.

Register entry

Telegram ID7681803158
TypeBot
Username@MajorHelpBot
First recorded8 August 2026
Last confirmed live12 August 2026
Measurements held3
Confirmed unchanged3 times, most recently 12 August 2026
On Telegramt.me/MajorHelpBot

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 98% 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

139,937160,414150,175.57 August 2026 โ€” 160,414 monthly users8 August 2026 โ€” 160,414 monthly users9 August 2026 โ€” 139,937 monthly users7 August 20269 August 2026
3 measurements spanning 3 days, net -20,477. 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 136,865โ€“163,486 and does not start at zero.
Measurement log โ€” every monthly users count we have recorded
Measured (UTC)Monthly usersChange
9 Aug 2026, 23:36139,937-20,477
8 Aug 2026, 19:06160,414no change
7 Aug 2026, 00:17160,414first 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 2 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 9 August 2026 โ€” this entry's latest reading, not the date you are reading this.

โ€œ๐— ๐—ฎ๐—ท๐—ผ๐—ฟ ๐—›๐—ฒ๐—น๐—ฝ ๐—•๐—ผ๐˜ - (๐—”๐—ฑ๐˜€ ๐—ฎ๐—ป๐—ฑ ๐—ฆ๐˜‚๐—ฝ๐—ฝ๐—ผ๐—ฟ๐˜)โ€ (@MajorHelpBot), 139,937 monthly users as measured 9 August 2026. Telegram Register, tgregister.com/channel/MajorHelpBot.

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.