Bot
BotFather
@BotFather
On this record: Topic · Growth · Engagement · Citations · Cite this entry
8,019,242monthly users
+69,987 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among the largest entries.
Register entry
| Telegram ID | 93372553 |
|---|---|
| Type | Bot |
| Username | @BotFather |
| First recorded | 6 August 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 60 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/BotFather |
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 88% 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
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 4 Nov 2026, 20:41 | 8,019,242 | +23,201 |
| 3 Nov 2026, 22:07 | 7,996,041 | +29,659 |
| 2 Nov 2026, 19:20 | 7,966,382 | +19,135 |
| 1 Nov 2026, 20:22 | 7,947,247 | +29,121 |
| 31 Oct 2026, 17:46 | 7,918,126 | +12,827 |
| 30 Oct 2026, 21:06 | 7,905,299 | +50,550 |
| 29 Oct 2026, 20:30 | 7,854,749 | +45,641 |
| 28 Oct 2026, 20:30 | 7,809,108 | +52,599 |
| 27 Oct 2026, 22:29 | 7,756,509 | +224,309 |
| 26 Oct 2026, 21:17 | 7,532,200 | +17,398 |
| 25 Oct 2026, 23:20 | 7,514,802 | +29,709 |
| 24 Oct 2026, 23:54 | 7,485,093 | +18,710 |
| 23 Oct 2026, 23:56 | 7,466,383 | +53,075 |
| 23 Oct 2026, 00:46 | 7,413,308 | +21,403 |
| 21 Oct 2026, 20:19 | 7,391,905 | -133,943 |
| 20 Oct 2026, 15:17 | 7,525,848 | -27,035 |
| 19 Oct 2026, 14:47 | 7,552,883 | -80,340 |
| 18 Oct 2026, 16:27 | 7,633,223 | +39,157 |
| 17 Oct 2026, 18:28 | 7,594,066 | +19,336 |
| 16 Oct 2026, 18:29 | 7,574,730 | first 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.
@Bot994 · 292 postsLearn Perfect English
@Learnperfectenglish · 21 postСигналы
@Signal_BPLA · 21 postCenTraLteXasSpunParTy
@SpunPartynPlaycentratexasMen4men · 161 postAnimal Crossing
@animalcrossingnavi · 11 postZaar
@azertyefixu · 21 postCilipep
@cilipep · 81 postТон по 8$ баксов
@gajajaksks · 351 post💌马来西亚会所|吉隆玻会所
@medusa0832 · 481 postSalmanhubbb
@poiybgm · 31 postPolisense. Важные обновления
@polisense · 371 postJ&T
@resumen123 · 31 post
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 1,076 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.
Named by
Channels on the register whose posts name this channel's handle.
@HowToClone · 33,488279 postsBotNews
@BotNews · 132,83469 postsRobots
@robots · 349,39368 postsVIP | Telegram Bots
@intartok · 6,68052 posts𝐒𝐎𝐔𝐑𝐂𝐄 𝐏𝐀𝐍𝐃𝐀 𖡋 سورس باندا
@SonicPandaHub · 93,02940 postsS𝐎𝐔𝐑𝐂𝐄 𝐌𝐀𝐑𝐈𝐎 . سورس ماريو
@MaRiOTaEm · 43,01124 postsقلعة التقنيات ♜︎ تطبيقات
@TechCsl · 26,30322 postsمصنع صنع بوتات - صانع البوتات - بوتات دعمكم - بوتات رشق
@x3344a · 5,89720 posts巨人网络官方频道
@juren · 13,98215 posts| CryptoМания | TSFCrypto |
@cryptomaniyaaaaa · 27,93414 postsrdfsx dev
@rdfsxdev · 339,13514 postsThe App Lab
@theapplab · 141,39814 posts@zhongwen 中文语言安装包🅥汉化翻译
@zhongwen677 · 65,88914 postsKoleksi Bot
@botkoleksi · 11,62513 posts李老根当狗推日记 @llggs
@llggx · 44713 postsNOTATKI
@notatki · 12,81413 postsTelegram Info
@tginfo · 83,68413 postsسورس زورو | Zoro Source 🎄
@BasamAldlim · 70,45112 postsBotHub
@bothub_center · 142,73812 postsکانال تکنولوژی هوش مصنوعی
@roidbest · 1,621,79112 postsTelegram Info عربي
@tginfoar · 25,00212 postsTG知识百科频道
@TGZSBK · 17,22012 postsTON Dev News
@tondev_news · 40,44112 posts- شروحات بوت فاذر .
@FxMxF · 1011 posts
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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“BotFather” (@BotFather), 8,019,242 monthly users as measured 4 November 2026. Telegram Register, tgregister.com/channel/BotFather.
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.